• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team

Checklist · Incident Response

Security Incident: First 24 Hours Checklist

What to do, in order, in the first day of a suspected security incident.
Security Incident: First 24 Hours Checklist cover photograph

Written for

Whoever is on call when it happens

Time needed

Keep printed

Items

28 across 5 areas

The first hours of an incident decide how bad it gets. People who have never handled one tend to do two things that hurt: they wipe evidence while trying to clean up, and they wait too long to call for help.

Print this checklist and keep it where it can be found without the network. If you have an active incident now, call the GuardsArm incident line.

0 of 28 in place (0%)

01

First hour: confirm and contain

Stop the spread without destroying evidence.

02

Hours 1 to 4: assemble and assess

Get the right people and a first picture.

03

Hours 4 to 12: scope and protect

Understand reach and protect what is left.

04

Hours 12 to 24: decide and communicate

Obligations and messaging.

05

Do not

Mistakes that make recovery harder.

How to get the most from this list

  1. 01

    Tick only what you can prove

    If you could not show an auditor or your board the evidence today, leave it unticked. A lower honest score is more useful than a high hopeful one.

  2. 02

    Give every gap an owner

    For each unticked item, name one person and one date. Gaps without an owner are the ones still open next year.

  3. 03

    Re-run it every quarter

    Your environment changes faster than policy. Repeat the list each quarter and after any major change, and compare the scores.

Gaps we see most often

  • Nobody has authority to isolate a system at night
  • Insurer notified late, which complicates the claim
  • Backups turned out to be reachable from the compromised network

Take it with you

Download the checklist as a PDF

A designed 6-page version with tick boxes, the common gaps and the questions people ask. Useful for a team review or as audit evidence.

Want a second pair of eyes?

Bring your completed list to a risk review. We will check the items that matter most for your environment, confirm the evidence and turn the gaps into a short, prioritized plan.

Request a risk review

Common questions

Should we turn the affected computer off?

Usually not. Disconnecting it from the network preserves memory evidence that powering off destroys.

When do we have to notify a regulator?

It depends on the law that applies and the data involved. Many regimes require notice quickly once you determine a breach creates a real risk of harm, so start the assessment on day one.

Should we pay a ransom?

That is a decision for leadership with legal counsel, your insurer and law enforcement advice. Payment does not guarantee recovery and may be restricted by sanctions law.