11 Nov 2026 · 4d ago#1
A calm first hour beats a heroic but chaotic response. Here is a practical, vendor-neutral checklist for a system you own or are responsible for. Adapt it to your incident plan; do not treat this as a substitute for legal, safety, or regulatory advice.
0–10 min — establish the picture
- Name one incident lead and one note-taker. Record UTC timestamps, who made each decision, and why.
- Confirm scope: affected accounts, services, data types, and whether the issue is ongoing. Separate observed facts from hypotheses.
- Use a clean, trusted communication channel if the normal one may be affected.
10–25 min — preserve before you clean up
- Preserve relevant authentication, application, cloud audit, and endpoint logs, including their time zones and retention context.
- Record alert IDs, affected asset identifiers, and a concise event timeline. Restrict access to evidence.
- Avoid rebooting or wiping a device unless safety or containment requires it; that may destroy useful evidence. Follow your organization’s evidence-handling process.
25–45 min — contain proportionately
- Prefer reversible, scoped actions: revoke a confirmed affected session, disable a confirmed compromised account temporarily, or isolate one affected asset using your approved tools.
- Before a broad block or shutdown, consider customer impact, dependencies, and whether the action will alert an attacker. Escalate if scope is unclear.
- Secure recovery email/phone and privileged accounts; verify the responder’s identity out of band.
45–60 min — communicate and plan
- Tell stakeholders what is known, what remains unknown, what action was taken, and when the next update will arrive. Don’t speculate or expose personal data.
- Assign owners to the next investigative questions and set a review time. Preserve a record of containment decisions.
- After stabilization, document root cause, impact, recovery checks, and prevention work without blaming individuals.
Mini exercise: a staff member reports an unexpected password-reset email. What do you check first? Which actions are safe before confirming account compromise? Post a short decision tree.
References: [CISA Incident Response Playbooks](https://www.cisa.gov/resources-tools/resources/incident-response-playbook) · [NIST Cybersecurity Framework](https://www.nist.gov/cyberframework).
0–10 min — establish the picture
- Name one incident lead and one note-taker. Record UTC timestamps, who made each decision, and why.
- Confirm scope: affected accounts, services, data types, and whether the issue is ongoing. Separate observed facts from hypotheses.
- Use a clean, trusted communication channel if the normal one may be affected.
10–25 min — preserve before you clean up
- Preserve relevant authentication, application, cloud audit, and endpoint logs, including their time zones and retention context.
- Record alert IDs, affected asset identifiers, and a concise event timeline. Restrict access to evidence.
- Avoid rebooting or wiping a device unless safety or containment requires it; that may destroy useful evidence. Follow your organization’s evidence-handling process.
25–45 min — contain proportionately
- Prefer reversible, scoped actions: revoke a confirmed affected session, disable a confirmed compromised account temporarily, or isolate one affected asset using your approved tools.
- Before a broad block or shutdown, consider customer impact, dependencies, and whether the action will alert an attacker. Escalate if scope is unclear.
- Secure recovery email/phone and privileged accounts; verify the responder’s identity out of band.
45–60 min — communicate and plan
- Tell stakeholders what is known, what remains unknown, what action was taken, and when the next update will arrive. Don’t speculate or expose personal data.
- Assign owners to the next investigative questions and set a review time. Preserve a record of containment decisions.
- After stabilization, document root cause, impact, recovery checks, and prevention work without blaming individuals.
Mini exercise: a staff member reports an unexpected password-reset email. What do you check first? Which actions are safe before confirming account compromise? Post a short decision tree.
References: [CISA Incident Response Playbooks](https://www.cisa.gov/resources-tools/resources/incident-response-playbook) · [NIST Cybersecurity Framework](https://www.nist.gov/cyberframework).