CRISC · Question #253
One of an organization's key IT systems cannot be patched because the patches interfere with critical business application functionalities. Which of the following would be the risk practitioner's…
The correct answer is A. Additional mitigating controls should be identified. When patching critical systems interferes with essential business functions, the best recommendation is to implement alternative compensating controls to mitigate the unpatched vulnerabilities. This allows the system to remain operational while addressing the increased risk.
Question
One of an organization's key IT systems cannot be patched because the patches interfere with critical business application functionalities. Which of the following would be the risk practitioner's BEST recommendation?
Options
- AAdditional mitigating controls should be identified.
- BThe system should not be used until the application is changed
- CThe organization's IT risk appetite should be adjusted.
- DThe associated IT risk should be accepted by management.
How the community answered
(16 responses)- A81% (13)
- C13% (2)
- D6% (1)
Why each option
When patching critical systems interferes with essential business functions, the best recommendation is to implement alternative compensating controls to mitigate the unpatched vulnerabilities. This allows the system to remain operational while addressing the increased risk.
If patches cause critical application functionality issues, the system remains vulnerable. Identifying and implementing additional mitigating controls (e.g., network segmentation, intrusion detection, hardening configurations, application-level controls) can reduce the likelihood or impact of exploitation without disrupting the critical business application.
Prohibiting the use of a key IT system until the application is changed is often impractical and can severely disrupt critical business operations, making it an extreme and often unacceptable recommendation.
Adjusting the organization's IT risk appetite is a strategic decision that changes the acceptable level of risk, rather than a direct technical or operational control recommendation for a specific identified vulnerability.
Accepting the risk should only be considered after all viable mitigation options have been explored and determined to be unfeasible or too costly, and it requires formal approval, not as a primary best recommendation for an unpatched critical system.
Concept tested: Risk mitigation strategies, compensating controls
Source: https://learn.microsoft.com/en-us/compliance/regulatory/risk-management-framework#step-4-implement-and-monitor-risk-response
Topics
Community Discussion
No community discussion yet for this question.