Guideöversikt · 11 kapitel · Handle the Incident

What good incident response looks like

Good incident response is calm, practised and clear about who decides what.

  • Av Thilanka Dilshan
  • Uppdaterad 6 oktober 2026

Good incident response is calm, practised and clear about who decides what.

The first 72 hours set the course. Decisions on containment, evidence and communication made early are hard to undo later.

Key points

  • Clear roles beat heroic effort
  • Containment and evidence must be balanced
  • Regulatory clocks start early

How this guide is organised

The guide has 11 chapters. Each one stands on its own, so you can read them in order or go straight to the topic you need.

  1. Preparation: roles, contacts and the incident plan
  2. The first hour: detect, confirm and contain
  3. Declaring an incident and setting severity
  4. Preserving evidence without slowing recovery
  5. Containment options and their trade-offs
  6. Communicating with staff, customers and the board
  7. Regulatory clocks: NIS2, GDPR and DORA
  8. Eradication and safe recovery
  9. Working with your MDR provider and external responders
  10. Lessons learned and the post-incident review

Who this guide is for

It is written for IT and security leads, risk and compliance owners and the managers who sign off on the work. This guide follows the order of a real incident.

Källor

Alla källor hämtades 9 October 2026.

Thilanka Dilshan

Boka en säkerhetsgenomgång på 30 minuter.
Ingen säljpresentation.

Prata med en Sverigebaserad analytiker. Vi går igenom din säkerhetsnivå, kartlägger dina luckor och ger dig en tydlig bild av läget, på vanlig svenska.

Boka en kostnadsfri genomgång
Ingen bindning Sverigebaserad analytiker