Skip to content

Your Wazuh security

Documented Checked against the CLI's current help and source. Not run end to end. Last checked on quoxcli 0.5.0, 2026-11-08.

Quox reads the Wazuh you already run. ARGUS, the Wazuh specialist, groups alerts by rule with their MITRE technique, ranks vulnerabilities by whether attackers actually use them, and signs a posture report anyone can verify offline. Reading changes nothing on your servers. Anything that would change a server (an active response, deploying or removing an agent) waits for a human approval.

What you need: QuoxCORE, the Wazuh plugin, and your Wazuh connected with quox wazuh connect (an org admin does this once).

  1. What should I look at first? Ask Quox which Wazuh alert matters most right now, with its rule, level, MITRE technique and server, explained in plain words. Machine verified 2 min
  2. Patch what attackers actually use Ask which vulnerabilities to patch first, ranked by whether they are exploited in the wild rather than by score alone. Machine verified 3 min
  3. Hand an auditor a signed Wazuh report Ask for a signed security posture report, then let the auditor check it on their own machine without trusting you. Machine verified 4 min
  4. See how hardened your servers are Ask Quox for the Wazuh security configuration assessment (the CIS benchmark score per server), then read the same scores from the terminal. Machine verified 2 min
  5. Wazuh at a glance Ask Quox whether your Wazuh manager is healthy, which daemons are stopped and why that is normal, and how many agents are actually reporting. Machine verified 1 min
  6. What changed on my servers' files Ask Quox what Wazuh file integrity monitoring holds for your servers, with the total per agent and what that number does and does not tell you. Machine verified 2 min