Can you please explain what you mean by that ? Honestly I am a bit scared after reading that.
The only reason I switched from Linux to GhostBSD is because I read BSD is more secure.
The Linux kernel offers all kinds of bells and whistles regarding security - it offers the grsecurity/PaX patchset, apparmor/tomoyo/SELinux security framework, strong ASLR, trusted path execution, various stack protection functionalities, seccomp etc. and some distros offer additional userspace protections like position independent code/executables, pointer obfuscations, stack/heap protections and whatnot. However, all of those features introduce quite some more lines of code, and if you have a big chunk of sourcecode you have quite some bugs also in it. The Linux kernel consists of far more code than the clean kernel of FreeBSD, maybe even than the whole FreeBSD operating system. Also, just look at Ubuntu: there you have a kernel update roughly weekly, and those updates also introduce some regressions. To emphasize this argument, just look at the number of CVEs:
FreeBSD CVEs vs
Linux Kernel CVEs - here you see that the the Linux kernel alone (without the tools of a base system like Debian or Ubuntu) has far more vulnerabilities than the whole FreeBSD operating system. But also note: just taking the number of CVEs into account for measuring a systems security is not enough.
And while those security frameworks are nice and interesting and do make sense in some environments, just look around at some tutorials about RedHat/Centos: most of them suggest to turn off SELinux in the first paragraph, otherwise the stuff you are configuring won't work - so what's the use of a security framework if you have to turn it of for most of the software you are trying to run? Even if you choose to develop all those complex SELinux rulesets, it is a hell lot of work!
It is not that FreeBSD is lacking all of the features I mentioned above, it just offers not that many. FreeBSD is a quite secure system, and most importantly: security is regarded as important by it's developors. Thats why we have the intrustion detection system feature of the base system, pkg audit and vuxml, security announcements etc. I can tell you that having a patched version of Firefox/Chromium is very important for desktop systems, and the situation with Firefox is very good: we get new versions as fast as with the most secure Linux distributions out there. Furthermore, I have been tracking the security issues of the stacks my clients use (various: mysql, postgresql, nginx, apache, php, nodejs, python, dovecot, postfix, samba, haproxy etc.) on their servers since 2016 and I can tell you that for most of the software packages FreeBSD is among the fastest systems to patch them! FreeBSD offers nice tools for you to have a very secure workstation/server (have a look at jails, or capsicum if you are a developer). I have switched from OpenBSD to FreeBSD on my workstations and do consider them more secure now.
...
Security isn't a product, it's a process. And any operating system can be rendered insecure through bad practices. OpenBSD is deemed slightly more secure at install by turning off or not loading unneeded services to reduce the attack surface. FreeBSD doesn't do this by default and has been criticised for that
here. However, if you follow best security practices then FreeBSD can be as secure as any other general purpose OS.
! ^^ this cannot be emphasized enough. The process is far more important than what operating system you are using.