DRIMT logoDRIMT

    Incident response · NIS2 · DORA · GDPR

    Incident response, ready before the clock starts

    When an incident hits, NIS2 gives you 24 hours for an early warning. Prepare your playbooks, detect early, contain with guardrails and report on time — with the evidence already collected.

    NIS2 Article 23

    24h · 72h · 1 month

    Early warning, incident notification and final report for significant incidents

    DORA major ICT incidents

    4h · 72h · 1 month

    Initial report within 4h of classification (max. 24h after detection), then intermediate and final

    GDPR Article 33

    72 hours

    Notify the data protection authority of a personal data breach, unless unlikely to cause risk

    The incident response lifecycle

    NIST SP 800-61 Rev. 3 now places incident response inside the whole NIST CSF 2.0 cycle, from governance to recovery. In practice, teams still work through five phases — and most of the work happens before the incident.

    1. 01

      Prepare

      Roles, contact lists, playbooks, logging and a tested decision tree for what is reportable.

    2. 02

      Detect & analyse

      Spot the anomaly, confirm the incident, assess scope and severity, and start the timeline.

    3. 03

      Contain

      Isolate affected systems and accounts fast, without destroying the evidence you need later.

    4. 04

      Eradicate & recover

      Remove the root cause, restore from clean backups and watch for the attacker coming back.

    5. 05

      Learn & improve

      Run the post-incident review, file the final report and turn lessons into new controls.

    The NIS2 reporting timeline

    For a significant incident — one that causes or can cause severe operational disruption or financial loss, or considerable damage to others — NIS2 sets three deadlines. In Belgium, notifications go to the Centre for Cybersecurity Belgium (CCB).

    • Within 24 hours of becoming aware: early warning, including whether malicious action is suspected and any cross-border impact
    • Within 72 hours: incident notification with an initial assessment of severity, impact and indicators of compromise
    • On request: intermediate status reports
    • Within one month of the notification: final report with root cause, mitigation and cross-border impact
    • Personal data involved? The GDPR 72-hour notification to the data protection authority runs in parallel — the DPO needs to be in the loop from hour one

    Detect early, not in the audit

    The 24-hour clock starts when you become aware — so the faster you see an incident, the more time you have to understand it. Drimt continuously scans your environment and connectors and raises findings with their severity and affected assets.

    • Continuous scanning of assets, configurations and exposed services
    • Findings ranked by severity and linked to the affected risk and control
    • A timestamped timeline you can reuse in your NIS2 and GDPR notifications

    Contain and fix with guardrails

    Speed matters, but an unsafe fix can cause a second outage. Drimt's auto-fix pipeline proposes remediations, checks them and keeps a rollback guard, so every change is reversible and logged in the audit trail.

    • Suggested fixes with a review step before anything changes
    • Rollback guard if a remediation breaks a service
    • Every action recorded in a signed audit trail for regulators and insurers

    Playbooks every regulated team needs

    Write these before you need them, test them in a tabletop exercise at least once a year, and keep the contact lists current.

    • Ransomware and destructive malware
    • Phishing, business email compromise and account takeover
    • Personal data breach (GDPR notification path)
    • Supplier or cloud provider compromise
    • DDoS and service outage
    • Insider threat and lost or stolen devices

    How Drimt helps

    Reporting deadlines tracked

    Each incident carries its NIS2, DORA and GDPR clocks so nobody misses the 24-hour early warning.

    Evidence collected as you go

    Timeline, affected assets and actions are captured automatically for your reports.

    Safe remediation

    Auto-fix with review and rollback guard, logged in a signed audit trail.

    Lessons into controls

    Post-incident findings become new risks and control updates in the same workspace.

    Cybersecurity training for teams

    Frequently asked questions

    What counts as a significant incident under NIS2?

    An incident is significant if it has caused or can cause severe operational disruption of your services or financial loss for your organisation, or if it has affected or can affect other people or organisations by causing considerable material or non-material damage.

    Do we report to both the CCB and the data protection authority?

    If the incident is significant under NIS2 and also involves personal data, yes: the NIS2 notification and the GDPR breach notification are separate obligations with separate recipients. Align them so the facts you report are consistent.

    We are a bank — does NIS2 or DORA apply to incident reporting?

    For financial entities in scope of DORA, DORA's major ICT incident reporting applies as the specific rule instead of the NIS2 reporting obligations. The timelines differ: the initial report is due within 4 hours of classifying the incident as major and no later than 24 hours after becoming aware.

    How often should we test our incident response plan?

    At least once a year, and after major changes. Tabletop exercises with management are the most efficient way to test decision-making, while technical drills test backups and restoration.

    What should the 24-hour early warning contain?

    It can be short: that an incident is happening, whether you suspect unlawful or malicious acts, and whether it could have cross-border impact. Details come in the 72-hour notification.

    Be ready for your next 24-hour clock

    Book a demo and get a free audit scan: we check your detection coverage, reporting readiness and the gaps in your playbooks.