Compliance

This is the Compliance demo. Every visitor shares this company, and it resets every night.

What you change here, everyone sees until the next reset. Email, payments, and the AI models are switched off.

Start your own trial
  • EU GDPR (2016)
  • ISO 27001:2022
  • NIS2
  • NIS2 Netherlands (Cbw, 2026)

Nothing found that matches the search criteria.

Start your own trial
SV
Sam de Vries
sam.devries@tidewell-it.example

Progress report and final report

Cyberbeveiligingswet art. 29 - Last updated Mandatory

Catalog reference

Send a final report to your CSIRT and your competent authority no later than one month after the notification of art. 27(1). It holds a detailed description of the incident, its severity and its effects; the type of threat or root cause that probably led to it; the mitigation measures applied and in progress; and, where applicable, the cross-border effects (art. 29(1)). If the incident is still ongoing when the final report is due, send a progress report on those aspects instead, and send the final report within one month after the incident has been handled (art. 29(2)).

Narrative — how we satisfy this requirement

No narrative yet. Add one.

Review

On track

Next review is 10/27/2027 — no urgency right now.

Review cadence
Every 365 days
Last reviewed
Next review due
Add a result
Result (optional)
    Record an earlier date
    Recorded when you mark the task done.

    Are you sure?

    This action cannot be reverted.

    Leave this page?

    Your changes on this form are not saved. If you leave, they are lost.