Skip to content

What should I look at first?

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-10.

Something looks off. Where do I start?

Wazuh fires dozens of alerts an hour. Get the one that matters, in plain words, without touching a server.

What you get: the alert to look at first, with its rule, level, MITRE technique and server, what it means in plain words, and every other alert in the window ranked below it. Nothing on your servers changes.

quox · talking to Quox

Something looks off on our servers. From Wazuh's alerts in the last two hours, what should I look at first? Give me the rule, its level, the MITRE technique and which server, then tell me what it means in plain words. Don't change anything.

▤ AOCL │ L1 identity complete · allowed · 1ms

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

▤ AOCL │ handoff narration kept out of the answer · I'll hand this to Argus, our Wazuh specialist, for a read-only look.

◐ DELEGATE │ delegate_to_agent agent_id=argus ✔ DELEGATE │ delegate_to_agent agent_id=argus │ 5 tools used, 5 tool outcomes · 54.1s

◐ ARGUS › WAZUH │ triage ✔ ARGUS › WAZUH │ triage │ 50ms

◐ ARGUS › WAZUH │ alerts ✔ ARGUS › WAZUH │ alerts │ 31ms

◐ ARGUS › WAZUH │ agent get ✔ ARGUS › WAZUH │ agent get │ 315ms

◐ ARGUS › WAZUH │ alerts ✔ ARGUS › WAZUH │ alerts

◐ ARGUS › WAZUH │ alerts ✔ ARGUS › WAZUH │ alerts

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

⛓ AEE │ envelope opened · stream_success

Reading is done. Nothing was changed.

Summary: 31 alerts came in over the last 2 hours, all between 11:37:37 and 11:44:42 UTC
(source: wazuh_alerts). Only one is at level 7 or above, and none reach the
high-severity mark of 12 (source: wazuh_triage). The top concern is a small SSH
brute-force burst against hyp-web-01.


Top concern: rule 5712 on hyp-web-01

• Rule: 5712, "sshd: brute force trying to get access to the system. Non existent user."
• Level: 10
• MITRE: T1110 Brute Force (tactic: Credential Access)
• Agent: 001, hyp-web-01 (192.0.2.22). It runs Ubuntu 24.04.3 LTS with Wazuh v4.12.0,
  and it is active, last checking in at 11:51:26 UTC (source: wazuh_agent_get).
• Count and time: it fired once, at 11:44:42.464 UTC (source: wazuh_triage).

What triggered it: rule 5710 ("Attempt to login using a non-existent user", level 5)
fired 9 times on agent 001 between 11:44:36.455 and 11:44:42.470 UTC. Wazuh maps that
rule to MITRE T1110.001 Password Guessing and T1021.004 SSH. Rule 5712 has a frequency
threshold of 8, so the 8th attempt in the burst set it off (source: wazuh_alerts). So
the activity was about six seconds of SSH logins with usernames that do not exist on the
host. It looks like automated scanning, not a targeted attack. I have not read the
source IP this turn, and that is the next thing to check.


All alerts, highest level first

Level       10
Rule        5712 sshd brute force, non-existent user
Count       1
Agents      001
Time (UTC)  11:44:42

Level       5
Rule        5710 sshd login attempt, non-existent user
Count       9
Agents      001
Time (UTC)  11:44:36 to 11:44:42

Level       3
Rule        5502
Count       8
Agents      002 (6), 001 (2)
Time (UTC)  11:37:39 to 11:38:05

Level       3
Rule        5501
Count       8
Agents      002 (6), 001 (2)
Time (UTC)  11:37:37 to 11:37:55

Level       3
Rule        5715
Count       3
Agents      002 (2), 001 (1)
Time (UTC)  11:37:37 to 11:37:53

Level       3
Rule        5402
Count       2
Agents      002
Time (UTC)  11:37:55

The level 3 rows are routine. I only read the rule ids and levels for them this turn,
not their descriptions. In the standard Wazuh ruleset, 5501 and 5502 are PAM sessions
opening and closing, 5715 is a successful SSH login, and 5402 is sudo to root. Those
meanings come from my general knowledge of Wazuh, not from this read. I also didn't look
up agent 002's hostname.


Suggested next steps (all read-only)

1. Get the source IP behind the 5710 and 5712 alerts on agent 001 and check whether it
   shows up anywhere else.
2. Make sure none of the three successful logins (rule 5715) came from that same source.
   The one on agent 001 was at 11:37, about 7 minutes before the burst started, so on
   timing alone they don't look connected. Confidence is moderate.
3. If the source turns out to be persistent or hostile, I can propose a firewall-block
   on agent 001. That would only run after you approve it, and I'd need the IP and a
   reason from you first.

The record of each read I made is kept as evidence for this session.

Tools used: wazuh_triage, wazuh_alerts ×3, wazuh_agent_get

Look at hyp-web-01 first: Argus found nothing above level 10 in the last two hours, and
nothing was changed.

63.8s · 6 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 mwampn

ARGUS, the Wazuh specialist, grouped the last two hours of alerts by rule, highest level first, and read the agent behind the top one. It found a short SSH burst on hyp-web-01: nine logins with usernames that do not exist (rule 5710) in about six seconds, which set off the brute-force rule 5712 at level 10. It says what it did not read (the source address, agent 002’s name) and which meanings come from general Wazuh knowledge rather than this read. Its next steps are reads, and the one change it mentions (blocking an address) would wait for your approval.

highest level first
quox wazuh triage --since 2h --level 5Ⓠ QUOX │ wazuh triage │ 2 rule groups, 10 alerts (level 5+, las… ✔LVL  COUNT  RULE  MITRE                AGENTS         LAST SEEN  CONTEXT  DESCRIPTION10   1      5712  T1110                hyp-web-01(1)  11m ago    -        sshd: brute force trying to get access to the system. Non existent user.5    9      5710  T1110.001,T1021.004  hyp-web-01(9)  11m ago    -        sshd: Attempt to login using a non-existent user
From a real run on our demo lab (two Ubuntu servers, a scripted SSH sweep).

--level sets the floor (the default 7 hides routine noise; 12 and above is high severity). --since takes 30m, 24h or 7d.

the burst behind rule 5712
quox wazuh alerts --rule 5710 --since 2h --limit 5Ⓠ QUOX │ wazuh alerts │ 5 alerts (last 2h) ✔WHEN     UTC                   LVL  AGENT       RULE  DESCRIPTION11m ago  2026-11-10 11:44 UTC  5    hyp-web-01  5710  sshd: Attempt to login using a non-existent user11m ago  2026-11-10 11:44 UTC  5    hyp-web-01  5710  sshd: Attempt to login using a non-existent user11m ago  2026-11-10 11:44 UTC  5    hyp-web-01  5710  sshd: Attempt to login using a non-existent user11m ago  2026-11-10 11:44 UTC  5    hyp-web-01  5710  sshd: Attempt to login using a non-existent user11m ago  2026-11-10 11:44 UTC  5    hyp-web-01  5710  sshd: Attempt to login using a non-existent user
Same lab, same window.

Narrow further with --agent <id|name>, --mitre T1110 or --q <text>.

Quox read Wazuh’s alerts and one agent record. Reading changes nothing, so no approval was needed. Anything that would change a server, such as an active response that blocks an address, waits for a person to approve it.