CISM domain - 30% of the exam

Incident Management

Incident Management is 30% of the CISM exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

90
Practice questions
12
Objectives
60
Medium
30
Hard

Where people go wrong

  • Swapping RTO, RPO and maximum tolerable downtime

    The wrong answers attach a figure to the wrong recovery parameter. A four-hour restoration deadline is labelled the recovery point objective or maximum tolerable downtime, and fifteen minutes of tolerable transaction loss is labelled the recovery time objective. The recovery time objective is how long restoration may take. The recovery point objective is tolerable data loss, so only more frequent backups close a gap against a one-hour objective. Maximum tolerable downtime is the outer limit.

    See it in a sample question
  • Ranking recovery priority by a proxy for impact

    The wrong answers set recovery priority or spend by something that resembles importance: how strongly executives value a report, how complex a process is, what a system costs to run, how often it was attacked, or one standard tier for every system. None measures the harm of disruption. Priority follows how quickly and severely an outage damages the organisation against agreed impact criteria, and the fastest, costliest recovery options go to processes with the tightest objectives.

    See it in a sample question
  • Blurring continuity, disaster recovery and incident response plans

    The wrong answers hand one plan the job of another. The disaster recovery plan is described as the whole recovery story, or as the place where invocation thresholds live. The business continuity plan is reduced to restoring IT, or treated as a last resort after recovery fails. Continuity keeps people, premises and processes operating. The disaster recovery plan restores systems, applications and data. Escalation and invocation criteria belong to the incident response plan.

    See it in a sample question
  • Declaring eradication or recovery complete too early

    The wrong answers treat the visible fix as the end of eradication. They restore from backup or rotate credentials while the backdoor and vulnerability remain, reset one account and reimage one server after lateral movement, or correct a misconfiguration while forged tokens stay valid. Eradication removes the root cause and every foothold, including sessions and signing keys. Recovery then restores from a backup that predates the compromise.

    See it in a sample question
  • Touching a live machine before capturing its memory

    The wrong answers act on a powered-on machine in ways that lose or contaminate volatile evidence: a clean shutdown, a quick file copy, running antivirus, reconnecting to capture traffic, or isolating the network first. A shutdown clears memory and alters timestamps, a file copy changes access times, antivirus deletes artefacts, and isolation can drop live connections and processes. The first step is to acquire a memory image and a forensic image under a documented process, recording hashes and timestamps, before any action that powers the system off.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleIncident Managementmedium

During business impact analysis, the team determines that the order-entry system must be restored within four hours of a disruption to avoid unacceptable loss. Which recovery parameter does this four-hour figure represent?

  • AThe recovery time objective, which sets the maximum tolerable period for restoring the system after a disruption Correct
  • BThe recovery point objective, which sets the maximum amount of data the organisation can afford to lose measured back from the disruption
  • CThe maximum tolerable downtime, which is the absolute outage limit beyond which the organisation cannot survive
  • DThe service delivery objective, which defines the reduced level of operation that must be sustained during the recovery period
The recovery time objective is the maximum tolerable period to restore a system or process after a disruption. A restoration deadline measured forward from the moment of disruption is the recovery time objective, distinct from the recovery point objective which measures tolerable data loss backward from the event. Confusing the two leads to mismatched backup and recovery strategies.

Why A is correct: The recovery time objective is the maximum acceptable duration to restore a process or system after disruption, so the four-hour restoration deadline is precisely the recovery time objective.

Why B is wrong: The recovery point objective is tempting because it is also expressed in time, but it measures tolerable data loss before the event, not how quickly the system must be back in service afterwards.

Why C is wrong: Maximum tolerable downtime is a plausible confusion because it is also an outage duration, but it is the outer survival limit for the whole process, and the recovery time objective is set to fall within it rather than equal it.

Why D is wrong: The service delivery objective describes the minimum capacity to run in alternate mode during recovery, not the deadline by which restoration must occur, so it does not match a four-hour restoration target.

Free sampleIncident Managementhard

A retailer's BIA must decide which processes are critical so recovery investment can be focused. One business unit insists its month-end reporting process is critical because executives value the reports highly. On what basis should the security manager judge whether a process is genuinely critical for recovery prioritisation?

  • AOn how strongly the process's owners and executive sponsors regard it, since perceived importance reflects the value the business places on the process.
  • BOn the volume of data the process holds and the number of integrations it has, since the most connected and data-rich processes are the hardest to restore.
  • COn how much the process costs to operate each year, since the most expensive processes represent the greatest investment to protect and recover first.
  • DOn how quickly and severely disruption to the process would harm the organisation, measured against agreed impact criteria such as financial loss and regulatory breach. Correct
Judge process criticality by the speed and severity of disruption impact against agreed criteria, not by stakeholder sentiment, complexity, or operating cost. Recovery prioritisation requires an objective and consistent basis, so criticality is assessed by how fast and how badly an outage would damage the organisation, scored against shared impact criteria such as financial, operational, legal, and reputational harm. This keeps prioritisation defensible and prevents louder stakeholders or technical complexity from distorting where recovery resources are placed.

Why A is wrong: Tempting because owner sentiment is easy to gather, but stakeholder enthusiasm is subjective and unevenly expressed; criticality must rest on the demonstrable impact of disruption, not on how strongly a process is valued.

Why B is wrong: Tempting because complex, integrated processes are harder to recover, but technical complexity describes recovery effort, not business criticality; a simple process can be critical and a complex one non-critical.

