If you go into the history of Checkpoint, it all started when the checkpoint was running on IPSO, back in the NOKIA days. NOKIA (yes, the phone company) was making the hardware and IPSO, the operating system, on which Checkpoint used to run. This IPSO was also a customised and hardened free BSD. So, not to brag, Checkpoint has crossed those waters which Juniper and PaloAlto are now sailing.
No PAN based on FreeBSD only. Similar to Juniper OS.
Juniper not get screen from Fortinet but who develop he detach from screen. Finally screen take care by Juniper.
I am curious what you're basing this assertion on. Consider PANW's own open source software listing: https://www.paloaltonetworks.com/documentation/oss-listings/oss-listings/pan-os-oss-listings/pan-os-... -- highlights include SELinux utilities and a base system package described as defining the base of a Red Hat Linux system. There are BSD-licensed utilities, but that is proof of nothing. The two mentions of FreeBSD on that page are related to a FIPS utility. The general list of known freebsd-based appliances has PAN not included: https://en.m.wikipedia.org/wiki/List_of_products_based_on_FreeBSD
as noted, the check point IPSO was FreeBSD based, but the boxes I've had occasion to handle were Linux-based.
hell, even Juniper has Wind River Linux running on the actual hardware these days. JCP (JunOS Control Plane) runs inside a we qemu hypervisor and then controls the hardware through virtio/virtnet drivers. This is mostly due to lack of aarch64 in older FreeBSD kernels, meaning the Linux + hypervisor layer is needed to facilitate use of Cavium processors. X86 is software emulated for JunOS.
Looks like report is quit old.there is no evidence that PAN is based on EL Kernel.
How we can ensure NSS report is correct and there is no pseudo information.
I did some research from my end. It is not completely correct information.
I was very familiar with this IPSO voyager interface. Correct statement.