Hi Francisco,
As you can see your log matches with another existing decoder pattern named windows-date-format
So either we need to write decoders based on this decoder or we need to modify the existing decoder file.
Ref: https://documentation.wazuh.com/current/user-manual/ruleset/decoders/custom.html#modify-default-decoders
Before doing so. I would like to confirm that this is the right format of logs we are working with.
For this, you can enable archive JSON format log from your manager's ossec.conf
<ossec_config>
<global>
___________________
<logall_json>yes</logall_json>
_______________
After making the changes make sure to restart the manager.
We recommend creating custom rules and decoders based on archives.json because in these logs we can see the field full_log, which is the one being parsed by analysis, one of the archives.json events should look like this (the field of interest is in bold):
{"timestamp":"2023-09-05T02:47:40.074+0000","agent":{"id":"001","name":"abc","ip":"10.0.2.29},"manager":{"name":"Server85"},"id":"1693882060.373586","full_log
":"Sep 5 03:10:19 Server91 dbus-daemon[676]: [system] Successfully activated service 'org.freedesktop.UPower'","predecoder"{"program_name":"dbus-daemon","timestamp":"Sep 5 03:10:19","hostname":"Server91"},"decoder":{},"location":"/var/log/syslog"}No matter how you are forwarding the logs to Wazuh if you enable archive. You should see the all logs in the archive logs. Are you able to see similar logs in archives.json?
Can you share the output of this command?
cat /var/ossec/logs/archives/archives.json | grep WFBS-SVC
Or
cat /var/ossec/logs/archives/archives.json | grep quarantined
It will help me understand the format of your logs that are forwarded to Wazuh rule engine and I will be able to guide you accordingly.
Looking forward to your update on the issue.