Chapters0/54 ▾
- 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 7 · Lesson 4 of 5
Compensating controls, exceptions, acceptance and transfer
1 min read
A compensating control is an alternative measure used when the primary fix cannot be applied yet: a proxy or web application firewall rule that filters the exploit request, tight access lists in front of an unsupported appliance, or a segment that admits only one imaging workstation and logs everything else.
These buy time by narrowing who can reach the flaw. They do not repair it, an attacker who finds a request shape the rule misses is back at the original defect, and the one permitted workstation is itself a route in if it is compromised.
So the finding stays open, the control is documented, and the patch or replacement stays on plan.
- Exception: when a fix conflicts with business needs or an internal standard, the decision goes to the risk owner, with justification, compensating controls, an expiry date and a review.
- Acceptance: a documented risk-owner decision to take no action, with a review date. An analyst cannot accept risk alone in a ticket comment.
- Transfer: a contract or insurance moves who pays, not the vulnerability, so a third-party finding stays tracked with the provider's fix commitment.
- Compliance scope: when an obligation applies, such as one inherited through a payment card contract, the control, its approval, scope and review date must be recorded as evidence.
Check yourself
1. An unsupported medical imaging controller carries a serious finding that cannot be patched. The team moves it to a segment that permits only the imaging workstation's traffic and logs every other attempt. A manager asks whether the risk is now resolved. Which answer is accurate?
2. A web application flaw cannot be patched for six weeks, so the team writes a blocking rule on the filtering layer in front of the application and confirms the rule stops the known attack request. The vulnerability manager asks what has actually changed. Which statement is accurate?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, FIRST: CVSS v4.0 Specification Document, FIRST: CVSS v4.0 User Guide, CISA: Known Exploited Vulnerabilities Catalog
CompTIA CySA+ cheat sheet: every key fact on one page →