Hi Thaynara,
Thank you for reaching out!
To disable specific operations within a rule without affecting the entire rule, you can create a custom rule in the /var/ossec/etc/rules/local_rules.xml file. Unfortunately, Wazuh doesn't allow the direct deactivation of individual operations within a rule; however, you can adjust the rule to ignore the events that correspond to the operations of lesser importance.
Here's a general approach you can take:
Copy the original rule: Identify the original rule (e.g., rule ID 91594) in the ruleset located at /var/ossec/ruleset/rules/ and copy its definition to your local_rules.xml.
Modify the Match Conditions: Edit the copy to exclude the specific operations you want to disable (in this case, the ones you've highlighted in red). You can achieve this by adjusting the <match> tag or using <not_match> conditions if available.
Add the overwrite="yes" tag: Remember to include the overwrite="yes" attribute to ensure that your changes take precedence over the original rule.
Restart the Wazuh manager: After making these changes, restart the Wazuh manager to apply them.
If you need help to redact the rule I will need the events that generate the alerts.
I was testing, and adding this rule worked for me:
This is based on the original alert-generating rule, 91594. I set the level to 0 to ensure that these will never be included in your configuration regarding the base level from which you decide to receive alerts.
In the field name, I included a regular expression that matches each of the options for which you want to stop receiving alerts.
You can add this rule in your own XML file that you create within /var/ossec/etc/rules/
With that, you should be able to resolve your issue. Best regards!



