Remediation Planning
Turn analysis output into prioritized remediation plans with clear ownership and sequencing.
Use this workflow to convert findings into an execution plan that engineering and security teams can actually run.
Planning Inputs
Risk and Exposure
- Active exploitation evidence.
- Asset criticality and external exposure.
- Potential blast radius.
Execution Constraints
- Patch availability and testing effort.
- Maintenance windows and change controls.
- Team bandwidth and dependencies.
Prioritization Matrix
| Priority | Conditions | Target timeline |
|---|---|---|
| P1 Immediate | Active exploitation + critical external exposure | 24 hours |
| P2 Urgent | No active exploitation but high business impact | 72 hours |
| P3 Planned | Low exposure or compensating controls available | 7-14 days |
Plan Generation Prompt
bash
Convert this analysis into a remediation plan with:
- priority tier per issue,
- required owner (SOC, platform, app team),
- immediate controls,
- long-term fixes,
- rollback/risk notes.
Minimum Plan Quality
- Every action has an owner and due window.
- Dependencies are explicit (testing, approvals, outages).
- Temporary mitigations are tracked until permanent fix lands.
- Residual risk is documented for leadership.