Security findings

A finding is one problem on one resource, with everything you need to decide and act in a single place.

What a finding contains

Every finding carries the resource, the evidence, why it matters, the fix, the owner, the effort to resolve, and when it was first and last seen. There is no hunting across consoles for context.

Fix first

The Fix first list ranks open findings by risk and cost together, so you work the highest-impact items first rather than sorting thousands of alerts by hand. Identity findings sit alongside the infrastructure they can reach, because identity is part of security.

Triage

For each finding you can:

• Assign it to an owner (routing can do this automatically — see SLAs and ownership).
• Raise a ticket in Jira or ServiceNow, read back when closed.
• Fix it through governed remediation.
• Accept the risk as a tracked exception with an approver and an expiry.

Every triage step is written to the audit trail.

Verified closure

A finding fixed through remediation is only marked resolved once the next scan confirms the intended state — it is never assumed. Findings that come back are surfaced again rather than silently reopened.

Where findings come from

Posture rules, ingested native findings, identity risk and CVE detection all produce findings on the same list with one severity scale.