PracticeISCFree practice exam

ISC · Information Systems and Data Management · 6 practice questions

When Should You Apply an Emergency Security Patch?

A critical, actively exploited vulnerability on an internet-facing system calls for emergency patching, not the next monthly window. Below: follow a customer portal from the vendor alert through testing, approval, deployment, and verification.

The ruleUse the emergency change process for a critical, actively exploited vulnerability affecting internet-facing systems. Expedite testing and obtain required approvals, with a rollback plan and post-deployment validation, rather than waiting for the routine maintenance window.

Try one first

A financial services firm operates internet-facing production web servers that host customer portals. The vendor released a security patch today for a remote-code-execution vulnerability rated CVSS 9.8; a public proof-of-concept and active in-the-wild exploitation have been reported. The patch is available but has documented cases of causing service disruptions in some configurations; standard regression testing takes about 48 hours. The organization's change-management policy normally applies patches during a monthly maintenance window (next window in 10 days), but the policy also includes an emergency (out-of-band) change process that can be used with CISO approval. The security team recommends applying the patch immediately via the emergency process; operations prefers waiting for the scheduled window. What is the most appropriate timing/trigger for applying the patch to these internet-facing production web servers?
Hint

Weigh the vulnerability's severity, the existence of a public proof-of-concept and active exploitation, the exposure of affected systems (internet-facing), and whether an emergency change process with required approvals is available.

The timeline

  1. Before Day 0A financial services firm schedules routine patching for Day 10.

    Its internet-facing customer portal normally follows a monthly maintenance cycle. Standard regression testing takes about 48 hours.

  2. Day 0: vendor alertThe vendor releases a patch for a critical remote-code-execution vulnerability affecting the portal.

    A public proof of concept and active exploitation are reported. Some configurations experience service disruptions from the patch.

  3. Day 0: risk assessmentSecurity triggers the emergency change process instead of waiting until Day 10.

    Critical severity, active exploitation, and internet exposure drive the decision. The firm need not wait until its own portal is attacked.

  4. Day 0: deployment preparationThe team performs expedited testing, documents the change, and prepares a rollback plan.

    Coordinate stakeholders and obtain the required CISO approval before deployment. Emergency timing does not eliminate operational safeguards.

  5. Day 0: emergency deploymentThe team promptly patches the affected production web servers through the approved emergency process.

    Do not stop at a small pilot and leave the remaining servers exposed until Day 10.

  6. Immediately after deploymentThe team verifies patch installation and confirms that the customer portal works.

    Record deployment results and validate remediation through vulnerability management. Starting the installation is not proof that the vulnerability is fixed.

Key points

  • Remember: emergency patching changes the timetable, not the need for change controls.
  • Active exploitation elsewhere is enough; do not wait for evidence that your own portal has been attacked.
  • Known disruption risk calls for expedited testing and rollback planning, not an automatic delay until the monthly window.

How the exam traps you

  • Wait for the monthly window to complete standard testing. Use expedited testing and emergency approval because the exposed vulnerability is already being exploited.
  • Patch immediately without testing, approval, or a rollback plan. Move quickly through the emergency process, not around it.
  • Patch a small pilot now but defer the remaining servers until the monthly window. Use pilot results to support prompt rollout; do not leave the remaining exposed servers waiting.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

A company uses a monthly patch cycle for infrastructure devices. On Tuesday, the vendor for the company's internet-facing firewall releases a patch for a newly disclosed vulnerability rated critical. Industry alerts indicate active exploitation is already occurring, and internal testing shows the patch will not disrupt the current firewall configuration. Under a sound IT infrastructure patch-management process, when should the company apply the patch?
Hint

Consider what should happen when a vulnerability affects an internet-facing device and active exploitation is already known.

Question 3

A midsize company operates a mix of on‑premises servers. A subset of those servers hosts an internet-facing customer portal that stores personally identifiable information (PII) and currently runs an OS version whose vendor has announced end-of-support (no more security patches) in nine months. Company policy and applicable regulations require that internet-facing systems storing customer PII must remain on vendor-supported platforms. Separately, (1) three internal application servers have averaged 85% CPU utilization for the past three months, (2) a group of legacy servers has incurred maintenance/support costs equal to about 55% of estimated replacement cost over the last 12 months, and (3) a redundant disk has failed in a noncritical database server but redundancy prevented data loss. Which event should trigger immediate action (such as expedited replacement, isolation, or other mitigation) to maintain security and compliance?
Hint

Focus on which event creates a fixed, external deadline that stops security patches and can cause regulatory noncompliance for internet-facing systems.

Question 4

The company's IT infrastructure policy states: (a) if average CPU utilization for a server exceeds 70% over any 30-day period, IT must begin procurement of additional compute capacity and schedule a hardware expansion in the next maintenance window (within 10 business days); (b) if available storage falls below 15% for two consecutive weeks, IT must expand storage or move data to longer-term storage. Current metrics for the primary on-premises database server: 30-day average CPU utilization = 70.5% (with occasional short spikes to 95%); available storage = 15.5% and has averaged 15.5% for the past three weeks. Based on the policy and metrics, which action should the IT manager take now?
Hint

Compare the 30-day averages to the policy thresholds and apply the policy's specified timing for any trigger that is met; short spikes do not override the 30-day average.

Question 5

A company monitors the storage environment that supports its customer order system. Over the last 3 months, storage utilization increased from 69% to 87%, overnight backup jobs have started running into the next business day, and users report slower retrieval of archived order data. Assuming no unusual one-time event caused the increase, what should this pattern trigger now?
Hint

Look for the option that responds to a sustained infrastructure trend before the resource is completely exhausted.

Question 6

A company uses baseline metrics to monitor the performance of its critical infrastructure. In 20X6, it migrated a major application to a new virtual server environment and changed the related storage configuration. The migration is complete, the environment is stable, and users are processing normal transaction volumes. When should IT staff establish the new baseline metrics for future monitoring of this updated infrastructure?
Hint

Focus on what a monitoring baseline is supposed to represent: expected performance in the current environment during ordinary operations.

Drill all 157 IT infrastructure 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 should a security patch bypass the monthly maintenance window?

Use emergency change handling when a critical vulnerability is actively exploited and affects internet-facing systems. The portal's exposure and active threat make waiting for the monthly window too risky.

Should I delay an emergency patch if it could disrupt service?

Known disruption risk does not justify waiting for the routine window in this scenario. Perform expedited testing, coordinate deployment, and prepare a rollback plan.

Does emergency patching still require approval and testing?

Yes. This company's policy requires CISO approval, and the response includes expedited testing, rollback planning, and post-deployment validation.

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 IT infrastructure

All IT infrastructure 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.