Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 9 · Reading 9 of 10

Running an incident from declaration to recovery

Security+ SY0-801 · Objectives 4.7

A ticket says “resolved” while service staff are still using a paper workaround. The technical team restored a server. The incident lead still has to decide when people can return to the service safely and what to tell them in the meantime.

Prepare authority before the incident

A response plan names the incident lead, technical responders, service owner, communications lead and escalation channels. A playbook describes decisions for a recurring scenario. A tabletop can expose an ambiguous approval path before an outage. Set severity criteria using business impact and exposure. Prepare a way to communicate when ordinary identity or messaging systems may be unavailable.

During identification, record the initial report, time source, affected assets and competing explanations. Declare an incident using the agreed criteria and establish a decision log. Prioritize ongoing harm while preserving evidence. Network isolation may protect peers while preserving volatile memory. Disabling a shared account may interrupt critical operations. Record the owner of the decision, expected consequences, fallback and time for reassessment.

Maintain a defensible handoff

Containment limits immediate impact. Eradication removes the cause and unauthorized access. Recovery restores trusted service. These activities may overlap as scope changes. Maintain a timeline that distinguishes observation from inference. Route external reporting decisions through responsible organizational stakeholders who can evaluate applicable obligations. Share evidence on a need-to-know basis and update affected users when verified facts change.

At recovery, test a normal business transaction, verify clean configuration and credentials, monitor for recurrence and obtain the service owner's acceptance. A host coming online establishes only part of recovery. The post-incident review should explain how the incident arose, which controls worked and where the evidence was incomplete. Assign corrective actions and test them in a future exercise. A lesson without an owner and verification date rarely changes the next response.

NIST incident response guidance

Brief different audiences from the same facts

An infrastructure lead needs the affected instance identifiers and which connections remain blocked. The advising desk needs a reliable alternate way to handle requests. A director needs to know the current impact, what decision requires authority and when the next update will arrive. These can be different messages derived from one decision log. Record the owner and time of each update to avoid different teams acting on conflicting instructions.

If the likely scope expands, distinguish newly confirmed facts from an estimate that changed. A precise account of what changed helps colleagues revise their decisions without discarding everything learned earlier. At the review meeting, ask whether the people affected by the outage received information early enough to use the workaround.

Write the next shift’s first five minutes

Imagine you are handing the incident to someone arriving at midnight. Describe the affected service as its users experience it, the last confirmed harmful action, the containment still in place and the next decision that requires authorization. Include where the underlying records are held and how to contact the responsible owner. If identity review is incomplete, name the remaining question and the condition that would permit release. A handoff like this reduces repeated collection and premature recovery. It also gives an investigator a disciplined starting point when a stakeholder later asks exactly what the incident exposed.

Containment and release gates

Inspect the three records, then use the evidence to answer the question.

1. Incident lead

Lead approves restricting access to the affected service.

2. Service owner

Owner restores the application and completes a test transaction.

3. Recovery evidence

Identity review still finds an unauthorized active session.

Apply the reading

What makes a restored application ready to return to service?

Compare your reasoning

Verify business function, the removal of unauthorized access, monitoring and acceptance by the accountable owner.