Security Configuration Assessment
The wazuh-states-sca index stores the results of the Security Configuration Assessment (SCA) checks on each endpoint, with the policy each check belongs to.
The following example shows a document from the wazuh-states-sca index. It records the result of a CIS benchmark check on the Ubuntu endpoint:
{
"_index" : "wazuh-states-sca",
"_id" : "wazuh_003_4ac934f2a35158bf04255a96435edf246798aedf",
"_score" : 1.0,
"_source" : {
"checksum" : {
"hash" : {
"sha1" : "fed019ea7dfb3d744a4ac23cef96c3f88dc6ff92"
}
},
"wazuh" : {
"cluster" : {
"name" : "wazuh"
},
"agent" : {
"host" : {
"hostname" : "ubuntu-QEMU-Virtual-Machine",
"os" : {
"name" : "Ubuntu",
"type" : "linux",
"version" : "24.04.4 LTS (Noble Numbat)",
"platform" : "ubuntu"
},
"architecture" : "aarch64"
},
"name" : "Ubuntu",
"groups" : [
"default"
],
"id" : "003",
"version" : "v5.0.0"
}
},
"check" : {
"result" : "Passed",
"remediation" : "Run the following script to unload and disable the cramfs module: - IF - the cramfs kernel module is available in ANY installed kernel: - Create a file ending in .conf with install cramfs /bin/false in the /etc/modprobe.d/ directory - Create a file ending in .conf with blacklist cramfs in the /etc/modprobe.d/ directory - Run modprobe -r cramfs 2>/dev/null; rmmod cramfs 2>/dev/null to remove cramfs from the kernel - IF - the cramfs kernel module is not available on the system, or pre-compiled into the kernel, no remediation is necessary #!/usr/bin/env bash.",
"condition" : "any",
"compliance" : {
"iso_27001" : [
"A.5.37",
"A.8.32",
"A.8.25"
],
"hipaa" : [
"164.308.a.1",
"164.308.a.8"
],
"pci_dss" : [
"1.2.5",
"2.2.4",
"6.4.1"
],
"tsc" : [
"CC6.3",
"CC6.6",
"CC8.1",
"CC5.1",
"CC5.2",
"CC5.3"
],
"nis2" : [
"21.2.e",
"21.2.a"
],
"nist_800_171" : [
"3.4.7",
"3.4.8",
"3.13.6"
],
"fedramp" : [
"CM-2",
"CM-3",
"CM-6",
"CM-7"
],
"nist_800_53" : [
"CM-2",
"CM-3",
"CM-6",
"CM-7"
],
"cmmc" : [
"CM.L2-3.4.7",
"CM.L2-3.4.8",
"SC.L2-3.13.6"
],
"gdpr" : [
"IV_32.1.a",
"IV_32.1.b",
"IV_32.1.c",
"IV_32.1.d",
"IV_32.2",
"IV_32.3",
"IV_32.4"
]
},
"name" : "Ensure mounting of cramfs filesystems is disabled.",
"description" : "The cramfs filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A cramfs image can be used without having to first decompress the image.",
"mitre" : {
"technique" : {
"name" : [
"Masquerading",
"Hide Artifacts"
],
"id" : [
"T1036",
"T1564"
]
},
"tactic" : {
"name" : [
"Stealth"
],
"id" : [
"TA0005"
]
}
},
"rules" : [
"c:modprobe -n -v cramfs -> r:install /bin/false|install /bin/true|Module cramfs not found",
"not c:lsmod -> r:cramfs",
"d:/etc/modprobe.d/ -> r:.*\\.conf -> r:^blacklist\\s+cramfs"
],
"id" : "35500",
"rationale" : "Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it."
},
"state" : {
"document_version" : 298,
"modified_at" : "2026-10-29T08:02:08.403Z"
},
"policy" : {
"file" : "cis_ubuntu24-04.yml",
"references" : [
"https://www.cisecurity.org/cis-benchmarks/"
],
"name" : "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0.",
"description" : "This document provides prescriptive guidance for establishing a secure configuration posture for Ubuntu Linux 24.04 LTS based on CIS benchmark for Ubuntu Linux 24.04 LTS.",
"id" : "cis_ubuntu24-04"
}
}
}
Example: Detect an SCA check that starts failing, then see where it fails
The Wazuh agent sends an SCA event when the result of a check changes. check.result is in that event and in the wazuh-states-sca index. A rule flags checks that change to Failed, then a query shows where the check fails now.
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 wazuh-sca integration, so create the rule in a custom integration titled wazuh-sca. Then promote it to the custom space and add it to a custom detector in Ruleset management > Detection > Detectors. In the query, replace <WAZUH_INDEXER_IP_ADDRESS>, <USERNAME>, and <PASSWORD> with your values. The highlighted lines show where check.result is used and where it appears in the output.
1. Rule on SCA events
logsource:
product: wazuh-sca
level: medium
status: experimental
enabled: true
detection:
condition: selection
selection:
event.dataset: wazuh.sca
check.result: Failed
metadata:
title: SCA check started failing
author: Security Team
description: Detects an SCA check whose result changed to Failed.
2. Finding (excerpt)
{
"event": { "dataset": "wazuh.sca", "action": "policy-check-evaluated", "outcome": "failure" },
"check": {
"id": "35608",
"name": "Ensure ip forwarding is disabled.",
"result": "Failed"
},
"wazuh": {
"agent": { "name": "Ubuntu" },
"rule": { "title": "SCA check started failing", "level": "medium" }
}
}
3. Query on the state index
curl -k -u <USERNAME>:<PASSWORD> -X GET "https://<WAZUH_INDEXER_IP_ADDRESS>:9200/wazuh-states-sca/_search?pretty" \
-H 'Content-Type: application/json' -d '
{
"query": { "bool": { "filter": [
{ "term": { "check.id": "35608" } },
{ "term": { "check.result": "Failed" } }
] } },
"_source": [ "wazuh.agent.name", "policy.name", "check.id", "check.name", "check.result" ]
}'
4. Result (excerpt)
"hits": [
{
"_index": "wazuh-states-sca",
"_source": {
"wazuh": { "agent": { "name": "Ubuntu" } },
"policy": { "name": "CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0." },
"check": {
"id": "35608",
"name": "Ensure ip forwarding is disabled.",
"result": "Failed"
}
}
}
]
Note
check.resultvalues start with a capital letter, such asPassedandFailed.
Fields
Field |
Type |
Level |
Normalization |
Indexed |
Example |
Description |
|---|---|---|---|---|---|---|
|
|
|
|
|
Log message optimized for viewing in a log viewer. |
|
|
|
|
|
|
|
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. |
|
|
|
|
|
Relationship between the rules. |
|
|
|
|
|
|
Extended description of the check. |
|
|
|
|
|
|
The ID of the SCA policy check. |
|
|
|
|
|
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. |
|
|
|
|
|
The name of the SCA policy check. |
|
|
|
|
|
|
The reason for the check. Why it is important. |
|
|
|
|
|
|
Reason for the check result. |
|
|
|
|
|
|
|
References for the check. |
|
|
|
|
|
Actions to take to remediate the check. |
|
|
|
|
|
|
Result of the check. |
|
|
|
|
|
|
|
Rules to be evaluated. |
|
|
|
|
SHA1 hash used as checksum of the data collected by the agent. |
||
|
|
|
|
|
Extended description of the policy. |
|
|
|
|
|
|
The file name of the SCA policy. |
|
|
|
|
|
|
The ID of the SCA policy. |
|
|
|
|
|
|
The name of the SCA policy. |
|
|
|
|
|
|
|
References for the policy. |
|
|
|
|
Version of the document. |
||
|
|
|
|
Date/time when the state was last modified. |
||
|
|
|
|
|
|
List of groups the agent belongs to. |
|
|
|
|
|
Operating system architecture. |
|
|
|
|
|
Hostname of the host. |
||
|
|
|
|
|
Host ip addresses. |
|
|
|
|
|
|
Operating system name, without the version. |
|
|
|
|
|
|
Operating system platform (such centos, ubuntu, windows). |
|
|
|
|
|
|
Which commercial OS family (one of: linux, macos, unix, windows, ios or android). |
|
|
|
|
|
|
Operating system version as a raw string. |
|
|
|
|
|
|
Unique identifier of this agent. |
|
|
|
|
|
|
Custom name of the agent. |
|
|
|
|
|
|
Version of the agent. |
|
|
|
|
|
Wazuh cluster name. |
||
|
|
|
|
Wazuh cluster node name. |
||
|
|
|
|
Wazuh schema version. |