ISC · Information Systems and Data Management · 6 practice questions
Emergency Change Criteria: When an Active Exploit Cannot Wait
Use the emergency-change path when waiting for normal approval would prolong a critical production threat. Below, follow a payment-system patch from the urgency test through emergency authorization and retrospective review.
Try one first
Hint
Focus on how the organization’s policy defines an 'emergency' trigger and what it allows when IT Security classifies a vulnerability as critical, balance immediate exploitation risk against downtime.
Answer B. IT Security has classified the vulnerability as 'critical' and the policy explicitly allows emergency changes to be implemented immediately in that case. A public proof-of-concept exploit exists and the vendor warns the WAF may not fully mitigate the vulnerability, so the risk of waiting outweighs a 30-minute outage. The policy-prescribed emergency path (immediate deployment with written justification and a post-implementation CAB review within 48 hours) is therefore the most appropriate action.
Why not A: This option minimizes downtime but ignores the policy's emergency trigger and the immediate exploitation risk. With a public proof-of-concept and vendor caution that the WAF may not fully mitigate the issue, waiting 72 hours leaves an unacceptable exposure despite the maintenance window.
Why not C: A temporary WAF rule may provide some protection, but the vendor warned it may not fully mitigate the vulnerability and a PoC exists, so relying solely on WAF is insufficient. The policy permits immediate emergency remediation when a vulnerability is classified 'critical.'
Why not D: This choice prioritizes pre-approval but conflicts with the stated policy: emergency changes for 'critical' vulnerabilities are allowed immediately and require only a post-implementation CAB review within 48 hours, not prior CAB approval.
Step by step
- Read the emergency policy
At one company, emergency changes require designated approval, documentation, a rollback plan, and retrospective Change Advisory Board (CAB) review. Normal changes need prior CAB approval; standard changes follow preapproved procedures.
- Identify the production threat
Attackers are exploiting the company's production payment system, causing transaction failures and potential data exposure. A vendor patch is available, no workaround exists, and waiting for tomorrow's CAB meeting would prolong the attack.
- Apply the waiting test
Immediate mitigation is necessary, so classify the patch as an emergency change rather than waiting for normal approval. Being vendor-supplied does not make the patch a preapproved standard change.
- Obtain designated emergency approval
The policy names the change manager as the emergency approver, and that person is available now. Obtain that approval before deployment; Operations' informal approval is not a substitute.
- Prepare and deploy promptly
Prepare the required rollback plan and perform feasible expedited testing before deployment. The patch requires five minutes of downtime, but that brief restart does not justify extending the active exposure.
- Document and review the change
Document the threat, authorization, implementation, and results, then submit the change for the required retrospective CAB review. The emergency path shortens the approval cycle without eliminating oversight.
Key points
- Remember: The emergency trigger is the risk of waiting, not the speed or simplicity of the patch.
- A vendor patch is not automatically a preapproved standard change.
- Emergency authorization replaces the normal approval timing, not all change controls.
- A short restart does not outweigh an ongoing critical exposure.
How the exam traps you
- Wait for the next CAB meeting because production changes require approval. Use the policy's emergency approval path when waiting would prolong active exploitation.
- Treat a vendor patch as standard because it needs only a brief restart. Standard changes require preapproval; brief downtime does not establish that status.
- Deploy immediately on Operations' informal approval and obtain authorization afterward. Obtain approval from the designated emergency approver before deployment when the policy requires it.
Question 2
Hint
Focus on whether the change is responding to an active incident or immediate threat, not just whether the change is important.
Answer D. An emergency change is used when a change must be made quickly to respond to an active incident or an immediate high-risk exposure. Blocking malicious traffic during an active ransomware attack fits that definition because waiting for the normal approval cycle could increase damage. The other choices are routine or planned changes that can follow standard or normal procedures.
Why not A: This is tempting because security patches can feel urgent. However, the fact pattern says the patch is preapproved, routine, and performed in a scheduled window, which makes it a standard change rather than an emergency change.
Why not B: This is a realistic business request, but it is neither urgent nor tied to an active incident or immediate high-risk exposure. It would typically be handled as a normal change, or possibly a standard change if it were routine and preapproved, but not as an emergency change.
Why not C: This choice may attract candidates who focus on the operational importance of a workflow change. But it is planned for next month and goes through normal preparation and testing, so it fits the normal change process, not the emergency category.
Question 3
Hint
Focus on which situations truly require immediate action for risk reduction and what compensating controls preserve accountability when prior approval is bypassed.
Answer D. Change-control frameworks permit a narrowly defined emergency-change exception for time-sensitive threats, such as an actively exploited vulnerability. Such emergency deployments must follow the organization's emergency-change procedure and include compensating controls, prompt documentation, retrospective CAB review, post-implementation review, and rollback/mitigation, to preserve oversight while reducing time-to-remediation.
Why not A: Plausible because maintenance windows are used for scheduled changes, but timing alone does not substitute for required approvals; only preapproved routine-change categories or delegated authority permit bypassing CAB review, not the maintenance window by itself.
Why not B: Tempting because vendors often supply and test fixes and may urge immediate installation, but vendor testing and recommendation do not replace the organization's responsibility to assess risk in its environment, test or accept the risk, and follow internal approval or retrospective-review processes before production deployment.
Why not C: Appealing since cosmetic changes seem low risk, but even UI tweaks can affect usability, integrations, or accessibility and may have unintended consequences; they should follow the organization's delegated-change or approval process rather than a blanket bypass of CAB oversight.
Question 4
Hint
Ask why the team skipped normal RFC/CAB pre-approval, which policy factor (need for immediate mitigation vs. routine testing/scheduling) controls the change category?
Answer D. The deployment was prompted by active exploitation and required immediate mitigation, so it fits the emergency-change category. The team bypassed the RFC/pre-approval process and will seek retrospective CAB review, the hallmark of emergency changes; brief lab testing and an overnight window do not convert an urgent response into a normal or standard change.
Why not A: Plausible because some policies allow a normal change to be expedited with prior ad-hoc on-call CAB approval; wrong here because the stem states the team did not obtain prior ad-hoc approval and instead plans retrospective review, which aligns with an emergency change rather than an expedited normal change.
Why not B: Tempting because the team did brief testing and planned an overnight deployment, which resemble routine operations; wrong because standard changes must be pre-authorized and low-risk, this deployment responds to an urgent security incident and bypassed pre-approval, so it cannot be a standard change.
Why not C: Appealing since normal changes follow RFC/CAB procedures and the team did testing and scheduling; incorrect because normal changes are not used for immediate mitigation of an active exploitation when the team bypasses pre-approval, that situation is classified as an emergency.
Question 5
Hint
Focus on why the change was moved quickly and whether the company still used an approved change process.
Answer A. This is an emergency change because it was implemented under the company's documented emergency change procedure to restore service quickly during an outage. Although expedited, it was logged, approved by a manager, and reviewed afterward, indicating a controlled emergency change rather than an unauthorized or routine change.
Why not B: Tempting because vendor patches can be routine, but standard changes are preapproved, low‑risk, repeatable activities performed without emergency escalation; this patch was applied urgently under an emergency procedure.
Why not C: Tempting because the patch reached production quickly before the normal change cycle, but it is incorrect since the company used a documented emergency process and obtained manager approval, so the change was authorized.
Why not D: Tempting because many production changes follow normal approval and scheduling, but this change was made urgently to address an active outage under an emergency procedure, not via the normal change path.
Question 6
Hint
Consider whether the person who acted had authority to implement immediate fixes during an active incident and what the policy requires after such an action.
Answer B. The facts describe an active incident threatening a critical business process (payroll) and an authorized on‑call senior systems administrator applying an immediate fix. The change was logged and ticketed, matching the organization's emergency process that permits immediate implementation with required post‑implementation testing and retrospective CAB review. Therefore it is an Emergency change rather than a Standard, Major, or outright unauthorized action.
Why not A: This is tempting because patches are often routine and only require logging. It fails here because the change was ad hoc and taken in response to an active exploit, and it involved disabling controls, which goes beyond the preauthorized, scripted Standard category.
Why not C: This distractor appeals because the change affected payroll and altered validation checks, which seem significant. It is incorrect because the policy explicitly allows immediate emergency actions by authorized personnel during active incidents; such actions do not require prior CAB preapproval but instead require post‑implementation testing and retrospective CAB review.
Why not D: This seems plausible because the change occurred outside the maintenance window and disabled validation. It fails because the on‑call senior systems administrator had emergency authority and the change was logged and ticketed, indicating it followed the emergency process rather than being an unauthorized action.
Common questions
When does a security patch qualify as an emergency change?
It qualifies when immediate action is necessary to address a critical production threat before normal approval can reasonably finish. In this example, waiting would prolong active exploitation of the payment system.
Does an emergency change still need approval?
Yes. Here, the designated emergency approver must authorize deployment before implementation. Retrospective CAB review follows; it does not replace that required authorization.
Is a vendor security patch a standard change?
Not automatically. Standard changes follow preapproved procedures. This patch uses the emergency path because active exploitation makes waiting unsafe, not because the vendor supplied it.
Watch it solved
A full CPA ISC task-based simulation on Change management, worked step by step.
Change Management: Approval & Segregation | CPA ISC 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 Change management
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.