Chapters0/54 ▾
0 of 54 lessons finished
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 10 · Lesson 4 of 5
Risk acceptance, exceptions, action plans and escalation
1 min read
Some findings cannot be fixed on schedule, and the report must make the resulting decision visible. A risk acceptance stands only when the record states the risk being accepted, the named owner with authority to accept it, the measures in place and a review date.
Without an accepting owner and a date, it is just an unremediated finding that stopped being tracked.
A deviation from a hardening standard, such as keeping an unsupported database release for two more cycles, becomes a time-bound exception naming the approver, compensating controls, expiry and residual risk. Suppressing the finding or rewriting the standard to match reality removes the control.
Inhibitors to remediation, such as a vendor contract that voids support if the customer patches an appliance, change how the risk is treated, not whether it is reported: recommend a compensating control and a documented exception while the supported fix is pursued with the vendor.
Every action plan row needs an accountable individual, its dependencies and what happens if the date slips; a team name and a quarter-end date give nobody a reason to act this week.
When a critical finding passes its agreed date twice, the analyst escalates along the documented path to the owner's management and the risk function, attaching the record of attempts. Publishing it company-wide, patching someone else's system or treating silence as acceptance all bypass the accountable decision-maker.
Check yourself
1. A critical internet-facing finding has passed its agreed remediation date twice. The system owner acknowledges the emails but schedules no work. What is the correct next step for the analyst?
2. A development team wants to keep running an unsupported database release for two more release cycles, which the hardening standard forbids. How should this deviation be communicated and recorded?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, NIST SP 800-40 Rev. 4: Guide to Enterprise Patch Management Planning
CompTIA CySA+ cheat sheet: every key fact on one page →