What it is
A searchable catalog of SCA policy.yml files that you can:
- Browse by platform (Linux, Windows), application (Apache, NGINX, MySQL, etc.), and CIS version
- Search by keyword across policy names, descriptions, and application names
- Preview the full YAML content before deploying
- Detect agents — discover which of your endpoints have the relevant software installed
- Deploy with copy-paste-ready shell commands
- The CIS benchmark version
- Target platform and application
- Application version
- A description of what the benchmark covers
Why this is a power feature
CIS benchmarks are most valuable once your agents are reporting and you have visibility into what software is running across your fleet. SCA Policies builds on top of the SCA Overview by helping you answer two questions:- Which policies should I deploy? — Browse the catalog and filter by the applications you care about.
- Which agents need this policy? — Use the built-in agent detection to find endpoints running the target software (e.g., Apache, MySQL, NGINX).
Where it lives in the UI
Menu path: Agents → Security Configuration Assessment → SCA Policies The page shows the full policy catalog with:- A search bar for free-text search across policy names, descriptions, and applications
- A filter panel with dropdowns for Platform and Application (dynamically populated from available policies)
- Policy cards showing the CIS version, platform badge, application version, policy name, and description
Operator workflows
Browse available policies
- Navigate to Agents → Security Configuration Assessment → SCA Policies
- The catalog loads automatically from the CoPilot-SCA repository
- Use the search bar to find policies by name or application (e.g., “apache”, “mysql”)
- Use the filter panel to narrow by platform or application
Detect agents running a specific application
- Click a policy card to open the detail view
- In the Agents with [application] section, click Detect Agents
- CoPilot queries the Wazuh Indexer for installed packages matching the application
- Results show each agent with the package name, version, and architecture
- Use this to identify which endpoints should receive the policy
Preview the policy YAML
- In the policy detail view, find the Policy YAML section
- Click Load YAML to fetch the full policy content from GitHub
- Review the checks, requirements, and conditions before deploying
Deploy a policy to an agent
- In the policy detail view, find the Deployment Instructions section
- The section provides ready-to-run commands tailored to the selected policy
- SSH into the target agent and run the commands:
- After the agent restarts, Wazuh will automatically pick up the new policy and begin scanning
- Results will appear in the SCA Overview within a few minutes
End-to-end example: deploying a MySQL benchmark
- Open SCA Policies and search for “mysql”
- Click the CIS Oracle MySQL Community Server 5.6 - Debian card
- Click Detect Agents — CoPilot finds agent
piHole(ID 088) withmariadb-serverinstalled - Review the Deployment Instructions — the commands are pre-filled with the correct filename
- SSH into the agent and run:
- Verify in logs:
tail -f /var/ossec/logs/ossec.log— look for SCA scan messages - Check SCA Overview to see the compliance score for the new policy
Policy detail view
When you open a policy, you’ll see:| Section | Description |
|---|---|
| Policy Information | ID, application, app version, platform, CIS version |
| Description | What the CIS benchmark covers |
| Deployment Instructions | Copy-paste shell commands to deploy the .yml file to an agent |
| Agents with [application] | Detect which agents have the relevant software installed |
| Applicable SCA Policies | Other policies in the catalog for the same application |
| Policy YAML | Full YAML content preview (loaded on demand) |
Supported applications
The following application categories are tracked for automatic agent detection:| Application | Package patterns searched | Example policy |
|---|---|---|
| Apache | apache2, httpd, apache2-bin, apache2-utils | CIS Apache HTTP Server 2.4 |
| NGINX | nginx, nginx-common, nginx-core, nginx-full | CIS NGINX |
| IIS | iis, w3svc | CIS Microsoft IIS |
| MySQL / MariaDB | mysql-server, mysql-community-server, mariadb-server, mariadb-common | CIS Oracle MySQL Community Server 5.6 |
| PostgreSQL | postgresql, postgresql-common, postgresql-client | CIS PostgreSQL |
| SQL Server | mssql-server, mssql-tools | CIS Microsoft SQL Server |
Setup checklist
SCA Policies works out of the box with no additional configuration:- CoPilot is running (policies are fetched from GitHub automatically)
- Wazuh Indexer is connected (required for agent detection)
- SSH access to agents (required for deploying
.ymlfiles)
Important notes
- File location: SCA policy
.ymlfiles must be placed in/var/ossec/ruleset/sca/on the agent. - Ownership: Files must be owned by
root:wazuh— usechown root:wazuh <filename>after downloading. - Agent restart: The Wazuh agent must be restarted (
systemctl restart wazuh-agent) to pick up new policies. - Verification: Check
/var/ossec/logs/ossec.logfor SCA scan messages after deploying a new policy. - Results: Once deployed, SCA scan results appear in the SCA Overview page.
Related resources
- Policy repository: https://github.com/socfortress/CoPilot-SCA
- Wazuh SCA documentation: https://documentation.wazuh.com/current/user-manual/capabilities/sec-config-assessment/index.html
- SCA Overview (compliance results)
