Skip to content

Solution · NIS2 and NISG 2026

Putting NIS2 into practice

Austria's NISG 2026 has been in force since 1 October 2026. We show what NIS2 requires technically and which measures blacklens.io, ACDC and our consulting team support.

NISG 2026 · Austria

Effective date

in force

Austria's transposition of Directive (EU) 2022/2555 (NIS2).

From EU law to the NISG 2026

  1. 2022Directive (EU) 2022/2555 (NIS2)
  2. 17 Oct 2024Deadline for transposition into national law
  3. 23 Dec 2025Published as BGBl. I Nr. 94/2025
  4. 1 Oct 2026NISG 2026 in force
Technical guidance, not legal advice.

Overview

What is NIS2?

NIS2, Directive (EU) 2022/2555, obliges essential and important entities to manage cybersecurity risks and report significant incidents, and holds their management bodies accountable; in Austria it is transposed by the NISG 2026. snapSEC GmbH from Vorchdorf supports companies in Austria, Germany and Switzerland with the technical implementation through blacklens.io, ACDC and consulting. Technical guidance, not legal advice.

At a glance

NIS2
EU legal basis
Directive (EU) 2022/2555 (NIS2), to be transposed by member states by 17 October 2024 (Art. 41)
Austria
NISG 2026, BGBl. I Nr. 94/2025, in force since 1 October 2026
In scope
Essential and important entities in 18 sectors (Annexes I and II)
Risk management
Ten minimum areas under Art. 21(2)
Reporting
24 hours, 72 hours, one month (Art. 23)
Accountability
Management bodies approve and oversee the measures (Art. 20)
snapSEC's part
Technical implementation with blacklens.io, ACDC and consulting
Not included
Legal advice, audits and certifications

Art. 23 NIS2

Reporting deadlines for significant incidents

Three deadlines run from the moment you become aware of a significant incident. Your company must report; ACDC and a managed SIEM provide the technical basis.

Who does what?

  • ACDCDetect, assess and escalate around the clock
  • Managed SIEMCentral logs for the timeline, including before the incident
  • Your companyReports to the CSIRT or the competent authority
  1. 0 hBecoming aware of the incidentThe clock starts here
  2. 24 hEarly warningWithout undue delay, at the latest 24 hours after becoming aware; where applicable, indicating whether unlawful or malicious acts are suspected or the incident could have a cross-border impact.
  3. 72 hIncident notificationAt the latest 72 hours after becoming aware, with an initial assessment of severity and impact.
  4. 1 monthFinal reportAt the latest one month after the notification, with a description, the root cause and the mitigation measures applied.
To the CSIRT or the competent authority (Art. 23). In Austria, entities report to the competent sector-specific CSIRT or, if there is none, to the national CSIRT. The CSIRT forwards the report to the cybersecurity authority (§ 34 NISG 2026).On request, an intermediate report as well

What NIS2 requires

What does NIS2 require of companies?

Member states had to transpose the directive into national law by 17 October 2024. In practice, four areas matter most.

  1. Art. 20

    Management is accountable

    Management bodies approve and oversee the measures and can be held liable for infringements. Training is mandatory for them.

  2. Art. 21

    Manage risks

    Appropriate and proportionate technical, operational and organisational measures based on an all-hazards approach.

  3. Art. 23

    Report incidents

    Report significant incidents in three stages: early warning, incident notification and final report.

  4. Art. 32–34

    Supervision and fines

    Authorities can inspect and issue binding instructions. Maximum fines are also linked to worldwide annual turnover.

SourcesDirective (EU) 2022/2555 on EUR-Lex (opens an external website)NISG 2026 in the RIS (BGBl. I Nr. 94/2025) (opens an external website)

Scope

Who is affected by NIS2?

Sector and size decide. The directive lists 18 sectors in two annexes.

Annex I

Sectors of high criticality

  • Energy
  • Transport
  • Banking
  • Financial market infrastructures
  • Health
  • Drinking water
  • Waste water
  • Digital infrastructure
  • ICT service management (B2B)
  • Public administration
  • Space

Annex II

