PracticeISCFree practice exam

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.

The ruleClassify a change as an emergency when immediate implementation is necessary to address a critical production threat before the normal process can reasonably finish. Follow the policy's emergency authorization, documentation, and review requirements.

Try one first

An organization's change management policy states: (1) standard changes must be scheduled during the weekly maintenance window (next window: Monday 2:00-4:00 AM, in 72 hours); (2) emergency changes may be implemented immediately outside the window when IT Security classifies a vulnerability as 'critical', emergency changes require written justification and a post-implementation CAB review within 48 hours. IT Security has just classified a newly discovered vulnerability in an internet-facing application as 'critical' because a public proof-of-concept exploit is available. The web application firewall (WAF) currently blocks known exploit signatures, but the vendor warns the WAF may not fully mitigate this vulnerability. Applying the vendor patch will require a 30-minute application outage and a database restart. Based on timing and the stated trigger, what is the most appropriate next action?
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.

Step by step

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

A company uses the following change-management categories: - Standard change: low-risk, routine, and preapproved - Normal change: nonroutine change that follows the usual review and approval process - Emergency change: change that must be implemented quickly to address an active incident or immediate high-risk exposure Which proposed action should be classified as an emergency change?
Hint

Focus on whether the change is responding to an active incident or immediate threat, not just whether the change is important.

Question 3

An organization policy requires prior Change Advisory Board (CAB) approval for all production changes. Which of the following best describes a limited exception that permits immediate implementation without prior CAB approval while still maintaining adequate change control?
Hint

Focus on which situations truly require immediate action for risk reduction and what compensating controls preserve accountability when prior approval is bypassed.

Question 4

Company X's IT change management policy categorizes changes as: standard (pre-authorized, low-risk repeatable), normal (requires a formal RFC and pre-implementation CAB approval), and emergency (implemented immediately to address critical threats, with documentation and retrospective CAB review). Security operations discovered active exploitation of a zero-day vulnerability in production web servers. The vendor released a hotfix; the team tested it briefly on a single lab server and decided to deploy the hotfix to all production web servers tonight to stop ongoing attacks. Deployment will require short reboots and brief user outages. The team did not wait for the next scheduled CAB meeting but documented the work and plans to obtain retrospective CAB approval. Under Company X's categories, how should this planned deployment be classified?
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?

Question 5

A company's payment system failed during business hours. To restore service, IT applied a vendor patch to production the same day under the company's documented emergency change procedure. The change was logged, a manager approved the expedited implementation, and a post-implementation review was completed the next business day. How should this production change be classified?
Hint

Focus on why the change was moved quickly and whether the company still used an approved change process.

Question 6

The organization's change management policy distinguishes Standard, Minor, Major, and Emergency changes. The policy allows an authorized on‑call senior systems administrator to take immediate corrective action for active incidents that threaten critical operations; such emergency changes must be logged, tested after implementation, and presented to the CAB for retrospective review. Major changes, by contrast, normally require CAB preapproval and testing in a maintenance window. Late on the Friday before payroll, monitoring detected an active exploit targeting the payroll application that would prevent employees from being paid. To avoid missed payroll, the on‑call senior systems administrator, who is authorized under the emergency procedures, applied a vendor security patch outside the maintenance window and temporarily disabled certain input‑validation checks so the payroll run could complete. The change was logged and a security incident ticket opened, but no prior CAB approval was obtained. Which classification best describes this change?
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.

Drill all 162 Change management questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

All Change management practice →

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.