Remediation actions
Every finding ships with a prioritized remediation plan: control class, suggested change, and the evidence that justifies it.
Key points
- Remediations are decision-support, not auto-apply — a human must approve each one.
- Each action links back to the finding(s) and the transcripts that produced it.
- Actions are versioned alongside the run that generated them.
- Export to JIRA, Linear, or PagerDuty via the integrations menu.
01
Action types
- Control upgrade (keyword filter → semantic classifier).
- Scope narrowing (reduce tool allowlist).
- Budget enforcement (token cap, rate limit).
02
Workflow
- Triage in the findings inbox.
- Assign to the owning service team.
- Verify by re-running the same scenario after the fix lands.