Other critical sectors

  • Postal and courier services
  • Waste management
  • Chemicals: manufacture, production, distribution
  • Food: production, processing, distribution
  • Manufacturing, e.g. medical devices, electronics, machinery, vehicles
  • Digital providers
  • Research
  • Size

    Usually medium-sized and large enterprises (Recommendation 2003/361/EC): 50 or more staff, or turnover and balance sheet total both above EUR 10 million.

  • Regardless of size

    For example providers of public electronic communications services, trust service providers, TLD name registries and DNS service providers (Art. 2(2)).

  • Essential or important

    The classification mainly determines the type of supervision and the range of fines. The Art. 21 measures apply to both.

  • Suppliers

    Companies outside the scope often feel NIS2 through contractual requirements from customers who must secure their supply chain.

Whether your company is in scope follows from national law; in Austria, the NISG 2026. This overview does not replace a legal assessment.

Mapping

Which service supports which measure?

The ten areas of Art. 21(2) and the reporting obligations of Art. 23, mapped to blacklens.io, ACDC and consulting. Dashed: tasks that stay within your organisation.

Mapping of NIS2 measures to snapSEC services
Measure blacklens.io ACDC Consulting Your organisation
Art. 21(2)(a)Risk analysis and information system securityPolicies to assess risks and secure systems.no direct contribution
  • Document the risk analysis
Art. 21(2)(b)Incident handlingDetect, assess, contain and follow up on incidents.
  • Incident response plan and roles
Art. 21(2)(c)Business continuity and crisis managementBackup management, disaster recovery, crisis management.no direct contributionno direct contribution
  • Backup, recovery and crisis plans
Art. 21(2)(d)Supply chain securitySecurity aspects of relationships with direct suppliers and service providers.no direct contributionno direct contribution
  • Supplier requirements in contracts
Art. 21(2)(e)Security in acquisition, development and maintenanceIncluding vulnerability handling and disclosure.no direct contribution
  • Vulnerability disclosure process
Art. 21(2)(f)Assessing effectivenessPolicies and procedures to assess whether the measures work.no direct contribution
  • Report results to management
Art. 21(2)(g)Cyber hygiene and trainingBasic cyber hygiene practices and cybersecurity training.no direct contributionno direct contribution
  • Awareness training
Art. 21(2)(h)Cryptography and encryptionPolicies and procedures for cryptography and, where appropriate, encryption.no direct contributionno direct contribution
  • Define a cryptography policy
Art. 21(2)(i)HR security, access control and asset managementHuman resources security, access control policies, asset management.no direct contribution
  • Access rights policy
Art. 21(2)(j)Multi-factor authentication and secured communicationsMFA or continuous authentication, secured voice, video, text and emergency communications.no direct contributionno direct contribution
  • Secured emergency communications
Art. 23Reporting obligationsEarly warning within 24 hours, notification within 72 hours, final report within one month of the notification.no direct contribution
  • Report to the CSIRT or authority

Mapping based on Art. 21(2) and Art. 23 of Directive (EU) 2022/2555. Technical guidance, not legal advice; no audit and no certification.

Please note

Technical guidance, not legal advice.

snapSEC does not carry out audits or certifications. Which obligations apply to your company is for you to clarify with your legal adviser, your auditor or the competent authority.

Not part of our offering: Legal advice, a binding assessment of whether you are in scope, audits and certifications. These are matters for legal advisers, auditors and authorities.

Three business units

What snapSEC can take on for NIS2

For the technical core of NIS2: see the attack surface, detect incidents, test effectiveness. Use them on their own or combined.

  1. See · Platform

    blacklens.io

    snapSEC GmbH's platform shows your attack surface the way attackers see it.

    Learn more
    • Continuously map the attack surface and external assets
    • Manage vulnerabilities internally, externally and in the cloud
    • Monitor suppliers for ransomware leaks
    • Find leaked credentials on the dark web
  2. Detect · Managed SOC

    ACDC – Active Cyber Defense Center

    The managed SOC monitors your environment around the clock and supports you with incidents. Operated by Active Cyber Defense Center Service GmbH

    Learn more
    • 24/7 monitoring and detection
    • Triage and escalation paths agreed with you
    • Support with forensic analysis and containment
    • Support with compliance requirements such as NIS2
  3. Test · Consulting

    Consulting

    Our consultants test whether your measures hold up in a real attack.

    Learn more
    • Penetration testing and red teaming
    • Phishing simulations and media drop tests
    • Cloud security assessment for Microsoft 365 and Azure
    • Managed SIEM for central logs kept for the long term

Process

Four steps to the technical implementation

