ISC · Security and Confidentiality and Privacy · 10 practice questions
Compensating Controls for Unpatched Vulnerabilities
When a critical vulnerability creates exposure above risk tolerance, reduce exposure immediately rather than wait for a patch or confirmed compromise. Below, one scenario changes a single fact at a time to show which immediate control fits.
Try one first
Hint
Focus on what management should do before the permanent fix is available when the current risk exceeds tolerance.
Answer B. With a known, actively exploited critical vulnerability and no immediate patch, management should reduce exposure now by applying compensating controls to lower the likelihood or impact of exploitation while essential operations continue. Examples include restricting external access, disabling nonessential vulnerable features, deploying protective controls (for example WAF rules or network segmentation), and increasing logging and incident monitoring until the vendor patch is available. Because the risk is above tolerance, waiting or accepting the risk without interim controls is inappropriate.
Why not A: This is tempting because the vendor patch is the definitive solution, but the question asks what to do now. Waiting 10 days while the vulnerability is actively exploited would leave the organization exposed; interim compensating controls are needed to reduce immediate risk.
Why not C: Insurance is a risk-transfer tool that may cover losses after an incident, but it does not reduce the immediate likelihood of exploitation or prevent data loss. Since the current risk exceeds tolerance, relying solely on insurance without mitigating controls is not an appropriate immediate response.
Why not D: Accepting risk is only appropriate when management knowingly accepts the exposure. Here the risk is already above the company's acceptable level and exploitation is occurring in the wild, so temporary acceptance without mitigations would be irresponsible.
Same scenario, one fact changes
Base case
Harbor's customer portal stores PII. A critical SQL injection flaw affects its essential reporting module. Exposure exceeds risk tolerance; no compromise is confirmed. A tested vendor patch is due in 10 days. The portal must stay available. Targeted WAF rules can block the exploit now without disrupting operations. Access can also be limited to required users.
Answer: Deploy the targeted WAF rules immediately, enhance logging and alerts, and apply the vendor patch as soon as safely possible.
The WAF reduces exploitability now while preserving essential reporting. Monitoring supports detection, but neither monitoring nor patch planning alone blocks the exploit.
Before you open each one, predict the answer.
Change 1The tested vendor patch is available now and can be installed safely without disrupting operations.
Answer: Apply the vendor patch now and continue monitoring.
The permanent fix is now safe and available. There is no reason to leave the flaw unpatched behind temporary controls.
Change 2Targeted WAF rules cannot block this exploit.
Answer: Immediately restrict access to required users, enhance monitoring, and apply the vendor patch as soon as safely possible.
An ineffective WAF rule cannot compensate for the flaw. Restricting access reduces reachable attack paths while essential operations continue.
Change 3The vulnerable reporting module is nonessential rather than essential.
Answer: Temporarily disable the reporting module, enhance monitoring, and patch it before restoring it.
Disabling the nonessential module removes the vulnerable function from service without interrupting essential portal operations.
Key points
- Remember: A patch delay is not a mitigation delay; reduce exposure while the permanent fix is pending.
- No confirmed compromise does not justify waiting when exposure already exceeds risk tolerance.
- A WAF virtual patch blocks exploit traffic; it does not repair the vulnerable code.
- Choose controls that preserve essential operations, not necessarily every feature.
How the exam traps you
- Wait for the patch because no compromise is confirmed. Act on the known exposure now; confirmation of harm is not the trigger.
- Increase logging without using available preventive controls. Block exploit traffic, restrict access, or disable the vulnerable feature; use logging to support those controls.
- Keep the virtual patch indefinitely after a safe vendor fix becomes available. Apply the vendor fix promptly; temporary protection does not remove the underlying flaw.
Now the same facts as questions
Each question changes one fact from the one before. Watch which change flips the answer.
Question 1
Answer B. Right. This reduces exploitability now while preserving essential operations and retaining permanent remediation.
Why not A: Wrong. Above-tolerance exposure requires action before compromise is confirmed.
Why not C: Wrong. Logging alone does not block exploitation when a preventive control is available.
Why not D: Wrong. A feasible, less disruptive control preserves the required portal availability.
Question 2
Answer A. Right. The permanent fix is safe and available now.
Why not B: Wrong. Temporary controls do not justify delaying a safe, available permanent fix.
Why not C: Wrong. Confirmed compromise is not required to remediate known above-tolerance exposure.
Why not D: Wrong. Monitoring does not remove the vulnerability.
Question 3
Answer C. Right. Restricted access reduces attack paths while preserving required use.
Why not A: Wrong. Rules that cannot block the exploit do not reduce this exposure.
Why not B: Wrong. Available access restrictions provide preventive protection that monitoring alone does not.
Why not D: Wrong. Essential operations require feasible interim protection, not unmitigated exposure.
Question 4
Answer D. Right. Disabling the nonessential module removes the vulnerable function without stopping essential operations.
Why not A: Wrong. Logging leaves the vulnerable function available for exploitation.
Why not B: Wrong. Disabling only the nonessential module preserves essential portal operations.
Why not C: Wrong. Known above-tolerance exposure already warrants mitigation.
Question 2
Hint
Focus on which choice most directly reduces exposure created by an unpatchable system that still must stay online.
Answer C. This choice most directly reduces the system's principal exposures: broad reachability and weak privileged-access practices. Network restriction/segmentation and least-necessary connectivity shrink the attack surface and blast radius, while named privileged accounts with MFA increase accountability and reduce credential-based compromise; monitoring speeds detection and response. Because encryption at rest and insurance already exist, these compensating access controls deliver the highest near-term risk reduction.
Why not A: Insurance and formal risk acceptance address financial transfer and governance, not the underlying likelihood or scope of unauthorized access. The stem asks for the best mitigation while the system remains online, so transferring or accepting risk is not the most effective technical control.
Why not B: Better backups improve recovery and availability after an incident but do not materially reduce the immediate confidentiality and privileged-access weaknesses in an unpatchable, widely reachable system. They are valuable but not the highest-priority mitigation here.
Why not D: Field-level encryption can protect data at rest, but if too many users and shared privileged accounts can access the live application environment, encryption at storage does little to stop misuse. Fixing excessive connectivity and privileged access yields greater near-term risk reduction.
Question 3
Hint
Which choice most quickly reduces the server's exposure and the likelihood of unauthorized access now, without taking the service fully offline or relying only on financial transfer?
Answer D. Network-level isolation and layered access controls immediately reduce the server's attack surface and the likelihood of unauthorized access while allowing business users to continue required work. Restricting RDP to VPN endpoints or limited source IPs, enforcing MFA, and enabling enhanced logging/alerting are effective compensating controls that can be implemented quickly; longer-term fixes (vendor patching, encryption at rest) can proceed in parallel.
Why not A: Tempting as a quick technical action, but wrong because credential changes do not remove the exposed RDP interface or fix protocol-level weaknesses; attackers can still exploit an open service even with new passwords. In addition, changing vendor-supplied credentials may break vendor access or be impractical, and rotations alone do not materially lower breach probability.
Why not B: Tempting because it avoids near-term operational disruption and aligns with the patch timeline, but wrong because it leaves unencrypted PII exposed on an Internet-accessible service. Accepting the risk without implementing available, low-disruption network mitigations maintains a high probability of compromise and forfeits immediate reduction of exposure and detection capability.
Why not C: Tempting because insurance can address financial consequences, but wrong because it does not reduce the likelihood of a breach, prevent regulatory or reputational harm, or substitute for required technical controls. Policies may have coverage limits or exclusions tied to known vulnerabilities or unencrypted PII, so insurance alone does not mitigate the active confidentiality risk.
Question 4
Hint
Focus on reducing exposure to PHI now and check whether the incident response plan allows emergency, targeted changes rather than waiting for full confirmation or routine change windows.
Answer D. The vulnerability is high severity and could expose PHI; incomplete logging means the absence of confirmed exploitation does not eliminate risk. The incident response plan authorizes CISO-approved emergency changes to contain or mitigate active security incidents, so immediate, targeted compensating controls (for example, a WAF rule or disabling the plugin) are appropriate to reduce exposure while pursuing an emergency patch or vendor mitigation. This approach balances urgent risk reduction with controlled approval and minimizes data risk without waiting for forensic confirmation or the routine change window.
Why not A: Tempting because it prioritizes operational stability and the lack of confirmed exploitation, but incorrect: a high-severity flaw affecting PHI and incomplete logs justifies immediate containment and compensating controls rather than waiting through routine change approvals.
Why not B: May seem proactive but is incorrect because broad, non-targeted emergency changes do not directly mitigate the immediate high-risk vulnerability and can introduce operational risk; priority should be targeted containment of the affected plugin while pursuing an emergency patch.
Why not C: This appeals to those favoring minimally invasive responses; however, isolation and monitoring alone may not eliminate exposure and postponing compensating controls or emergency patching leaves PHI at unnecessary risk given the severity and logging gaps.
Question 5
Hint
Think about which immediate control directly prevents the current exploit, what investigative and legal steps are required when data is likely exfiltrated, and how to balance continuity with risk reduction.
Answer C. Option C balances immediate technical mitigation with investigation and the legal/notification obligations stated in the stem. Deploying a WAF rule is an appropriate compensating control to stop further exploitation while preserving business continuity; enhanced logging helps confirm scope; notification is required because forensics indicate likely exfiltration. The vendor's permanent patch should be applied when available as the definitive fix.
Why not A: Tempting because delaying notification can allow confirmation, but the stem explicitly states company policy and law require timely notification when personal information is likely compromised; postponing would violate those obligations.
Why not B: Tempting because taking the system offline stops access, but it's overly disruptive when an effective compensating control (the WAF) is available; the stem implies the organization should use least-disruptive reasonable mitigations while investigating.
Why not D: Tempting because credential hardening and encryption are useful generally, but they do not address a SQL injection that permits arbitrary database queries and data exfiltration; omitting the WAF leaves the vulnerability exploitable and fails to meet the immediate mitigation need.
Question 6
Hint
Compare the provided post-mitigation residual risk scores and implementation time/operational impact; prefer rapid, preventive compensating controls that significantly lower likelihood while keeping services running.
Answer C. Option C provides rapid, preventive compensating controls that materially reduce the likelihood of exploitation (from 4 to 1) while preserving customer-facing availability. The controls are implementable quickly (within 48 hours) and impose low operational disruption, yielding the best practical balance of reduced residual risk and business continuity while the vendor patch is pending.
Why not A: Monitoring and alerts are useful for detection but do not reduce the vulnerability's likelihood; they leave the high baseline risk unchanged while awaiting the patch, which is inconsistent with the requirement to reduce risk now.
Why not B: Encryption at rest can reduce impact for some exposures but often does not prevent API-level exfiltration (where decrypted data may be returned by the API), and it typically takes longer to deploy and may require vendor changes, so it is not the best immediate mitigation.
Why not D: Removing the service eliminates the data-access risk but also causes significant outage and business harm. Given the goal to preserve availability until the vendor patch, this overly disruptive option is not the most appropriate immediate response when less-disruptive effective controls exist.
Common questions
Should mitigation wait until exploitation is confirmed?
No. Harbor's exposure exceeds risk tolerance even without a confirmed compromise. Available controls should reduce that exposure immediately.
Is a WAF virtual patch a permanent fix?
No. It can block exploit traffic while the code remains vulnerable. Harbor should still apply the vendor patch as soon as safely possible.
What if a WAF rule is unavailable for an unpatched vulnerability?
Use another feasible control that reduces exposure. In Harbor's scenario, restrict access to required users and increase monitoring until the patch can be applied.
Watch it solved
A full CPA ISC task-based simulation on Mitigation, worked step by step.
IT Risk-to-Control Mapping | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Mitigation
- Stolen Credentials: When MFA Is the Best Mitigation
- Full-Disk Encryption on Laptops: Protection and Limits
- Suspected Data Exfiltration: Contain and Preserve Evidence
- Vendor Privileged Access: Standing Rights vs. Time-Bound Access
- Least Privilege and Masking for PII: CPA ISC
- Risk Responses: Mitigation, Transfer, Acceptance, Avoidance
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.