Austria's NISG 2026 Is Live: What EU Suppliers Need to Know

Austria published the NISG 2026 in the Federal Law Gazette on 23 December 2025. It enters into force on 1 October 2026. The number of in-scope organisations jumps from roughly 100 under the old regime to an estimated 4,000.
If you advise Austrian clients — or run a business anywhere in the EU that supplies one — that date is now a hard line in your project plan. After 1 October, registration is mandatory, the management board is personally on the hook, and the supply-chain clauses pull in vendors that aren't even directly regulated.
Here's what changed, who it catches, and what you should be doing in the next three months.
The NISG 2026 replaces a law that covered almost nobody
Austria's original NIS Act applied to about 100 operators of essential services. That was the whole point of NIS2 across the EU: the first directive was too narrow, so the second one widened the net dramatically.
The NISG 2026 is the result. It transposes Directive (EU) 2022/2555 and mirrors its structure exactly — Annex I for essential-entity sectors, Annex II for important-entity sectors. Telecoms, financial services, energy, transport, health, digital infrastructure, public administration, and even licensed gambling operators are now in scope.
The size threshold is the standard EU medium-enterprise test: 50 or more employees, or annual turnover and balance-sheet total above EUR 10 million. Hit either and you're presumptively covered. Some entities — public electronic communications network providers, for example — are caught regardless of size.
That's how you get from 100 to 4,000.
Essential versus important decides how hard the authority hits you
The classification isn't cosmetic. It changes your penalty ceiling and how closely the regulator watches you.
Essential entities (Annex I) face administrative fines up to EUR 10 million or 2% of global annual turnover, whichever is higher. They're subject to proactive supervision — the authority can audit you without waiting for an incident.
Important entities (Annex II) face fines up to EUR 7 million or 1.4% of global turnover, and supervision is reactive — the authority steps in after something goes wrong or a complaint lands.
Most consultants' clients will land in the important-entity bucket. That's not a reason to relax. The obligations are nearly identical; only the enforcement posture and the fine ceiling differ.
Does NIS2 Apply to Your Organisation?
Does your organisation operate in an essential or important sector (energy, transport, health, digital infrastructure, etc.)?
Does your organisation have 50 or more employees, or both an annual turnover and a balance sheet total exceeding €10 million?
NIS2 does not directly apply to your organisation.
NIS2 applies to your organisation as an Essential or Important Entity.
Is your organisation a critical infrastructure provider or a qualified trust service provider?
NIS2 may apply to your organisation — seek legal advice to confirm your status.
Does your organisation operate in an essential or important sector (energy, transport, health, digital infrastructure, etc.)?
Does your organisation have 50 or more employees, or both an annual turnover and a balance sheet total exceeding €10 million?
Is your organisation a critical infrastructure provider or a qualified trust service provider?
NIS2 does not directly apply to your organisation.
NIS2 applies to your organisation as an Essential or Important Entity.
NIS2 may apply to your organisation — seek legal advice to confirm your status.
Registration closes on 31 December 2026 — and it's the easy part
Once the law enters into force on 1 October, covered entities have three months to register with the NIS Anlaufstelle, the national contact point run under the Federal Ministry of the Interior. That puts the hard deadline at 31 December 2026.
Miss it and the fine is up to EUR 50,000 for a first offence, rising to EUR 100,000 for repeat failures. Those numbers are small next to the multi-million-euro ceilings for substantive breaches, but registration is also the moment you put yourself on the regulator's radar. Late or missing registration is the easiest possible thing for an authority to spot and penalise.
Treat registration as a deadline, not a project. The real work is everything the registration commits you to: the risk-management measures under Article 21, incident reporting, and supply-chain controls.
The board carries the obligation — not the IT department
This is the part Austrian executives keep underestimating. Under the NISG 2026, responsibility for implementing and monitoring cybersecurity risk-management measures sits explicitly with the management board or executive directors.
You cannot delegate this to the CISO and walk away. The board must approve the measures, oversee them, and — under the directive's logic — can be held personally liable for failures. Management is also required to undergo cybersecurity training.
For consultants, this is your opening. The conversation that gets you in the door isn't "your firewall needs work." It's "your directors are now personally accountable for a control framework they've never seen." Brief the board first. The budget follows.
Article 21 — 10 NIS2 Cybersecurity Measures
Article 21
10 Cybersecurity Measures
Governance & Strategy
Incident & Continuity
Supply Chain & Systems
Technical Controls
People & Assets
The supply-chain clause catches companies that aren't even in scope
Here's the provision with the longest reach. The NISG 2026 requires covered entities to assess and contractually secure the cybersecurity of their direct suppliers and service providers.
That means a regulated Austrian entity will push security requirements down its contracts. Even a company that falls below the size thresholds — and is therefore not directly regulated — can be required to provide security evidence as a condition of staying in the supply chain.
If your client sells to a hospital, a bank, an energy operator, or a telecoms firm in Austria, expect security questionnaires, contractual clauses, and audit rights to start appearing in renewal negotiations. The regulated buyer has a legal obligation to demand them.
This is the mechanism that makes NIS2 a market force, not just a compliance line item. A small MSP in Vienna with zero direct obligation can still lose a contract for failing a customer's vendor assessment. For the deeper mechanics of how this works in practice, see our guide on NIS2 supply-chain security and the detail on supplier contracts under Article 21.
NIS2 Penalty Escalation — Beyond the Fine
Trigger event
Non-Compliance Detected or Incident Occurs
A supervisory authority identifies a compliance gap or an organisation fails to meet NIS2 requirements
Compliance orders with binding deadlines
Mandatory security audits at your expense
Public disclosure of violations
Binding instructions on specific security measures
Suspension of certifications or operating licences
Temporary ban on management functions for individuals
Public naming of responsible natural persons
Austria joins a fast-closing group of transposed states
Austria isn't an outlier any more. As of early 2026, 21 of 27 member states had transposed NIS2, and the European Commission referred the laggards to the Court of Justice. Germany flipped its switch, Belgium's audit regime is running, and France, Portugal, and Poland are all live.
For a consultant or MSP working across borders, the practical takeaway is that the patchwork is hardening into a baseline. A client operating in Austria, Germany, and Belgium can't run three different compliance postures. The smart move is to build one Article 21-aligned control set and map it to each national flavour.
The national variations matter at the edges — registration portals, exact deadlines, fine ceilings — but the core risk-management obligations are the same directive underneath. Get the core right once and the per-country work shrinks to paperwork.
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.
What to do before 1 October 2026
The window is short and the sequence matters. If you're advising an Austrian client, work it in this order.
First, confirm scope. Run the size threshold and sector check now, before October, so the client knows whether they're essential, important, or out. Don't assume — the gambling and digital-infrastructure inclusions catch organisations that never thought of themselves as critical.
Second, brief the board. Get the personal-liability and training obligations in front of the management directors early. This is what unlocks budget and authority.
Third, run a gap analysis against Article 21. The ten measures are the substance of compliance, and most organisations have three or four of them half-implemented at best. Our step-by-step gap-analysis guide walks through the process.
Fourth, register before 31 December 2026. Once scope is confirmed, registration is administrative — but don't let it slip past the deadline.
Fifth, fix the supply chain. Map your client's critical suppliers and start the contractual work now. This is the slowest item because it depends on counterparties, so begin early.
If you want to know where a specific organisation stands today, the fastest starting point is a structured readiness assessment that scores them against every Article 21 measure and flags the gaps. Run the NIS2 quick scan and you'll have a prioritised picture in minutes — exactly the kind of evidence the board, and an Austrian supplier's customers, will want to see.
The NISG 2026 has been law since December. The clock to 1 October is already running.
Still have a question?
Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.
