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.
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 responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state. 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.
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.
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.
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?
What asks for it in Slovenia
We scope the work to what your requirement asks for, so the result serves that audit or supervisor too.
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.
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.
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.
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.
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.
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.
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.
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.
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
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
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
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.
Plan Test
A walk-through of your plan with the people named in it, with gaps and fixes written down.
Tabletop Exercise
A realistic scenario run with your board or your operational team, ending with a short report.
Classification Matrix
The DORA, NIS2 and GDPR thresholds turned into one matrix your team can apply in minutes.
Reporting Drill
A timed practice run of the full reporting process, up to the point of submission.
Post-Incident Review
What happened, what was reported and what to change, written for your board and auditors.
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.
1On signing
Start
Accept the proposal. You receive your client number for incident reports.
2Within 2 working days
Your reporting map
Which laws apply, to which authority you report in each country, and who in your organisation decides.
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.
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.
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 ITInformation Technology, your SOCSecurity Operations Centre or your incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state. 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.
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.
DORA, Germany (BaFin)
You send BaFin its outsourcing form; our reporters are enabled on its reporting portal.
DORA, France (ACPR)
You notify the ACPR first; we can submit from the next day.
DORA, Luxembourg (CSSF)
You inform the CSSF before the first report and name our staff for the eDesk role.
DORA, Belgium (FSMA)
The FSMA confirms reporting can be outsourced; you stay responsible.
NIS2, Germany (BSI)
Your BSI-Portal owner adds us as an external user for your company.
NIS2, Italy (ACN)
You can designate us as your CSIRT contact, who notifies CSIRT Italia.
NIS2, Denmark
The official incident form allows reporting on another organisation's behalf.
NIS2, Czechia (lower-obligation regime)
The cybersecurity role that reports through the NÚKIB Portal may be outsourced.
Personal data breaches, Denmark
Lawyers and consultants may notify Datatilsynet for you, with your authorisation.
Personal data breaches, Spain
You may authorise an entity to notify the AEPD; proof of authority may be asked for.
Personal data breaches, Italy
A delegate of your legal representative may notify the Garante, who names the delegating person.
Personal data breaches, Poland
A proxy may notify UODO with a power of attorney and proof of the stamp duty.
Personal data breaches, Ireland
The DPC form accepts a notification on behalf of a controller, named in the form.
Personal data breaches, Türkiye
A lawyer or consultant may notify the KVKK, with a contract or power of attorney attached.
FAQ
Incident Reporting Desk: questions buyers ask first
Something else? Ask us in a 30-minute call.
Which incidents do we have to report, and to whom?
It depends on your sector, your market and what the incident affected. A significant incidentUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. goes to your CSIRTComputer Security Incident Response Team or competent authority under NIS2 and its national law; a major ICT-related incidentAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. goes to your financial supervisor under DORA; a personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms. goes to the data protection authorityAn independent public body that supervises compliance with data protection law. Under the GDPR, such authorities monitor and enforce its application, handle complaints and exercise investigative and corrective powers. under GDPR; and manufacturers report actively exploited vulnerabilitiesA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. and severe incidents under the Cyber Resilience Act. 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, GDPR and the CRA it runs from when you become aware. Under 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 it runs from your determination that a cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. incident occurred, and under the SEC requirements 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 (within four business days of the materiality decision) and notices under NYDFS Part 500 (within 72 hours, and 24 hours for an extortion payment). In the United Kingdom we cover breach reports under UK GDPR and NIS incident notices under the UK NIS Regulations, 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 vulnerabilitiesA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. and severe incidents under the Cyber Resilience Act: an early warning within 24 hours, a notification within 72 hours and a final report, through the single reporting platform to the CSIRTComputer Security Incident Response Team coordinator and ENISAEuropean Union Agency for Cybersecurity. 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) →
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.
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.
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 +31 20 241 66 00

