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.
Try one first
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.
Answer A. Given the high severity (CVSS 9.8), the availability of a public proof-of-concept, active in-the-wild exploitation, and that the affected systems are internet-facing, the immediate risk outweighs waiting for the routine window. Use the emergency (out-of-band) change process with required approvals (e.g., CISO), undertake expedited testing and stakeholder coordination, and prepare a rollback and post-deployment validation plan to balance speed with operational safety.
Why not B: Tempting because it follows standard change-management discipline and reduces the chance of disruption; however, it is incorrect here because active exploitation of a critical internet-exposed RCE makes waiting 10 days (and full routine testing) unacceptably risky, an out-of-band emergency remediation is warranted.
Why not C: Tempting because it maximizes speed against exploitation; however, it is wrong because bypassing testing, approvals, and rollback increases the risk of causing widespread outages or irreversible problems. The emergency process exists to enable rapid but controlled deployment with necessary safeguards.
Why not D: Tempting because it combines temporary risk reduction with validation steps and appears to limit disruption; however, it is incorrect here because compensating controls can be incomplete or bypassed and a pilot leaves most production servers exposed while active exploitation continues. When critical internet-facing assets are under active attack, a full emergency remediation is appropriate.
The timeline
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Question 2
Hint
Consider what should happen when a vulnerability affects an internet-facing device and active exploitation is already known.
Answer C. A critical patch for an internet-facing infrastructure component should be expedited when active exploitation is already occurring. Because internal testing shows the patch will not disrupt operations, the appropriate trigger is emergency change handling based on severity, exposure, and active threat activity. A normal monthly cycle is too slow for this situation.
Why not A: This is tempting because disciplined change management usually favors scheduled windows. However, emergency change procedures exist for high-risk situations like a critical, actively-exploited vulnerability; waiting for the normal cycle needlessly prolongs exposure.
Why not B: This may appeal to candidates who prefer coordinating large patch batches. But patch priority should be driven by risk: an internet-facing firewall with a critical actively-exploited vulnerability is typically far more urgent than routine server or endpoint updates.
Why not D: This distractor sounds evidence-based, but patching is a preventive control. Once a critical vulnerability is known and active exploitation is reported, the trigger to act is already present; waiting for device-specific compromise increases unnecessary risk.
Question 3
Hint
Focus on which event creates a fixed, external deadline that stops security patches and can cause regulatory noncompliance for internet-facing systems.
Answer A. End-of-support for an OS on internet-facing systems that host PII is an external, fixed deadline after which security patches and vendor fixes stop. That materially increases vulnerability and can violate company policy and applicable regulations, so it requires immediate remediation planning and expedited mitigation (replacement, isolation, or compensating controls) to maintain security and compliance. The other items are operational or economic concerns that typically lead to planned capacity, budgeting, or routine repair actions rather than an immediate compliance-triggered response.
Why not B: Sustained high CPU is a valid availability and performance concern and may prompt capacity increases or optimization, which makes it tempting, but it does not create the same fixed security/compliance deadline as vendor end-of-support for internet-facing PII systems.
Why not C: Rising maintenance costs are an economic signal that replacement may be justified, but this is typically handled through budgeting and planning rather than immediate emergency action unless there is also a security or availability failure.
Why not D: Hardware failure is important to address, but when redundancy preserved data and service, the appropriate response is prompt repair during the routine maintenance window rather than an immediate overhaul; it doesn't pose the same imminent compliance risk as loss of vendor security support on exposed PII systems.
Question 4
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.
Answer D. The CPU trigger is met: the 30-day average CPU utilization is 70.5%, which exceeds the 70% threshold. Under the policy IT must begin procurement and schedule the hardware expansion in the next maintenance window within 10 business days. The storage trigger is not met because available storage averages 15.5% (above the 15% threshold) for the past three weeks, so no storage action is required now.
Why not A: Cloud migration is tempting as a long-term fix but is a major project and not the policy-prescribed immediate action. Additionally, the storage trigger is not met, and migration does not replace the requirement to begin procurement and schedule expansion within the required 10 business days.
Why not B: This is tempting because it acknowledges the capacity need while seeking cost savings through consolidation. It is wrong because the policy requires scheduling the expansion in the next maintenance window within 10 business days once the 30-day CPU threshold is exceeded; delaying to quarter-end violates the required timing.
Why not C: This option is tempting as a cautious operational approach, mitigations and monitoring can address transient load. It fails because the policy is explicit: once the 30-day CPU average exceeds 70% IT must begin procurement immediately; waiting a month and relying solely on mitigations does not meet the mandatory requirement.
Question 5
Hint
Look for the option that responds to a sustained infrastructure trend before the resource is completely exhausted.
Answer C. Sustained growth in utilization combined with backup jobs running into business hours and user-facing performance degradation indicate the storage environment is under capacity and operational strain. IT should proactively review capacity and plan expansion or optimization before service levels decline further. Waiting until full exhaustion increases risk of outages and data loss.
Why not A: Access reviews address authorization risks but do not explain sustained storage growth or backup windows spilling into business hours. Slower retrieval in this scenario is far more plausibly caused by capacity and performance constraints than by excessive privileges.
Why not B: This is tempting for candidates who think action is only required at full exhaustion. However, backup overruns and user performance problems show the system is already strained; waiting until 100% would raise the risk of operational failures. Proactive capacity planning is the appropriate trigger.
Why not D: While application changes can sometimes cause storage growth, the facts describe an ongoing capacity trend with operational impacts rather than a recent code change. The immediate, practical response is an infrastructure capacity review, not a development approval process.
Question 6
Hint
Focus on what a monitoring baseline is supposed to represent: expected performance in the current environment during ordinary operations.
Answer C. A performance baseline should be based on observed system behavior during normal operations in the current environment. Once the new infrastructure is stable and handling ordinary workloads, IT can capture meaningful metrics for future comparisons. Relying on vendor specifications, waiting for an incident, or delaying to include longer calendar periods would not produce a representative operational baseline.
Why not A: Vendor specifications are planning estimates and may not match actual production behavior; a baseline must be based on measured performance. Establishing a baseline before the migration would not reflect the real operating characteristics of the new environment.
Why not B: Baselines are intended to represent normal, expected performance, not degraded conditions. Using a slowdown as the baseline would set an abnormal, lower-performance reference and reduce the usefulness of future comparisons.
Why not D: Waiting for the end of the fiscal year delays timely monitoring and may mix normal activity with seasonal or unusual fluctuations. A delayed, overly long baseline can obscure the typical operating state rather than providing a clear normal-state reference.
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
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.