Hi German,
It is not possible the exact correlation you want. But based on your explanation I would like to propose this solution.
I believe only when you use "Reset Password..." and you leave the default check in the checkbox "user must change password at next logon" will always trigger this PasswordLastSet=%%1794 and PasswordLastSet=date will trigger in any password change condition.
So considering PasswordLastSet=%%1794 as a unique condition for password reset we can create a rule to trigger an alert.
Based on that we can write a new rule like this
<rule id="120066" level="15">
<if_sid>60110</if_sid>
<field name="win.system.eventID">^4738$</field>
<field name="win.eventdata.passwordLastSet">\p\p1794</field>
<description>User "$(win.eventdata.subjectUserName)" reset password </description>
</rule>
Ref:
Rules Syntax
Let me know if you need further assistance on this.
The agent ID field is not available for rule creation as this is considered as a log header and the rule engine has no information about it.
You can use the agent.name filed in the rule creation but you need to define it as <hostname>
<hostname>agent_name</hostname>
Saying so, you can use a list of parameters for rules using the CDB list.
The CDB list can contain keys and values. Values can be repeated, but the keys must be unique. You can add entries to a CDB list in key:value pairs or key: only.
With a key, we can determine the presence or absence of a field in a given list.
Check this document to learn more:
https://documentation.wazuh.com/current/user-manual/ruleset/cdb-list.html
You can also check these use cases to understand how the CDB list works.
https://documentation.wazuh.com/current/proof-of-concept-guide/audit-commands-run-by-user.html#wazuh-server
https://documentation.wazuh.com/current/user-manual/capabilities/malware-detection/cdb-lists-threat-intelligence.html
Let me know if you need any further information.