| 1 | --- |
| 2 | title: SCA overview |
| 3 | description: Review Wazuh Security Configuration Assessment (SCA) posture across endpoints. |
| 4 | --- |
| 5 | |
| 6 | # SCA overview |
| 7 | |
| 8 | **Menu:** Agents → SCA Overview |
| 9 | |
| 10 | SCA (Security Configuration Assessment) is Wazuh’s secure configuration/hardening framework. It evaluates endpoints against policies (benchmarks) and reports pass/fail results so you can: |
| 11 | - find configuration drift |
| 12 | - measure baseline hardening posture |
| 13 | - prioritize remediation of failed controls |
| 14 | |
| 15 |  |
| 16 | |
| 17 | --- |
| 18 | |
| 19 | ## What you’re looking at |
| 20 | |
| 21 | ### Filters |
| 22 | |
| 23 |  |
| 24 | |
| 25 | You can scope results by: |
| 26 | - **Customer** (multi-tenant) |
| 27 | - **Agent Name** |
| 28 | - **Policy Name** |
| 29 | - **Score range** (min/max) |
| 30 | |
| 31 | ### Load SCA Data |
| 32 | |
| 33 |  |
| 34 | |
| 35 | This page typically requires an initial fetch. |
| 36 | |
| 37 | Use **Load SCA Data** to pull the latest SCA results into the view. |
| 38 | |
| 39 | ### Results view |
| 40 | |
| 41 |  |
| 42 | |
| 43 | Once loaded, you’ll use this page to identify: |
| 44 | - which agents are failing baseline policies |
| 45 | - which policies are producing the lowest scores |
| 46 | - where remediation work will produce the biggest posture improvement |
| 47 | |
| 48 | --- |
| 49 | |
| 50 | ## When to use it |
| 51 | |
| 52 | Use SCA overview when you need to: |
| 53 | - identify endpoints failing hardening baselines |
| 54 | - find drift after a change window (GPO, tooling rollout, new images) |
| 55 | - support audits/compliance reporting with repeatable evidence |
| 56 | |
| 57 | --- |
| 58 | |
| 59 | ## Common tasks |
| 60 | |
| 61 | ### Triage low scores first |
| 62 | |
| 63 | A practical flow: |
| 64 | 1) Filter by customer |
| 65 | 2) Set a **Max Score** threshold (start low) |
| 66 | 3) Identify the bottom-scoring endpoints/policies |
| 67 | 4) Remediate the highest leverage failures (the ones that apply broadly) |
| 68 | |
| 69 | ### Investigate and remediate failed checks |
| 70 | |
| 71 | Use the agent’s dedicated page to drill down: |
| 72 | - open an agent and review the **SCA** tab for policy/check details |
| 73 | |
| 74 | Remediation usually happens outside CoPilot (GPO, configuration management, image updates), then you validate by re-running SCA and confirming the score improves. |
| 75 | |
| 76 | ### Export / reporting |
| 77 | |
| 78 | If you need a deliverable: |
| 79 | - see: [SCA report](/user/ui/report-sca) |
| 80 | |
| 81 | --- |
| 82 | |
| 83 | ## Prerequisites |
| 84 | |
| 85 | - Wazuh SCA is enabled on agents |
| 86 | - Policies are deployed to the endpoints/groups you care about |
| 87 | - Agents are checking in and SCA scans have run |
| 88 | |
| 89 | --- |
| 90 | |
| 91 | ## Gotchas |
| 92 | |
| 93 | - SCA is only as good as your policies and rollout. Keep policies consistent per OS/group/customer. |
| 94 | - Score changes often lag behind configuration changes (depends on scan cadence + agent check-in). |
| 95 | - Don’t chase perfect scores blindly—prioritize controls that reduce real risk for your environment. |