Three ways a third-party Wazuh rules file breaks a 4.14.7 manager
This week we loaded a third-party Wazuh decoder and rules file, exactly as published, into a clean...
Tag archive
This week we loaded a third-party Wazuh decoder and rules file, exactly as published, into a clean...

A verified Azure-to-Wazuh-to-Qwen SOC lab with read-only alert analysis and human review.
For an event that comes from an agent, analysisd sets the host name to the agent name before rules...

A hands-on Azure Ubuntu and Wazuh 4.14.8 lab using Tailscale, private agent communication, SSH detection, and verified security alerts.
If you run Wazuh for several customers, there is a good chance you separate them the 4.x way: an...
A custom rule can pass the loader, sit in etc/rules for months and never fire, and nobody notices,...
What you see: several log lines match within a minute and you get one email or webhook call, not one...
What tells you a Wazuh rule has gone quiet? An MSSP detection lead described a gap to us...
The rule fired, the alert is in alerts.json, and the block did not happen. This line is written by a...
You edit rules, save, reload the ruleset from the dashboard or the API, and shortly afterwards...
You wrote a custom rule. wazuh-analysisd -t exits 0, a one-line logtest even shows it matching, and...
You grep alerts.json and the alert is there. You open the dashboard and it is not. The manager looks...