Skip to content
  • There are no suggestions because the search field is empty.

How to Document a Security or Data Incident

Choose the template that fits what happened and work through the incident step by step.

How do I register an incident?

Go to the incident log, select Create incident and choose the template that matches what happened, for example Personal data breach or NIS2 incident. You are then taken through the incident one step at a time, with only the fields that matter for that kind of incident. See Standard Incident Templates and Your Plan.

Steps to register an incident

  1. Go to Incidents.
  2. Select Create incident.
  3. Choose the incident template.
  4. Work through the steps. For an information security incident they are Incident, Access, Timeline, Services and impact, Notification, Relations and Documentation. Use Next and Previous to move between them.
  5. Select Complete when you are ready.

Information security incident open on step 1 of 7 in the guided flow (Incident, Access, Timeline, Services and impact, Notification, Relations, Documentation), with fields for name, description, type, severity, status, business areas, compliance areas and tags

Some fields must be filled in before the incident can be created, so the essentials are always captured from the start. Which fields these are is decided by the template.

If the incident was first reported as an observation, you do not need to type it in again. See Convert an Observation to an Incident.

Why does incident documentation matter?

Well-documented incidents support your compliance with GDPR Articles 33 and 34, fulfil NIS2 notification obligations, and build an internal record that strengthens your organisation's ongoing compliance work and preparedness.


Related Articles