See your open incidents and how severe they are
What is still open, and how bad is it?
Quox turns alerts into incidents. One question gives you the count, which ones are still open, how severe they are and where to start.
What you get: every incident in your org, split by status and severity, the open ones named with their server and alert, and a suggested first one to look at. Nothing changes when you ask.
Ask Quox
Section titled “Ask Quox”Can you show me my governance incidents? I'd like to know how many monitoring incidents there are.
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 3ms
◐ QUOX │ cli ✔ QUOX │ cli │ 8 total, 8 showing, 8 sample · 8.6s
⛓ AEE │ envelope opened · ops.tool · quox_cli ok
⛓ AEE │ envelope opened · stream_success
There are 8 monitoring incidents in total (showing 8 of 8). All of them came from Wazuh alerts. By status: 4 open, 2 resolved, 2 closed. By severity: 6 medium, 2 high. The 4 open incidents: • hyp-web-01: Level 10 sshd brute force from a non-existent user (INC_1794177398557_g7a615). It is the oldest, opened 8 Nov, and repeats are still being added to it. It is unassigned. • hyp-wazuh-01: Level 7, listening ports changed (INC_1794315171968_una5zc). • hyp-db-01: Level 7, new dpkg package installed (INC_1794315220835_z969eu). • hyp-db-01: Level 7, dpkg half configured (INC_1794315221474_lmk79l). None of the four has an assignee. The three level 7 ones were all raised around 12:53 UTC today. The 4 settled incidents are the two level 12 "DEMO" sshd brute force alerts and two earlier level 10 brute force alerts. Their resolutions say the demo rule was removed, there was no repeat for 6 hours, or the incident duplicated g7a615. I'd start with the hyp-web-01 brute force, since it is the highest level and still active. The two hyp-db-01 dpkg alerts look related, so one package change may explain both. I can hand either to sentinel or argus for investigation if you like.
20.0s · 1 tool · 0 approvals
quox.✔ Machine verified against the CLI on 10 Nov 2026 · test report mwapg4
Quox read the real incident list for your org, the same one the terminal shows below. It counted 8 incidents (4 open, 2 resolved, 2 closed; 6 medium, 2 high), named each open one with its server and alert, noticed that none has an owner yet and that two of them look related, and suggested which to start with. Quox did not assign, resolve or close anything. It offered to hand an incident to an investigating agent and waited for you to say so.
Do it yourself
Section titled “Do it yourself”quox monitoring incidents listID Severity Status Type Agent CreatedINC_1794315221474_lmk79l medium open wazuh_alert - 2026-11-10T12:53:41.474ZINC_1794315220835_z969eu medium open wazuh_alert - 2026-11-10T12:53:40.835ZINC_1794315171968_una5zc medium open wazuh_alert - 2026-11-10T12:52:51.968ZINC_1794266476182_hh26hg medium resolved wazuh_alert - 2026-11-09T23:21:16.182ZINC_1794254437334_l02xcz high closed wazuh_alert - 2026-11-09T20:00:37.334ZINC_1794231879607_tj4dmj high resolved wazuh_alert - 2026-11-09T13:44:39.607ZINC_1794185340500_nd7bbw medium closed wazuh_alert - 2026-11-09T00:49:00.500ZINC_1794177398557_g7a615 medium open wazuh_alert - 2026-11-08T22:36:38.557Z Each row is one incident with its severity, its status, the kind of alert that raised it and the agent working on it (a dash means nobody yet). The newest are at the top. Quox’s answer also named the server and alert behind each open one, which it read from the same incidents.
What just happened
Section titled “What just happened”Quox and the terminal read the same incident list for your org. Reading changes nothing. Assigning, resolving or closing an incident is a separate step you take on purpose.