Peter, Thank you. I was unaware of clamav support and will certainly look into your linked documentation to better understand it's use case and qualifications. I did know about clamav in name alone but never set out to learn how to implement it.
I will certainly read through documentation based on the need to check off boxes for the compliance regimes - I like how you put that. I will also watch your presentation - thanks so much!! Unrelated - I have one of your books, The Book of PF, 3rd edition. Thank you for your contributions to bettering computing. I will admit that I never finished reading it. I picked it up when I needed some help managing a pure OpenBSD firewall running PF. Now when I begin my OpenBSD related personal projects, it is by my side. I am familiar with commercial firewall software but I like the joy of being in the *pilot's seat. *I think you understand that. I appreciate you taking the time to respond to my questions. Take care, Brogan On Wed, Nov 25, 2020 at 5:33 PM Peter Nicolai Mathias Hansteen < pe...@bsdly.net> wrote: > > > 25. nov. 2020 kl. 23:10 skrev Brogan Beard <broganbe...@gmail.com>: > > In the enterprise context, there are often extensive security compliance > rules, which include but are not limited to anti-virus software > requirements. There are, of course, exceptions to these rules but generally > policies drive the technology in use or allow it to be used. I am not aware > of any anti-virus software that supports openbsd or any bsd for that matter > (not saying it needs it ;) ). > > > You will find functional antivirus in packages, such as clamav (which I > use in my spameater appliance), see eg > https://bsdly.blogspot.com/2014/02/effective-spam-and-malware.html (a > longish piece, but for reasons) > > > How does OpenBSD handle the compliance aspects of security in regards to > A/V? Is there an, "it's already under the hood," response based on modern > security standards? > > > I am not aware of any publicly available set of documents that provide the > direct checkoffs for OpenBSD with respect to specific compliance regimes, > but I’m fairly certain that you will find useful answers by reading OpenBSD > documentation with your lists of requirements in hand, checking off on your > list (if any) as you go along. > > I would recommend browsing the official OpenBSD docs at > https://www.openbsd.org/, with special attention to > https://www.openbsd.org/events.html and searching https://man.openbsd.org/ > using > relevant keywords. FWIW, perhaps even my recent presentation («OpenBSD and > you, the 6.8 update»), linked from > https://undeadly.org/cgi?action=article;sid=20201109055713 could provide > some useful pointers. > > All the best, > Peter > > > — > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. > > > > >
