Hi Gustavo
Hope you are doing well today and thank you for using wazuh.
Let me explain how rules and decoders work, First, the logs are generated by servers or devices and sent to the manager server. Then the logs are decoded by the default decoders that are present at the manager side /var/ossec/ruleset/decoders. If you get the logs but they don't match the default decoder, in that case, you have to make custom decoders. Once the log is decoded it will match to default rules that are present at the manager server/var/ossec/ruleset/rules/. If it doesn't match any of the rules or the rule level is less than 3 you won't get any alerts, in that case, you have to make rules on the basis of decoders and log at /var/ossec/etc/rule/local_rules.xml .
So, There are default rules and decoders if logs reach the manager but you don't get alters in that situation to need to create custom rules and decoders.
If you have a log and you want to test it you can run the log at/var/ossec/bin/wazuh-logtest and there you can see the decoders and rules for that particular log.
Now can you please be more specific about what you are looking for if you want this rule to be triggered the rule level must be 3 or more that that.
<group name="windows, sysmon, sysmon_event1">
<rule id="100040" level="1">
<if_sid>92217</if_sid>
<field name="win.eventdata.image"
negate="yes" >C:\\WINDOWS\\servicing\\TrustedInstaller.exe</field>
<description>Falso positivo insight</description>
<options>no_full_log</options>
<group>pci_dss_10.2.5,gdpr_IV_32.2,</group>
</rule>
If you want to ignore the field which have a specific path you can use
negate="yes"
<field name="win.eventdata.image" negate="yes" >C:\\WINDOWS\\servicing\\TrustedInstaller.exe</field>
Hope this will helps.
Regards,