Hi Frank,
I hope you are doing great today. About your questions, yes, this is expected behavior as rule 60106 is a default rule that captures windows login succesful events, You can see the rule below:
Here you will notice that this rule matches the eventID to one of several values, you can see 4769 but not 4768, which is why it is not matching the eventID you want. You could write a custom rule by copying this rule and then updating it to match your needs. I'll explain with an example and how you can do this.
To find the rule you want to check you can use the Kibana interface, go to Wazuh -> Management -> Rules, and here you can search for the rule id 60106 as shown below:
You can click the file name to view it, in here you will see several rules, you can scroll down to find 60106 and can copy the rule to your clipboard.. Then you need to go back and select Add new rules file from the options:
This will allow you to create a custom rule:
You can paste the rule from the previous step and edit it and use a different file name, this is just an example. You may notice I removed the groups tags and mitre tags, you may leave them if you wish. Once you are done with the change, you can save the file and restart the manager using the button that will appear. You can find more information below:
https://wazuh.com/blog/creating-decoders-and-rules-from-scratch/
You can copy the rule from here:
<group name="windows,windows_security,">
<rule id="100006" level="3">
<if_sid>60103</if_sid>
<field name="win.system.eventID">^4769$</field>
<description>You custom description for the rule</description>
<options>no_full_log</options>
</rule>
</group>
The other option would be to override the original rule, you
would need to do something similar to what we did, but you would not change the
Rule Id, also you would need the overwrite command in the Rule tag, like this:
More information here:
https://documentation.wazuh.com/current/user-manual/ruleset/custom.html
Best regards,
Ariel