A pragmatic path: visibility first, then detection, then regular testing.

  1. Clarify the starting point

    Whether and how you are in scope is for your legal adviser. With us you discuss the technical starting point and priorities.

  2. Make the attack surface visible

    blacklens.io maps externally reachable systems, vulnerabilities and dark web findings, and keeps that picture up to date.

  3. Detect and respond

    ACDC monitors around the clock. Alternatively, snapSEC runs a managed SIEM with which your team detects threats itself.

  4. Test effectiveness

    Pentests, red teaming, phishing simulations and cloud assessments show whether the measures work, with reports for your documentation.

FAQ

Frequently asked questions about NIS2

Is my company affected by NIS2?

That depends mainly on sector and size. Directive (EU) 2022/2555 covers entities in 18 sectors listed in Annexes I and II, usually from medium size upwards: 50 or more staff, or annual turnover and balance sheet total both above EUR 10 million. Some entities are covered regardless of size. National law is decisive; in Austria, that is the NISG 2026. The binding assessment is for you and your legal adviser; we support the technical implementation.

What does the NISG 2026 mean for companies in Austria?

The NISG 2026 is Austria's transposition of NIS2. It was published as BGBl. I Nr. 94/2025 and has been in force since 1 October 2026. Entities in scope must implement risk-management measures, report significant incidents on time and ensure their management bodies take responsibility. Specific obligations such as registration and deadlines follow from the text of the act; have them checked by a legal adviser. For sites in other EU member states, the local transposition act generally applies.

Which deadlines apply to security incidents?

For significant incidents, Art. 23 NIS2 sets three stages: an early warning without undue delay and at the latest 24 hours after becoming aware, an incident notification at the latest 72 hours after becoming aware with an initial assessment, and a final report at the latest one month after the notification. Reports go to the CSIRT or the competent authority. That only works if incidents are detected and evidenced quickly; ACDC's 24/7 monitoring and a managed SIEM with central logs help here.

Which measures does Art. 21 NIS2 require?

Art. 21(2) lists ten minimum areas: risk analysis and information system security, incident handling, business continuity with backup and crisis management, supply chain security, security in acquisition, development and maintenance including vulnerability handling, assessing effectiveness, cyber hygiene and training, cryptography, human resources security with access control and asset management, and multi-factor authentication and secured communications. The measures must be appropriate and proportionate.

What can snapSEC take on for NIS2?

snapSEC takes on key technical parts of the implementation. blacklens.io continuously shows your attack surface, vulnerabilities and supply chain risks. ACDC – Active Cyber Defense Center monitors your environment around the clock and supports incident handling. Our consultants test effectiveness with penetration tests, red teaming, phishing simulations and cloud security assessments, and can run a managed SIEM for you. Organisational tasks such as policies, contingency plans and training concepts remain with you.

Does this replace legal advice or an audit?

No. This page and our services provide technical guidance, not legal advice. snapSEC does not carry out audits and does not issue certificates or confirmations of compliance. Which obligations apply to your company, whether you count as an essential or important entity, and how you register and report incidents are questions for your legal adviser, your auditor or the competent authority. We implement technical measures and deliver results you can include in your documentation.

What responsibility does senior management carry?

Management bodies carry the responsibility themselves. Under Art. 20 NIS2 they approve the cybersecurity risk-management measures, oversee their implementation and can be held liable for infringements. Their members must also follow training so that they can identify risks and assess cybersecurity risk-management practices. Operational implementation can be delegated; management's accountability remains. How the NISG 2026 regulates liability in detail is something to have checked by a legal adviser.

Does NIS2 also apply to suppliers?

Directly only if the supplier is itself in scope. Indirectly, often yes: Art. 21 requires entities in scope to address the security of their supply chain, including their relationships with direct suppliers and service providers. That is why many companies pass security requirements on to their suppliers by contract. blacklens.io helps on both sides, for example by monitoring suppliers for ransomware leaks and keeping a continuous view of your own attack surface.

First conversation

NIS2 starts with a plan.

Talk to us about your technical starting point. We will show where blacklens.io, ACDC and our consulting team can help, and where you need to act yourself.

Destination: snapSEC, Vorchdorf

snapSEC GmbH
Asamerstraße 1b
4655 Vorchdorf, Austria 47°59′ N · 13°55′ E

Personal, without obligation and confidential.