Skip to content

See how hardened your servers are

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.6.0 on 2026-11-11.

How well hardened are my servers?

Wazuh scores every server against a benchmark. Ask for the scores and what they mean.

What you get: the benchmark policy each server is checked against, its pass, fail and not-applicable counts, its score, and when it was last scanned.

quox · talking to Quox

Can you show me my security configuration assessment in Wazuh? I'd like to know how many policies there are.

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 7ms

◐ DELEGATE │ delegate_to_agent agent_id=argus ✔ DELEGATE │ delegate_to_agent agent_id=argus │ 2 tools used, 2 tool outcomes · 22.1s

◐ ARGUS › WAZUH │ agents ✔ ARGUS › WAZUH │ agents │ 55ms

◐ ARGUS › WAZUH │ sca ✔ ARGUS › WAZUH │ sca │ 78ms

⛓ AEE │ envelope opened · ops.tool · delegate_to_agent ok

⛓ AEE │ envelope opened · stream_success

Wazuh is Argus's domain, so I'll hand this to them.

There is one distinct SCA policy in this org: CIS Ubuntu Linux 24.04 LTS Benchmark 
v1.0.0. ( cis_ubuntu24-04 ). It runs on all 3 enrolled agents, which gives 3 policy
results, one per agent. All three agents are active (source: wazuh_agents) and all three
SCA reads succeeded (source: wazuh_sca).

Agent        │ ID  │ Pass │ Fail │ Invalid │ Total checks │ Score │ Last scan (UTC)
─────────────┼─────┼──────┼──────┼─────────┼──────────────┼───────┼─────────────────
hyp-wazuh-01 │ 000 │ 99   │ 138  │ 42      │ 279          │ 41%   │ 2026-11-10 12:56
hyp-web-01   │ 001 │ 99   │ 138  │ 42      │ 279          │ 41%   │ 2026-11-10 02:09
hyp-db-01    │ 002 │ 99   │ 138  │ 42      │ 279          │ 41%   │ 2026-11-10 02:10

What this means

• Every host scores 41% against CIS. Each one fails 138 of 279 checks, so more checks
  fail than pass. That is a weak hardening baseline, and it covers the Wazuh manager
  itself (000).
• The three hosts have exactly the same results. That usually means they were built from
  the same image and have not been hardened individually, so fixing the image once
  would improve all three. This is my inference from the matching numbers. I haven't
  confirmed it check by check.
• On every host, 42 checks came back invalid, meaning the check could not be evaluated.
  Those 42 are neither passes nor fails, so the real pass rate is unknown for that part
  of the benchmark.

Confidence is high for the numbers above. They come straight from the Wazuh SCA scans,
and all were taken today. I changed nothing.

If you want, I can pull the list of failed checks with their remediation advice for one
agent next. hyp-wazuh-01 (000) is the one I'd start with, since it runs the manager.

Tools used: wazuh_agents, wazuh_sca

32.6s · 3 tools · 0 approvals

A real turn on our own install (CLI 0.6.0, 10 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 10 Nov 2026 · test report mwaprc

Quox handed the question to ARGUS, the Wazuh specialist, which listed the agents and read the security configuration assessment. It reported one policy (the CIS Ubuntu 24.04 benchmark) running on all three servers, each scoring 41% with 138 of 279 checks failing, and said that the identical results were its own inference about a shared image, not something it checked line by line. Quox did not fix, rescan or change any server: it only read the scores.

wazuh sca
quox wazuh scaⓆ QUOX │ wazuh sca │ 3 policies across 3 agents ✔AGENT         POLICY                                        PASS  FAIL  N/A  SCORE  SCANNEDhyp-wazuh-01  CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0.  99    138   42   41%    11h 24m agohyp-web-01    CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0.  99    138   42   41%    10h 10m agohyp-db-01     CIS Ubuntu Linux 24.04 LTS Benchmark v1.0.0.  99    138   42   41%    10h 10m ago
From the same scratch workspace, read after the turn above.

The terminal counts one policy result per server, which is why it says 3 policies where Quox said one distinct policy on three servers. The N/A column is what Quox called invalid: checks Wazuh could not evaluate.

Quox and the terminal read the same assessment from your Wazuh manager. Reading a score changes nothing; raising it means fixing the failed checks on each server, which is a separate job.