Skip to main content
Back to overview

NIS2 Near Miss Reporting: What Article 30 Lets Your Clients Send, and What It Does Not Oblige

By NIS2Certify
nis2article-30near-missincident-reportingmsp
NIS2 Near Miss Reporting: What Article 30 Lets Your Clients Send, and What It Does Not Oblige

Your SOC blocks a credential-stuffing run against a client's VPN at 02:10. Nothing is encrypted, nothing is exfiltrated, no service goes down. By 09:00 the ticket is closed as "no impact". Under NIS2, was that an event you had to report? No. Was it an event you were allowed to report? Yes, and Article 30 is the reason.

Most MSPs know the mandatory clock in Article 23. Far fewer know the voluntary channel next to it. That gap is where good clients get better, and where careless advice creates risk.

NIS2 near miss reporting: what Article 30 actually says

Article 30 of Directive (EU) 2022/2555 is titled "Voluntary notification of relevant information". It sits in Chapter VI, next to the information-sharing arrangements of Article 29.

Paragraph 1 says that, in addition to the mandatory notification under Article 23, member states must ensure entities can notify their CSIRT (or, where applicable, the competent authority) on a voluntary basis. Essential and important entities may report incidents, cyber threats and near misses. Other entities, in scope or not, may report significant incidents, cyber threats and near misses.

A near miss, as defined in Article 6, is an event that could have compromised the availability, authenticity, integrity or confidentiality of data or services, but was prevented or did not materialise. The blocked login run above fits. So does a phishing email that a user reported before anyone clicked.

Two details matter for your advice. First, the channel is open to entities outside NIS2 scope, which includes many of your smaller clients. Second, a voluntary report is not a lesser report: the CSIRT handles it under the same procedure as Article 23 notifications.

Voluntary does not mean free of rules

Paragraph 2 contains the sentence MSPs should quote to nervous clients: voluntary notification must not result in any additional obligations for the notifying entity that it would not have been subject to had it not made the notification.

In plain terms, sending a near-miss report does not make your client a worse supervised entity. It does not open a new reporting duty and it does not lower the bar for what counts as significant.

It also does not suspend anything. If the same event later turns out to meet the threshold of Article 23(3), meaning severe operational disruption or financial loss, or considerable damage to others, the mandatory clock applies to that incident. Authorities may also prioritise mandatory notifications over voluntary ones, so do not expect a fast reply to a near-miss report.

Where voluntary reporting meets the mandatory clock

The mistake we see is treating Article 30 as a way to park a doubtful incident. If you are unsure whether an event is significant, the answer is a documented assessment, not a voluntary label. For the mandatory side, see our guide to the 24-hour, 72-hour and one-month deadlines.

NIS2 Incident Reporting Timeline

24h

Early Warning

Notify the competent authority (CSIRT/NCA) within 24 hours of becoming aware of a significant incident.

72h

Incident Notification

Submit a detailed notification within 72 hours with an initial assessment of severity, impact and indicators of compromise.

1mo

Final Report

Deliver a comprehensive final report within one month covering root cause, remediation taken and cross-border impact.

A workable rule: when the event has already caused disruption, run the Article 23 assessment first. When nothing happened and the control worked, consider a voluntary report. Either way, record the decision and the reasoning. An auditor will ask for it, as we describe in the incident handling article on Article 21(2)(b).

Personal data adds a second track. A near miss without data exposure rarely triggers GDPR, but any event that touches personal data needs the parallel assessment covered in one breach, two clocks.

Why a client would send one

Three practical reasons come up with MSP clients.

Early warning for others. A CSIRT that sees the same phishing kit or the same exploited appliance from several entities can warn the sector. Your client contributes without disclosing anything beyond the report.

Evidence of a working programme. A log of near misses, each with detection, response and a decision on reporting, is proof that Article 21 measures operate. It is better evidence than a policy document.

A relationship before a crisis. The first contact with a CSIRT should not be a 24-hour early warning at 03:00. A client that has already used the portal knows the form, the contact and the tone.

The costs are real but small: staff time, and a duty to be accurate. Do not report what you cannot describe.

Five national routes, five different realities

The directive sets the floor. The channel, portal and exact wording depend on national law, and member states are at different points.

