Wazuh ruleset is used to detect attacks, intrusions, software misuse, configuration problems, application errors, malware, rootkits, system anomalies or security policy violations.
The ruleset includes compliance mapping with PCI DSS v3.1 and CIS.
├── wazuh-ruleset │ ├── decoders # OSSEC decoders created/updated by Wazuh │ ├── rules # OSSEC rules created/updated by Wazuh │ ├── rootchecks # OSSEC rootchecks created/updated by Wazuh │ ├── scap_content # OVAL, XCCDF, DS created/updated by Wazuh │ ├── lists # CDB lists created/updated by Wazuh | │ ├── tools | │ ├── README.md │ ├── VERSION │ ├── update_ruleset.py # Install/update ruleset
Full documentation at documentation.wazuh.com
stablebranch on correspond to the last ruleset stable version.
masterbranch contains the latest code, be aware of possible bugs on this branch.
If you have created new rules, decoders or rootchecks and you would like to contribute to our repository, please fork our Github repository and submit a pull request. To make a pull request for new rules and decoders, follow these instructions:
If your rules and decoders are related to existent ones in the ruleset, you should add them at the end of the corresponding file. If they are made for a new application or device that Wazuh does not currently support, you should create a new
XMLfollowing the title format. For example, if the last
0620-last-xml_rules.xml, the next one should be named
0625-new_integration.xml. Please, make sure your rules do not use an existent
Make sure to create your
test.inifile. You may find examples under the
wazuh/wazuh-ruleset/tools/rules-testing/testsfolder. Then add it to the repository along with the rest of the tests.
Create the pull request
If you are not familiar with Github, you can also share them through our users mailing list, to which you can subscribe by sending an email to
email@example.com. As well do not hesitate to request new rules or rootchecks that you would like to see running in Wazuh and our team will do our best to make it happen.