Hi,
In Wazuh 4.14, this is partially possible.
You can create a correlation rule that fires after several matching events using `if_matched_sid` with `frequency` and `timeframe`, and optionally `same_field` if the events share a stable common field.
However, Wazuh does not natively merge the decoded fields from multiple previous events into one new alert as separate variables. The correlated alert keeps the fields from the event that finally triggers the rule. The previous matching events are available only as raw text in `previous_output`.
So for your Windows Event ID 6416 / rule 60227 case:
- Yes, you can raise a new alert after the 3 related events arrive.
- No, you cannot build one Wazuh alert containing the structured fields of event 1 + event 2 + event 3 as independent fields.
- If the 3 events share a stable field such as a device identifier, use that with `same_field`.
Here is docu related:
-
https://documentation.wazuh.com/current/user-manual/ruleset/ruleset-xml-syntax/rules.htmlExample:
<rule id="100200" level="10" frequency="3" timeframe="5">
<if_matched_sid>60227</if_matched_sid>
<description>USB device detected after 3 correlated 6416 events. Current class=$(win.eventdata.className), current description=$(win.eventdata.deviceDescription)</description>
</rule>
If you need a single enriched alert containing data from all 3 events as structured fields, that requires external aggregation or custom scripting before/after Wazuh processing.
Regards