Common Remediations¶
Findings
Common Remediations group fixes that resolve multiple findings at once — prioritized by blast radius so your team fixes the highest-impact issues first.
Overview¶
Many security findings share the same root cause. For example, enabling MFA on an AWS account might resolve dozens of individual findings. Common Remediations identifies these patterns and presents them as single actions with maximum impact.
Why it matters¶
| Approach | Effort | Impact |
|---|---|---|
| Fix findings one by one | High — repetitive work | Low — one issue at a time |
| Common Remediations | Low — one fix, many findings | High — blast radius prioritized |
Work smarter, not harder. Instead of closing 50 individual findings, apply one remediation that addresses the shared root cause.
What you'll see¶
Each common remediation shows:
- Title — What needs to be fixed
- Findings resolved — How many findings this fix addresses
- Blast radius — How broadly the fix impacts your environment
- Priority — Recommended order based on severity and compliance impact
- Guidance — Steps to apply the remediation
Who uses it¶
- Security engineers — Efficient remediation sprints
- Compliance managers — Demonstrating systematic fix progress for audits
- Team leads — Assigning high-impact work to the right people
How to use it¶
- Navigate to Common Remediations in the platform
- Review remediations sorted by blast radius
- Select a remediation and review the affected findings
- Apply the fix in your environment
- Mark as complete — linked findings update automatically on next sync
Related¶
- Findings → How It Works — The findings lifecycle
- AI Assistant — Ask for help applying a remediation