---
title: "Incident Reporting Desk"
url: "https://grc.plus/service/incident-reporting-desk/"
type: "Service"
updated: "2026-11-20"
publisher: "GRC+"
---

Incident reporting

# Know What to Report, to Whom and by When.

One incident can start several reporting clocks at once: NIS2, DORA, the GDPR and, since September 2026, the Cyber Resilience Act. We decide with you what is reportable, draft every notification in the authority's own format and check or prepare each report before it goes out.

![CISSP](https://grc.plus/wp-content/themes/grcplus/assets/img/credentials/cissp.webp) ![CISM](https://grc.plus/wp-content/themes/grcplus/assets/img/credentials/cism.webp) ![CISA](https://grc.plus/wp-content/themes/grcplus/assets/img/credentials/cisa.webp)

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)

[Try the Incident Reporting Clock](/tools/incident-reporting-clock/)

**500+** Regulations Laws and standards

**40** Countries Europe, Gulf, Asia and North America

**25+** Years In regulated sectors

**9** Industries From banking to healthcare

Have an incident now?

## Report it through our form.

This is regulatory reporting: deciding what the law asks you to report, and writing it. Your own team or incident response firm keeps containing the incident. If your systems are down or not safe to use, call the Intake Line; the numbers are next to the form.

Single incident · Pay as you go

### One incident, start to finish

The reporting decision for each law, and the first notification to each authority drafted for you to submit. Follow-up and final reports at an hourly rate.

