Closed zbalkan closed 1 year ago
@zbalkan Why do you say that OSSEC is defunct ? It seems to be active: https://github.com/ossec/ossec-hids/compare/3.7.0...master
15 PRs merged in 3 years for a security product look defunct for me. Half of them are just documentation updates and some of the others are regex pattern fixes for edge cases. There is less than 5 actual improvements in 3 years.
But of course, it is subjective.
@zbalkan Ok. Sounds sensible.
Also, I know many people still stick to OSSEC due to various reasons. I don't suggest removal of OSSEC from LYNIS as an approved product. I suggest adding Wazuh along with it.
@zbalkan Added an alternative pull request with the same FINT-4344 test and also a TOOL-5128 test.
There was already a PR I created last year. I might have missed some details but it is linked already. I am open for review.
Is your feature request related to a problem? Please describe. Wazuh is a SIEM and XDR solution, that is a fork of OSSEC. It is actively developed and supported. The agent includes a daemon that works on Linux, Windows and MacOS clients called wazuh-syscheckd. The agent does the file integrity checks on the endpoints that are configured for FIM via syscheck configuration.
The OSSEC is already included in the current tests (FINT-4328). Since Wazuh is a continuation to now defunct OSSEC project, it is also acceptable by current standards.
Therefore,
wazuh-sysceckd
should be able to satisfy remote logging capabilities.Describe the solution you'd like Include wazuh-sysceckd in the accepted FIM utilities in test FINT-4350.
Required changes File integrity tests need a new check
Additional context Wazuh is an open source solution that helps PCI-DSS compliance with built-in capabilities. FIM is one of them.
https://documentation.wazuh.com/current/pci-dss/file-integrity-monitoring.html https://documentation.wazuh.com/current/user-manual/capabilities/file-integrity https://documentation.wazuh.com/current/user-manual/capabilities/file-integrity/how-it-works.html