Findings fields
The findings data streams store findings generated by detection rules. Wazuh creates one data stream for each event category, for example wazuh-findings-v5-security and wazuh-findings-v5-system-activity. You can query all of them with the wazuh-findings-v5* index pattern.
Findings include all the event fields, plus fields that describe the rule that matched and the case the finding belongs to:
wazuh.rule.*: The rule that generated the finding, including its ID, title, level, and status, its MITRE ATT&CK mapping (wazuh.rule.mitre.*), its compliance requirements (wazuh.rule.compliance.*), and the Sigma rule it was imported from (wazuh.rule.sigma_id).wazuh.case.*: The case the finding is attached to, including its title, status, severity, priority, TLP classification, owner, and comments.event.doc_idandevent.index: The ID and the backing index of the event that matched the rule.
The complete list of findings fields is in the fields.csv and wcs_flat.yml files of the stateless/events/findings module.
Example: Set the level of a finding from a rule
Decoders don't write findings fields. Wazuh creates a finding when an event matches a rule, and copies the rule's details into wazuh.rule.*. wazuh.rule.level comes from the rule's level. This rule matches the failed SSH logins that the system-auth integration decodes from the authentication log of a Linux endpoint.
Create the rule in Ruleset management > Detection > Rules. The rule's logsource.product must match the title of the integration you create it in. The events come from the built-in system-auth integration, so create the rule in a custom integration titled system-auth. Then promote it to the custom space and add it to a custom detector in Ruleset management > Detection > Detectors. The highlighted lines show where wazuh.rule.level is used and where it appears in the output.
Rule
logsource:
product: system-auth
level: high
status: experimental
enabled: true
tags:
- attack.credential-access
- attack.t1110
detection:
condition: selection
selection:
event.dataset: system-auth
event.outcome: failure
metadata:
title: SSH authentication failure
author: Security Team
description: Detects a failed SSH authentication on a monitored endpoint.
Finding (excerpt)
{
"_index": ".ds-wazuh-findings-v5-system-activity-000001",
"_source": {
"event": {
"dataset": "system-auth",
"action": "connection-closed",
"outcome": "failure",
"doc_id": "ncvwq6EBmx_Zvxl5lghO",
"index": ".ds-wazuh-events-v5-system-activity-000001"
},
"user": { "name": "wcsdocsfail" },
"source": { "ip": "192.168.72.3" },
"wazuh": {
"agent": { "name": "Ubuntu" },
"rule": {
"title": "SSH authentication failure",
"level": "high",
"tags": [ "high", "system-auth", "attack.credential-access", "attack.t1110" ]
}
}
}
}
Note
Filter findings by
wazuh.rule.levelto triage the most severe ones first.The rule level is also the first item of
wazuh.rule.tags, followed by the integration and the rule's own tags.event.doc_idandevent.indexpoint to the original event in the events data stream.
Fields
Field |
Type |
Level |
Normalization |
Indexed |
Example |
Description |
|---|---|---|---|---|---|---|
|
|
|
|
|
In a finding, the |
|
|
|
|
|
|
In a finding, the backing index of the event that matched the rule. |
|
|
|
|
|
|
Array of comments attached to the case, each authored and timestamped independently. |
|
|
|
|
|
|
Name of the user that authored the comment. |
|
|
|
|
|
|
Text content of the comment. |
|
|
|
|
|
|
Timestamp when the comment was created. |
|
|
|
|
|
|
Timestamp when the comment was last updated. |
|
|
|
|
|
|
Timestamp when the case was created. |
|
|
|
|
|
|
Detailed description of the case. |
|
|
|
|
|
|
Priority of the case. One of low, medium, high, urgent. |
|
|
|
|
|
|
Severity of the case. One of informational, low, medium, high, critical. |
|
|
|
|
|
|
Current status of the case. One of active, acknowledged, completed, error, deleted, audit. |
|
|
|
|
|
|
|
Tags attached to the case for organization. |
|
|
|
|
|
Title summarizing the case. |
|
|
|
|
|
|
Traffic Light Protocol classification of the case. One of TLP:RED, TLP:AMBER, TLP:GREEN, TLP:CLEAR. |
|
|
|
|
|
|
Timestamp when the case was last updated. |
|
|
|
|
|
|
Name of the user that owns the case. Not editable by the user. |
|
|
|
|
|
|
|
Rule author |
|
|
|
|
|
Rule category |
|
|
|
|
|
|
|
CMMC requirements. |
|
|
|
|
|
|
FedRAMP requirements. |
|
|
|
|
|
|
GDPR requirements. |
|
|
|
|
|
|
HIPAA requirements. |
|
|
|
|
|
|
ISO 27001 requirements. |
|
|
|
|
|
|
NIS2 requirements. |
|
|
|
|
|
|
NIST 800-171 requirements. |
|
|
|
|
|
|
NIST 800-53 requirements. |
|
|
|
|
|
|
PCI DSS requirements. |
|
|
|
|
|
|
TSC requirements. |
|
|
|
|
|
Rule description |
|
|
|
|
|
|
Rule ID. Under |
|
|
|
|
|
|
Severity level of the rule: |
|
|
|
|
|
|
Rule license |
|
|
|
|
|
MITRE ATT&CK subtechniques. |
||
|
|
|
|
|
|
MITRE ATT&CK subtechnique identifiers. |
|
|
|
|
|
|
MITRE ATT&CK subtechnique names. |
|
|
|
|
MITRE ATT&CK tactics. |
||
|
|
|
|
|
|
MITRE ATT&CK tactic identifiers. |
|
|
|
|
|
|
MITRE ATT&CK tactic names. |
|
|
|
|
MITRE ATT&CK techniques. |
||
|
|
|
|
|
|
MITRE ATT&CK technique identifiers. |
|
|
|
|
|
|
MITRE ATT&CK technique names. |
|
|
|
|
|
Rule name |
|
|
|
|
|
|
Rule reference URL |
|
|
|
|
|
|
Rule ruleset |
|
|
|
|
|
|
Identifier of the Sigma rule the rule was imported from, when it has one. |
|
|
|
|
|
|
Maturity status of the rule: |
|
|
|
|
|
|
|
Tags of the rule. Under |
|
|
|
|
|
Title of the rule. Under |
|
|
|
|
|
|
Rule UUID |
|
|
|
|
|
|
Rule version |