[Report an Incident](https://grc.plus/report-an-incident/)

Not urgent

### A second opinion on your report

Your team drafted the notification. We check it is complete, consistent with earlier reports and defensible, and send it back with our changes.

Get a Proposal

Plan ahead

### A monthly plan

After a first incident, a plan means the next one starts from a reporting map that is already set up.

Get a Proposal

Why you need it

## One incident can start several reporting clocks

The problem

### Nobody is sure what to report, to whom or by when

- Your team is busy containing the incident
- Each law has its own threshold, authority, portal and form
- The first deadline can fall within hours
- A late or missing report is a breach in its own right

What we do

### Decide and draft with you

- The incident assessed against each law that may apply
- The decision and its reasons recorded, also when the answer is no
- Notifications drafted in the authority's format, approved by you
- Or your own draft reviewed before you send it

The result

### Every report on time, and a record that holds up

- Your team stays on containment and recovery
- Notifications and final reports ready within the legal deadlines
- A decision record your board, auditors and supervisor can follow
- Regulator questions answered from one consistent file

Does a requirement ask for it?

## The laws and standards that ask for it

We scope the work to what your requirement asks for, so the result serves that audit or supervisor too.

[EU Directive NIS2 · Art. 23(1), 23(4) Significant incidents reported to the CSIRT or authority: early warning in 24 hours, notification in 72 hours, final report within a month. Read the Requirement](https://grc.plus/regulation/nis2/)

[EU Regulation DORA · Art. 19; Delegated Reg. (EU) 2025/301, Implementing Reg. (EU) 2025/302 Major ICT-related incidents reported: initial notification within 4 hours of classification, at most 24 hours from awareness. Initial notification, intermediate and final reports submitted on the standard forms and templates. Read the Requirement](https://grc.plus/regulation/digital-operational-resilience-act-dora/)

[EU Regulation GDPR · Art. 33, 34 Personal data breaches notified to the supervisory authority within 72 hours, and to people without undue delay where the risk is high. Read the Requirement](https://grc.plus/regulation/general-data-protection-regulation-gdpr/)

[EU Regulation CRA · Art. 14 Manufacturers report actively exploited vulnerabilities and severe incidents within 24 and 72 hours, from 11 September 2026. Read the Requirement](https://grc.plus/regulation/cyber-resilience-act-cra/)

[United States SEC cyber rules · Form 8-K Item 1.05 Material cybersecurity incidents disclosed within four business days of the materiality determination. Read the Requirement](https://grc.plus/regulation/sec-cybersecurity-disclosure-rules/)

[United States NYDFS Part 500 · § 500.17(a), (c) Cybersecurity incidents notified within 72 hours; extortion payments within 24 hours, with the reasons within 30 days. Read the Requirement](https://grc.plus/regulation/nydfs-cybersecurity-regulation-23-nycrr-500/)

[United Kingdom UK GDPR · Art. 33, 34 Personal data breaches notified to the UK regulator within 72 hours, and to people without undue delay where the risk is high. Read the Requirement](https://grc.plus/regulation/uk-general-data-protection-regulation-uk-gdpr/)

[United Kingdom UK NIS · Reg. 11 Operators of essential services notify NIS incidents to their competent authority within 72 hours of becoming aware. Read the Requirement](https://grc.plus/regulation/uk-network-and-information-systems-regulations-2018/)

What we handle

## From the first hour to the final report

You stay in charge of the incident. We take the reporting off your team.

### Is it reportable?

Assessed with you against the criteria of each law, with the decision on record.

### Where and to whom

The authority, CSIRT or supervisor for each law and country, and the portal or form it uses.

### Every notification on time

Early warnings, initial notifications and breach notices drafted and approved by you, then submitted by you, or by us under mandate on the Covered plan.

### Review of your own report

An independent check of a report your team drafted: complete, consistent and defensible before it goes out.

### Follow-up and final reports

Intermediate and final reports tracked to their deadlines, with the facts consistent from one report to the next.

### Customers and people affected

Notices to clients and data subjects where a law requires them, in plain words.

### Regulator questions

One file with the timeline, decisions and reports, from which we answer the authority.

### Filing under a mandate

On the Covered plan, where an authority accepts it, we file in your name under a written mandate. Otherwise we draft and you submit.

THE CLOCKS

## The deadlines one incident can trigger

Which ones apply depends on your sector, your market and what the incident affected. These are the deadlines in the law; national laws and supervisors can add detail, such as forms or the authority to use.

### DORA: major ICT-related incident

Initial notification within 4 hours of classifying the incident as major, and at the latest 24 hours after you became aware of it. Intermediate report within 72 hours of the initial notification; final report within a month of the latest intermediate report. RTS (EU) 2025/301 sets the deadlines and content, ITS (EU) 2025/302 the forms.

[Source →](https://eur-lex.europa.eu/eli/reg_del/2025/301/oj)

### NIS2: significant incident

Early warning within 24 hours of becoming aware, incident notification within 72 hours, final report within a month of the notification, to the CSIRT or competent authority. National laws apply these deadlines and name the authority.

[Source →](https://eur-lex.europa.eu/eli/dir/2022/2555/oj)

### GDPR: personal data breach

Notice to the supervisory authority within 72 hours of becoming aware, where feasible, with reasons for any delay. The people affected are told without undue delay where the risk to them is high.

[Source →](https://eur-lex.europa.eu/eli/reg/2016/679/oj)

### CRA: products with digital elements

From 11 September 2026, manufacturers report actively exploited vulnerabilities and severe incidents to the CSIRT coordinator and ENISA: early warning within 24 hours, notification within 72 hours, then a final report.

[Source →](https://eur-lex.europa.eu/eli/reg/2024/2847/oj)

### SEC: Form 8-K Item 1.05

Listed companies disclose a material cybersecurity incident within four business days of deciding it is material. The materiality decision must be made without unreasonable delay after discovery.

[Source →](https://www.sec.gov/files/form8-k.pdf)

### NYDFS Part 500

Notice to the Superintendent within 72 hours of determining that a cybersecurity incident occurred, also at an affiliate or third-party service provider. An extortion payment is notified within 24 hours and explained within 30 days.

[Source →](https://www.dfs.ny.gov/system/files/documents/2023/10/rf_fs_2amend23NYCRR500_text_20231101.pdf)

### UK GDPR

A personal data breach is reported to the UK regulator within 72 hours of becoming aware, where feasible, and to the people affected without undue delay where the risk to them is high.

[Source →](https://www.legislation.gov.uk/eur/2016/679/article/33)

### UK NIS Regulations

Operators of essential services notify a NIS incident to their competent authority without undue delay and no later than 72 hours after becoming aware of it.

[Source →](https://www.legislation.gov.uk/uksi/2018/506/regulation/11)

Ways to start

## Start with one incident, then plan for the next

The single incident is the way in. After that, the 2 monthly plans keep you ready all year.

### Single Incident

Something has happened and you need help now

- Reporting decision for each law, on record
- First notification to each authority drafted
- Follow-up and final reports at an hourly rate
- No contract beyond the incident

Ask for Single Incident

### Ready

You want a tested process and a team that knows your set-up

- Reporting map kept current every quarter
- Reporting procedure and incident classification matrix
- One reporting drill a year

Ask for Ready

### Covered

You report often, or your supervisor expects a standing arrangement

- Everything in Ready
- All notifications and follow-ups drafted, and filed under mandate where allowed
- A yearly report to your board

Ask for Covered

### A proposal and an invoice

Monthly plans come on a contract your procurement team signs, with payment by bank transfer.

Add-ons

## Make the next incident easier

Each add-on can be agreed on its own or added to a monthly plan.

### Incident Response Plan

A plan written for your organisation that ties containment to the reporting steps and names who decides.

Ask About an Add-On →

### Plan Test

A walk-through of your plan with the people named in it, with gaps and fixes written down.

Ask About an Add-On →

### Tabletop Exercise

A realistic scenario run with your board or your operational team, ending with a short report.

Ask About an Add-On →

### Classification Matrix

The DORA, NIS2 and GDPR thresholds turned into one matrix your team can apply in minutes.

Ask About an Add-On →

### Reporting Drill

A timed practice run of the full reporting process, up to the point of submission.

Ask About an Add-On →

### Post-Incident Review

What happened, what was reported and what to change, written for your board and auditors.

Ask About an Add-On →

WORKING WITH US

## What it takes from your side

What we need during an incident, and what the Ready and Covered plans set up before one.

### One incident lead

A named person who can give us the facts and take or obtain the reporting decision.

### Your approval before anything is submitted

Every notification goes to the authority only after you approve it. The decision to report stays yours.

### Access to the portals

We prepare each report for you to submit from your own account. On the Covered plan we can file under your mandate where the authority allows it, with access set up in advance.

### Remote by default

We work by phone, video and a shared, access-controlled folder; on site only when you want it.

### Alongside your lawyers and responders

We work with your legal counsel and your incident response firm, not instead of them.

### Lessons fed back

On the Ready and Covered plans, each incident and each drill updates your classification matrix, templates and contact list.

How it works

## What happens after you accept the proposal

Four steps, each with what we do and what we need from you. The legal deadlines set the pace; which regimes apply and how many reports follow depend on the incident.

1. 1On signing
  Start
  Accept the proposal. You receive your client number for incident reports.
2. 2Within 2 working days
  Your reporting map
  Which laws apply, to which authority you report in each country, and who in your organisation decides.
3. 3When something happens
  Report the incident
  Use the incident form with your client number. If your systems are down or not safe to use, call the Intake Line. A practitioner contacts you to start the reporting decision.
4. 4Afterwards
  Close the file
  Final reports sent, questions from authorities answered and what to change next time written down.

IS IT REPORTABLE?

### See which clocks your incident starts

Our free Incident Reporting Clock shows the deadlines that may apply to an incident, by regime. When you want someone to make the call with you and draft the reports, report it through our incident form, or ask for a proposal for the Ready or Covered plan.

Get a Quote

Cover and independence

## We report with you. The incident stays yours.

### We draft, you submit

Many authority portals only accept a filing from your own login. We prepare every report and sit beside you while you submit. Filing under a mandate is part of the Covered plan where the authority allows it.

### We do not run your response

Your IT, your SOC or your incident response firm contains and recovers. We handle what the law asks you to report, which keeps our judgement independent.

### You approve every report

Nothing goes to an authority in your name without your sign-off. The duty and the decision remain with you.

Why GRC+

## Reporting is a legal judgement made under time pressure

Lawyers advise on the law and incident responders contain the attack. GRC+ makes sure every report goes to the right authority, in the right form, on time.

### GRC+

- Certified practitioners who work with these laws every week
- The deadlines taken from our own regulation database, kept current
- One team for NIS2, DORA, the GDPR and the CRA
- Professional indemnity insurance on every engagement

**Why GRC+**

|  | GRC+ | Law firm | Incident response firm | Internal team |
| --- | --- | --- | --- | --- |
| Reporting decision across every regime | YesPer regime, with the reasons on record | PartlyLegal advice, regime by regime | PartlyFocused on containment | PartlyNext to handling the incident |
| Notifications drafted, ready to submit | YesEvery notification and follow-up report | PartlyDrafts on request | NoNot in scope | PartlyIf someone knows the portals |
| One log for every deadline | YesKept from the first report to the final one | PartlyPer matter | PartlyTechnical timeline only | PartlyVaries |
| Ready before an incident | YesClassification matrix, templates and portal access in place, on the Ready and Covered plans | PartlyAdvice on request | PartlyA response plan | PartlyVaries |
| Regulators' follow-up questions | YesAnswered from one consistent file | YesYes | NoRarely | PartlyDepends on capacity |

## Delivered Work on the Same Topic

Clients are described, never named.

[NIS2 Getting the Finnish NIS2 Position Confirmed Before Acting on It Three questions an energy group settled with local counsel before acting on Finland's new NIS2 law. Read the Case](https://grc.plus/case-study/getting-the-finnish-nis2-position-confirmed-before-acting-on-it/)

[DORA Running a DORA Programme From Inside a Bank’s Task Force A principal consultant inside a bank's DORA task force: more than 200 tasks across the bank, closed at board level. Read the Case](https://grc.plus/case-study/running-a-dora-programme-from-inside-a-banks-task-force/)

[All Case Studies →](https://grc.plus/case-studies/)

SUBMITTING FOR YOU

## Where we can submit for you

On the Covered plan, where the authority accepts a report from a provider you authorise, we submit it in your name and you stay responsible for it. Everywhere else we draft every report in the authority's format for you to submit. Each line links its official source, checked on 18 November 2026.

### DORA, every EU country

Article 19(5) lets you outsource reporting to a provider; you stay responsible and tell your authority first.

[Source →](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022R2554)

### DORA, Germany (BaFin)

You send BaFin its outsourcing form; our reporters are enabled on its reporting portal.

[Source →](https://www.bafin.de/DE/unternehmen-maerkte/mvp-portal/MVP_Fachverfahren_Digital_Operational_Resilience_Act_DORA/MVP_Fachverfahren_Digital_Operational_Resilience_Act_DORA_node.html)

### DORA, France (ACPR)

You notify the ACPR first; we can submit from the next day.

[Source →](https://acpr.banque-france.fr/system/files/2025-06/Instruction_2025-I-09.pdf)

### DORA, Luxembourg (CSSF)

You inform the CSSF before the first report and name our staff for the eDesk role.

[Source →](https://www.cssf.lu/wp-content/uploads/cssf25_893eng.pdf)

### DORA, Belgium (FSMA)

The FSMA confirms reporting can be outsourced; you stay responsible.

[Source →](https://www.fsma.be/nl/faq/3-welke-vereisten-gelden-inzake-de-rapportage-van-de-incidenten-en-de-cyberdreigingen-art-19)

### NIS2, Germany (BSI)

Your BSI-Portal owner adds us as an external user for your company.

[Source →](https://www.bsi.bund.de/DE/Service-Navi/FAQ/BSI-Portal/faq_bsi-portal_node.html)

### NIS2, Italy (ACN)

You can designate us as your CSIRT contact, who notifies CSIRT Italia.

[Source →](https://www.acn.gov.it/portale/en/faq/nis/ruoli-e-procedure)

### NIS2, Denmark

The official incident form allows reporting on another organisation's behalf.

[Source →](https://virk.dk/assets/cmhIfcTaAQ7947FMPwhR1/Vejledning_indberetning_af_h%C3%A6ndelse_NIS2_v1.pdf)

### NIS2, Czechia (lower-obligation regime)

The cybersecurity role that reports through the NÚKIB Portal may be outsourced.

[Source →](https://portal.nukib.gov.cz/storage/uploads/2026/06/02/manual-nizsi-rezim-v1-1_uid_6a1eaedd0ce9f.pdf)

### Personal data breaches, Denmark

Lawyers and consultants may notify Datatilsynet for you, with your authorisation.

[Source →](https://www.datatilsynet.dk/Media/637886298435856391/H%C3%A5ndtering%20af%20brud%20p%C3%A5%20persondatasikkerheden.pdf)

### Personal data breaches, Spain

You may authorise an entity to notify the AEPD; proof of authority may be asked for.

[Source →](https://www.aepd.es/guias/guia-brechas-seguridad.pdf)

### Personal data breaches, Italy

A delegate of your legal representative may notify the Garante, who names the delegating person.

[Source →](https://servizi.gpdp.it/databreach/resource/1629905132000/DB_Istruzioni)

### Personal data breaches, Poland

A proxy may notify UODO with a power of attorney and proof of the stamp duty.

[Source →](https://uodo.gov.pl/pl/492/2278)

### Personal data breaches, Ireland

The DPC form accepts a notification on behalf of a controller, named in the form.

[Source →](https://forms.dataprotection.ie/breach-notification)

### Personal data breaches, Türkiye

A lawyer or consultant may notify the KVKK, with a contract or power of attorney attached.

[Source →](https://kvkk.gov.tr/SharedFolderServer/CMSFiles/369d954a-aaee-44ca-9ca6-105e8b4102f9.pdf)

FAQ

## Incident Reporting Desk: questions buyers ask first

Something else? Ask us in a 30-minute call.

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)

**Which incidents do we have to report, and to whom?**

It depends on your sector, your market and what the incident affected. A significant incident goes to your CSIRT or competent authority under [NIS2](/regulation/nis2/) and its national law; a major ICT-related incident goes to your financial supervisor under [DORA](/regulation/digital-operational-resilience-act-dora/); a personal data breach goes to the data protection authority under [GDPR](/regulation/general-data-protection-regulation-gdpr/); and manufacturers report actively exploited vulnerabilities and severe incidents under the [Cyber Resilience Act](/regulation/cyber-resilience-act-cra/). One incident can fall under several of these at once. We assess each with you and record the decision.

**When does the clock start?**

Not always at the same moment. Under [NIS2](/regulation/nis2/), [GDPR](/regulation/general-data-protection-regulation-gdpr/) and the [CRA](/regulation/cyber-resilience-act-cra/) it runs from when you become aware. Under [DORA](/regulation/digital-operational-resilience-act-dora/) the initial notification is due within 4 hours of classifying the incident as major, and at the latest 24 hours after you became aware. Under [NYDFS Part 500](/regulation/nydfs-cybersecurity-regulation-23-nycrr-500/) it runs from your determination that a cybersecurity incident occurred, and under the [SEC requirements](/regulation/sec-cybersecurity-disclosure-rules/) from your decision that it is material, which must be made without unreasonable delay. Our deadline log records each start time.

**Do you replace our lawyers or our incident response firm?**

No. We work alongside them. Your incident response firm contains and investigates the incident, your legal counsel advises on liability and legal privilege, and we make sure every report goes to the right authority, in the right form, on time. GRC+ does not give legal advice.

**We report in the United States or the United Kingdom. Is that covered?**

Yes. In the United States we cover Form 8-K Item 1.05 under the [SEC cybersecurity disclosure requirements](/regulation/sec-cybersecurity-disclosure-rules/) (within four business days of the materiality decision) and notices under [NYDFS Part 500](/regulation/nydfs-cybersecurity-regulation-23-nycrr-500/) (within 72 hours, and 24 hours for an extortion payment). In the United Kingdom we cover breach reports under [UK GDPR](/regulation/uk-general-data-protection-regulation-uk-gdpr/) and NIS incident notices under the [UK NIS Regulations](/regulation/uk-network-and-information-systems-regulations-2018/), both within 72 hours. We follow changes to the UK requirements as they are made.

**What changed for manufacturers in September 2026?**

Since 11 September 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities and severe incidents under the [Cyber Resilience Act](/regulation/cyber-resilience-act-cra/): an early warning within 24 hours, a notification within 72 hours and a final report, through the single reporting platform to the CSIRT coordinator and ENISA. This applies to products already on the market, not only to new ones.

**Do you file the reports for us?**

On the Covered plan, where the authority accepts it, yes: we submit in your name under your authorisation, and you stay responsible for the report. That is confirmed for DORA reports across the EU, NIS2 reports in Germany, Italy, Denmark and the Czech lower-obligation regime, and personal data breach notifications in Denmark, Spain, Italy, Poland, Ireland and Türkiye. On Single Incident and Ready, and wherever the portal login is tied to your own registration, we draft each report in the authority’s format for you to submit. The list on this page links each source.

**Want to know more about NIS2?**

Our guide to NIS2 explains who it applies to, what it requires, the deadlines and what happens if you do not comply. [Network and Information Security Directive (NIS2) →](https://grc.plus/regulation/nis2/)

Prefer a proposal?

## The same service, with a proposal, a contract and an invoice

Tell us your set-up and a principal consultant sends the scope and a fixed fee within 2 working days.

Get a Proposal

### Service Sheet

How to report an incident to us, the deadlines we cover and the ways to work with us, to send to your board and procurement.

[Download the Service Sheet](https://grc.plus/service/incident-reporting-desk/pdf/?v=2efc9b9e)

## Know where to report before the clock starts

Tell us who you are and the regimes you report under. We will help clarify the scope and the information needed for a written proposal. You can share details of past incidents and documents after confidentiality arrangements are agreed. [sales@grc.plus](mailto:sales@grc.plus)  [+31 20 241 66 00](tel:+31202416600)

[Not ready to talk yet? Read our NIS2 guide →](https://grc.plus/regulation/nis2/)

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)

Get a Quote
