Built-in finding kinds
| Kind | What it means | Default severity |
|---|---|---|
unowned | No owner assigned | high |
stale | No use in ≥ 90 days | medium |
orphaned | Owner is inactive / deleted user | high |
over-privileged | Grants match *:* or a suppressed set of dangerous verbs | high |
unrotated | Key / secret older than the policy allows | medium |
unused-privilege | Granted permissions the identity never actually used | low |
cross-account-trust | Trust policy allows a non-owned account | high |
long-lived-key | Static key with no expiry | medium |
Filtering
NHIG → Findings exposes filters for severity, kind, source, and age. Common views:- High-severity, unresolved — the default landing page.
- Over-privileged in AWS —
kind=over-privilegedfilter + sourceaws. - Older than 30 days — the “Stale” tab.
Remediation
Each finding has one or more suggested remediations:- Assign owner — for
unowned - Archive — for
staleororphaned - Right-size policy — for
over-privileged(creates a proposed policy diff) - Rotate now — for
unrotated(calls into Secrets Manager if the secret is under SM management) - Add to review campaign — everything else
Suppression
Some findings are known-good (a break-glass account is intentionally over-privileged). Open the finding in the UI and click Suppress — enter a reason and an expiry so the exception itself expires. Suppressed findings show up on the risk view labelled with the reason and the expiry — auditors can see intentional exceptions.Related
Ownership
Most first-scan findings are
unowned — fix that first.Access reviews
Findings that survive suppression get pulled into campaigns.