NIS2 transposition by country

  • AustriaIn force
    • In force since October 1, 2026
    • Act: NISG 2026 (BGBl. I Nr. 94/2025)
    • Registration due December 31, 2026

    Authority: Federal Office for Cybersecurity Β· Source

  • NetherlandsIn force
    • In force since August 15, 2026
    • Act: Cyberbeveiligingswet (Stb. 2026, 187)
    • Registration required, no transition period

    Authority: NCSC (MijnNCSC) Β· Source

  • LuxembourgIn force
    • In force since May 10, 2026
    • Act: Law of 5 May 2026
    • Registration due July 10, 2026

    Authority: ILR (CSSF for finance) Β· Source

  • PolandIn force
    • In force since April 3, 2026
    • Act: UKSC (Dz.U. 2026 poz. 252)
    • Registration due October 3, 2026
    • Measures due April 3, 2027

    Authority: Minister Cyfryzacji (Wykaz KSC) Β· Source

  • PortugalIn force
    • In force since April 3, 2026
    • Act: Decree-Law 125/2025 (RJC)

    Authority: CNCS Β· Source

  • BulgariaIn force
    • In force since February 13, 2026
    • Act: Cybersecurity Act amendment (State Gazette No 17/2026)

    Authority: Ministry of e-Government Β· Source

  • MaltaIn force
    • In force since January 23, 2026
    • Act: S.L. 460.41

    Authority: Critical Infrastructure Protection Department Β· Source

  • SwedenIn force
    • In force since January 15, 2026
    • Act: SFS 2025:1506

    Authority: NCSC-SE Β· Source

  • EstoniaIn force
    • In force since January 1, 2026
    • Act: Cybersecurity Act (KΓΌTS) amendment
    • Registration within 3 months

    Authority: RIA Β· Source

  • GermanyIn force
    • In force since December 6, 2025
    • Act: NIS2UmsuCG
    • Registration due March 6, 2026
    • 17,729 registered by June 30, 2026

    Authority: BSI Β· Source

  • CzechiaIn force
    • In force since November 1, 2025
    • Act: Act No 264/2025 Coll.
    • Registration within 60 days

    Authority: NÚKIB · Source

  • DenmarkIn force
    • In force since July 1, 2025
    • Act: NIS 2 Act No 434 of 6 May 2025
    • Registration due October 1, 2025

    Authority: Danish Agency for Societal Security Β· Source

  • SloveniaIn force
    • In force since June 19, 2025
    • Act: ZInfV-1 (OG 40/25)
    • Registration within 30 days

    Authority: URSIV Β· Source

  • CyprusIn force
    • In force since April 25, 2025
    • Act: Law 60(I)/2025

    Authority: Digital Security Authority Β· Source

  • FinlandIn force
    • In force since April 8, 2025
    • Act: Cybersecurity Act 124/2025
    • Registration due May 8, 2025
    • Measures due July 8, 2025

    Authority: Traficom (NCSC-FI) Β· Source

  • HungaryIn force
    • In force since January 1, 2025
    • Act: Act LXIX of 2024

    Authority: SZTFH Β· Source

  • SlovakiaIn force
    • In force since January 1, 2025
    • Act: Act No 366/2024 Coll.
    • Registration within 60 days

    Authority: NBÚ · Source

  • RomaniaIn force
    • In force since December 31, 2024
    • Act: GEO 155/2024 (Law 124/2025)
    • Registration within 30 days

    Authority: DNSC Β· Source

  • GreeceIn force
    • In force since November 27, 2024
    • Act: Law 5160/2024 (Gazette A' 195)

    Authority: National Cybersecurity Authority Β· Source

  • BelgiumIn force
    • In force since October 18, 2024
    • Registration due March 18, 2025

    Authority: CCB Β· Source

  • LithuaniaIn force
    • In force since October 18, 2024
    • Act: Law No XIV-2902

    Authority: NCSC (MoND) Β· Source

  • ItalyIn force
    • In force since October 16, 2024
    • Act: D.Lgs. 138/2024
    • Baseline measures due by October 2026 (entities listed in 2025)

    Authority: ACN Β· Source

  • LatviaIn force
    • In force since September 1, 2024
    • Act: National Cybersecurity Law

    Authority: National Cybersecurity Centre Β· Source

  • CroatiaIn force
    • In force since February 15, 2024
    • Act: Cybersecurity Act (OG 14/2024)

    Authority: NCSC (SOA) Β· Source

  • FranceNot yet transposed
    • Senate adopted the law on March 12, 2025
    • Regulator published its framework on March 17, 2026
    • Referred to the Court of Justice on July 8, 2026
    • Pre-registration open

    Authority: ANSSI Β· Source

  • SpainNot yet transposed
    • Draft bill approved on January 14, 2025
    • Referred to the Court of Justice on July 8, 2026
    • The NIS1 regime still applies

    Authority: CCN / INCIBE Β· Source

  • IrelandNot yet transposed
    • Referred to the Court of Justice on July 8, 2026
    • Bill not yet enacted

    Authority: NCSC Ireland Β· Source

Status as of September 28, 2026. Other member states: see the country-by-country timeline.

Netherlands. The Cyberbeveiligingswet has applied since 15 August 2026. The NCSC explicitly invites organisations to make voluntary reports of non-significant incidents and near misses, through its portal at mijn.ncsc.nl. A voluntary report goes to the sectoral CSIRT, not to the supervisor.

Italy. Article 26 of Legislative Decree 138/2024 provides the voluntary route, to CSIRT Italia, on top of the mandatory notification in Article 25. Paragraph 26.1(a) covers essential and important entities; 26.1(b) covers other entities.

Germany. The NIS2 Implementation Act amended the BSI Act and the BSI is the reporting counterpart. Check the current BSI portal for the voluntary form before you advise, as we have not confirmed the section numbering for this article.

Poland. The amended national cybersecurity system act is in force, with the sectoral CSIRTs NASK, GOV and MON as recipients depending on the entity. Confirm which one applies to your client.

France and Spain. Neither has transposed the directive. ANSSI's CERT-FR and, in Spain, INCIBE-CERT and CCN-CERT already take reports, but these are not Article 30 channels in law. Advise clients to use them as good practice, not as a legal route.

What to put in place for your clients

Add three lines to your incident runbook. One: every blocked or contained event gets a near-miss record. Two: a named person decides, in writing, whether it is reported voluntarily, mandatorily or not at all. Three: the CSIRT contact and portal for each country you serve are stored with the client file.

Then test it once. Pick a recent blocked event and walk it through your own process. If nobody can say who would have decided, you have found a gap that no regulator needs to find for you.

Wondering how your clients' incident handling holds up? Run a free NIS2 quick scan and see where reporting and detection controls stand.

Article 30 is a small provision. Used well, it turns routine blocked attacks into evidence, and gets your clients to the CSIRT before they need it.

Still have a question?

Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.