Why C is wrong: Tempting because cost feels like a proxy for importance, but operating spend reflects running cost, not the impact of an outage; a cheap process can be business-critical and an expensive one merely convenient.

Why D is correct: Correct: criticality is determined by the speed and severity of harm a disruption causes, assessed against consistent impact criteria, which lets processes be ranked objectively for recovery prioritisation.

Free sampleIncident Managementmedium

A board asks the information security manager to explain how the business continuity plan differs in purpose from the disaster recovery plan, so the two investments are not seen as duplicates. Which statement best captures the distinction the manager should give?

  • AThe continuity plan restores IT systems and data quickly, while recovery defines the manual workarounds the business uses while systems are down.
  • BThe continuity plan is a technical document for IT, while recovery is a board-level governance document owned by executive management.
  • CThe continuity plan keeps the whole business operating during a disruption, while recovery focuses on restoring the IT systems that support it. Correct
  • DThe continuity plan is invoked only after recovery has failed, so it serves purely as a fallback when systems cannot be restored at all.
Business continuity sustains critical business operations during disruption, whereas disaster recovery is the narrower technical restoration of supporting IT systems and data. Business continuity has a wider scope than disaster recovery: it keeps people, premises and critical processes functioning, often through manual workarounds, while disaster recovery concentrates on bringing the underlying technology back. Treating them as duplicates misunderstands that one is a business plan and the other a technical sub-component.

Why A is wrong: Tempting because both terms involve restoring service, but this reverses the two roles: recovery is the technical restoration and continuity covers the business workarounds.

Why B is wrong: Tempting because ownership levels do differ, but it misassigns them: continuity is the business-wide plan and recovery is the more technical IT-focused effort, not the reverse.

Why C is correct: Correct because business continuity addresses sustaining critical operations across people, premises and processes, whereas disaster recovery is the narrower technical task of restoring systems and data.

Why D is wrong: Tempting because the plans are sequenced, but continuity is not a last resort after recovery fails; it runs in parallel to sustain operations while recovery proceeds.

Free sampleIncident Managementhard

An attacker exploited a misconfigured identity provider to issue forged authentication tokens across several cloud services. The incident is contained and the misconfiguration is corrected. As the information security manager validates eradication before recovery, which residual condition most needs to be addressed to prevent the attacker from regaining access?

  • AThe corrected identity-provider configuration should be exported and stored so it can be reapplied quickly if a future incident occurs
  • BForged tokens and active sessions issued during the compromise window may still be valid until the signing keys are rotated and sessions are revoked Correct
  • CThe affected cloud services should be migrated to a different region to ensure the attacker loses any cached network routes to the providers
  • DMulti-factor authentication should be enforced on all new logins so that any future authentication attempt requires a second factor
Eradicating an identity compromise requires rotating signing keys and revoking sessions and tokens issued during the compromise window. Forged or stolen authentication tokens and live sessions remain valid independently of the original misconfiguration, so they survive a configuration fix; only rotating the signing keys and revoking the issued sessions and tokens removes this persistence and prevents the attacker from re-entering using credentials minted during the breach.

Why A is wrong: Capturing a known-good configuration is sound preparation, but it is a resilience measure for future events rather than a residual threat from this incident, so it is tempting as good hygiene yet does nothing to close the attacker's current foothold.

Why B is correct: Correcting the misconfiguration stops new abuse, but tokens and sessions minted while it persisted remain trusted until the signing material is rotated and sessions revoked, so this residual persistence is the key eradication gap that lets the attacker retain access if left unaddressed.

Why C is wrong: Regional migration sounds like it disrupts the attacker, but token-based access does not depend on network routes or region, so this misdiagnoses the persistence mechanism and adds disruption without removing the forged-token foothold.

Why D is wrong: Enforcing multi-factor authentication strengthens future logins and is good practice, but forged tokens bypass the interactive login flow entirely, so adding a second factor to new logins does not invalidate the already-issued tokens that constitute the residual compromise.

Free sampleIncident Managementhard

During the response to a suspected fraud, an information security manager learns that a laptop holding key evidence is still powered on with several applications open. Forensic investigators have not yet arrived. To best preserve the evidentiary value of the data, what should the manager direct staff to do first?

  • AShut the laptop down cleanly through the operating system so that open files are saved before it is moved.
  • BCopy the relevant files to a network share so a backup exists before the device is handled further.
  • CCapture the volatile data and a forensic image under a documented process, leaving the machine in its current state until that is done. Correct
  • DDisconnect the laptop from the network and continue normal investigation once it is isolated.
Preserve the most volatile evidence first by capturing memory and a forensic image before altering a live system. Evidence has an order of volatility: memory and running state vanish on shutdown, so a forensic process captures volatile data and an integrity-verified image before any change is made to the device.

Why A is wrong: A clean shutdown feels orderly and protects unsaved work, but it alters timestamps, clears volatile memory, and runs shutdown scripts that can overwrite evidence, reducing forensic value.

Why B is wrong: A quick file copy seems to safeguard the data, but it changes access times, omits deleted and volatile artefacts, and produces no verifiable image, weakening any legal case.

Why C is correct: Acquiring volatile memory and a bit-for-bit image under a documented, repeatable process preserves the most fragile evidence first and maintains integrity for later admissibility.

Why D is wrong: Network isolation is a sensible containment step, but acting on it first without capturing volatile state can drop live connections and processes that hold the very evidence being sought.

Other domains in this exam

See also the CISM cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by ISACA. Original, blueprint-aligned practice material only.