You can generate a test event by logging into the agent machine using incorrect credentials. In this case, you will receive alert ID 60122 "Logon Failure - Unknown user or bad password" and MITRE ID T1531.
Tail the alerts log for your test event:
- sudo tail -f /var/ossec/logs/alerts/alerts.json | grep "60122"
- Trigger another failed login on the agent and watch for a new entry (it should trigger 60122 rule ID that satisfied your requirement of Mitre. If nothing appears here, double-check your agent's connection (/var/ossec/bin/agent_control -l)
The above-mentioned rule is for the Windows logon failure alert.
Verify that other logs from this agent are being received successfully.
If the agent is disconnected, then troubleshoot to reconnect back otherwise, no logs appear on the dashboard from that agent.
Windows 64-bit: C:\Program Files (x86)\ossec-agent\ossec.log
Windows 32-bit: C:\Program Files\ossec-agent\ossec.log
Please share the logs from the agent ossec.log if the agent is disconnected.
If the agent is connected, then verify the alert received to the alerts.json file as mentioned above, and if you can find the log there, then check again in the dashboard by navigating to Discovery -> Add filter -> Field as
rule.id , Operator is and value 60122 -> Save.
Also, you can check by navigating to Threat Intelligence -> MITRE ATT&CK -> Events
Let me know the update on this.