CloudSignLab

Incidents

Never miss an NIS2 reporting deadline

Record an incident the moment you become aware of it. For significant incidents CloudSignLab shows the NIS2 reporting clock with every deadline, reminds the people handling it and keeps the record of what was sent and when.

An incident with the NIS2 reporting clock and its deadlines

How it works

  1. Report it at once

    Describe what happened, choose type and severity, and confirm when you became aware: the clock starts then.

  2. Follow the clock

    Early warning 24 hours, notification 72 hours and final report one month after the notification, with reminders before each.

  3. Handle and document

    Move the status from open to closed, note impact and measures, and attach logs or screenshots as evidence.

What changes for you

  • Deadlines in plain sight

    Reports due next are listed at the top of Incidents and in Tasks, soonest first.

  • GDPR in the same place

    When personal data is affected, the 72-hour data protection check is shown as well.

  • Everyone can report

    Every member can report an incident, and every package includes unlimited incidents.

What it covers

  • NIS2 Art. 23
  • NIS2 21(2)(b)
  • ISO 27001 A.5.24-A.5.28
  • GDPR Art. 33

Included in

  • Free
  • Supplier Ready
  • Professional
  • Business
  • Enterprise
Compare packages →

Works together with

Questions

Does CloudSignLab send the report to the authority?

No. You send the reports to your CSIRT or authority yourself, then enter the dates and the case number, so the record is complete.

Who gets reminders?

The owners, admins and the person handling it: 6 hours before the early warning, 12 hours before the notification and 5 days before the final report.

Be ready before something happens

Set up your organization now, so an incident is recorded in seconds when it counts.

Start free