Security incident response

Respond to a security incident - contain it, investigate it and report it.

IT & OperationsEngineering


Incident

A short name for the incident

Severity

๐Ÿ”ด Critical | ๐ŸŸ  High | ๐ŸŸก Medium | ๐ŸŸข Low

Status

๐Ÿ”ด Active | ๐ŸŸก Contained | ๐ŸŸข Closed

Incident lead

@mention the incident lead

Detected

Summary

Two or three sentences: what happened, how you found it, and what is at risk. Update it when you learn more.

Containment

  • Isolate the affected systems or accounts: which ones
  • Change the passwords, keys or tokens that may be exposed
  • Block the source of the attack, for example an IP address or an email sender
  • Keep the evidence: do not delete logs, and make copies before you change a system
  • Record each action in the investigation table below
  • A step from your incident response plan

Investigation

Time (UTC)

Finding

By

10:15

The logs show sign-ins to an admin account from an unknown device.

A security engineer

time

what you found or did, and the evidence

@mention the person

Affected data and systems

  • A system or a service, and how the incident affects it
  • The data that may be exposed: the type of data and the number of records
  • The people affected, for example customers or staff, and how many

Notifications

Deadlines to report the incident

A law, a regulator or a contract can set a deadline to report an incident. Ask your legal team which deadlines apply, and start early.

  • Write the deadlines that apply to you, for example a regulator's or a customer contract's

Who

When

By

who you must tell, for example customers, a regulator or your insurer

@mention the person who sends the notice

Lessons and follow-ups

What you learned: what worked, what did not, and what to change in your systems or your response plan.

  • Action ยท @owner ยท

allanswered knowledge management