Status, level, category, owner
Four fields change in a single row at the top of the case; every change lands in the activity history.
CASE Findings with an owner and a closing reason
Cases
Every finding is a case with a number, severity, category, owner, description and a step-by-step remediation. Comments, attachments and a PDF summary live on the same record.
Screenshots are taken from a demo tenant; organisation names and data are entirely fictional.
The case screen has two panes: a filterable list on the left and the selected case on the right. A "Subdomain takeover confirmed" case, for example, explains what is exposed and proposes four steps: remove the CNAME, recreate the bucket in your own account if you cannot, add DNS clean-up to the decommissioning checklist, and sweep the zone for other orphaned CNAMEs.
What it does
@mention comments
Pull a colleague into the case, attach files, follow the case; the notification goes to the right person.
Closing with a reason
Resolved, risk accepted or false positive. The reason is recorded and the same finding will not alert again.
How it works
-
01
Open
The case opens via a playbook or by hand, with the raw record and evidence attached.
-
02
Assign
An owner and priority are set; tags (Takeover, Patch Required, Leak) make filtering easy.
-
03
Close
The fix is applied, the case closes with its reason and a PDF summary is exported.
What you get
- "Who was following this?" stops being a question.
- Audits get evidence case by case.
- False positives are closed once and do not return.
Scenarios featuring this module
Employee credentials in a stealer log
An infostealer on an employee's personal device exfiltrated credentials and an active session cookie for the corporate VPN portal. The record surfaced inside a bulk sale package on …
4 modules
Other modules
Next step
What shows up on your own surface?
In a 30-minute session we run a live scan against your own domains.