NIS2: The Transition Period Ends on December 31. What Slovak Operators Need to Check Before 2027
The amendment to the Cybersecurity Act has been in force since January 1, 2025, but some entities listed in the register under the previous legislation could rely on the transitional provisions until December 31, 2026. For operators in energy, transport, healthcare, water management and other strategic services, the final weeks of the year are therefore an opportunity to check not only formal compliance, but also the actual level of protection for their operations.
The end of the transition period is not the beginning of NIS2
Directive (EU) 2022/2555 set a transposition deadline of October 17, 2024. Slovakia met that deadline through Act No. 366/2024 Coll., which amended Act No. 69/2018 Coll. on Cybersecurity with effect from January 1, 2025. The amendment changed the scope of regulated entities, how they are identified and registered, the requirements for risk management, security measures and oversight mechanisms. It strengthened management accountability, supply-chain security and the ability to restore service delivery after an incident.
The transitional provisions in Section 34b allowed some entities already on the register to move gradually to the new regime. Until December 31, 2026, operators registered under the legislation in force through the end of 2024 may adopt and implement security measures, and conduct audits, under the previous rules. This option ends on January 1, 2027. The transition period was not, however, a general exemption: the new regime’s baseline requirements applied on an ongoing basis within the deadlines set by law, not only from January 1, 2027. Entities that began carrying out a regulated activity after January 1, 2025 have their own timeline: notification within 60 days of starting the activity, security measures within 12 months, and a first audit within two years of registration.
Section 34b(8) is less widely known. An operator of an essential service may meet an audit obligation falling due in 2025 or 2026 for Category I and II networks and information systems by means of a self-assessment through the single information system. This does not apply to an audit falling due in 2027.
Who is an operator of an essential service, and who is an operator of a critical essential service?
The Act distinguishes between an operator of an essential service (PZS) and an operator of a critical essential service (PKZS). Neither category should be confused with the status of a critical entity under Act No. 367/2024 Coll. on Critical Infrastructure, which transposes the CER Directive and identifies critical entities through a separate procedure. A business may therefore be both a PKZS and a critical entity. The obligations under both laws then apply cumulatively, and the documentation should be aligned rather than duplicated. The central authorities identified critical entities for the first time by July 17, 2026 at the latest, so many organizations are dealing with both regimes at the same time.
A PZS is an entity registered under Section 17 that operates in a regulated sector and meets the identification criteria. A PKZS is an entity that provides at least one critical essential service under Section 18. This is a narrower category subject to a stricter regime.
Special rules apply to entities registered under the legislation in force through December 31, 2024. Under Section 34b(1), from January 1, 2025 they are deemed to be PKZS directly by operation of law, without a decision. However, by December 31, 2026, the National Security Authority (NBÚ) may decide, including on its own initiative, that a particular entity does not meet the conditions. The difference is not merely formal: for the same violation, a PZS may face a fine of up to €7 million or 1.4% of turnover, while a PKZS may face a fine of up to €10 million or 2% of turnover (Section 31). Checking the register entry and any decisions issued by the Authority should therefore be among the first steps.
Security measures: the actual state of affairs matters, not the documentation
Under Section 19(1), a PZS must adopt, maintain and implement security measures at least to the extent required by Section 20, based on a risk analysis, within 12 months of registration. The details have been governed since September 1, 2025 by NBÚ Decree No. 227/2025 Coll., which replaced Decree No. 362/2018 Coll.
The measures must cover the full lifecycle of information and operational technologies: risk and asset management, vulnerability management, incident detection and response, business continuity, backup and recovery, security in procurement and maintenance, access management, physical security, supply-chain security and event monitoring. The latter areas are particularly important for operations that depend on technology not owned by the organization: external service access, a cloud service or an industrial control system may have an impact comparable to an attack on the organization’s own network. Documentation must therefore reflect the actual state of affairs. Approved policies that are not followed do not serve their purpose.
Audits: new rules apply from September 2026
Section 29 requires an audit within two years of registration, then at intervals set by the implementing regulation and after every significant change. An amendment to Decree No. 493/2022 Coll., adopted through NBÚ Decree No. 212/2026 Coll., has been in force since September 1, 2026.
An audit is considered complete when the final report is delivered to the operator, and its performance must not exceed 12 consecutive months. The next audit must be carried out no later than the end of the third calendar year following the year in which the previous audit was completed. If the entity is a PZS that is not a PKZS and uses self-assessment, the interval is extended to the fifth calendar year; in the meantime, self-assessment must be conducted every two years, and the cybersecurity manager must submit its report. In the event of a significant change affecting the measures implemented, an audit must be carried out within six months at the latest. Audit scope is calculated in person-days according to the number of people involved in implementing the security measures; no more than 30% of the time may be allocated to preparation and reporting. The certified auditor is responsible for the accuracy of the final report, while the operator is responsible for implementing corrective measures. The report, including the measures and deadlines, must be submitted to the NBÚ within 30 days of the audit’s completion. The Authority may also conduct an audit on its own initiative at any time, but the operator bears the cost of a routine audit.
The transition rules are a matter of planning: an audit begun but not completed by August 31, 2026 must be completed under the previous version of Decree No. 493/2022 Coll., and an audit begun by December 31, 2026 may be carried out under that version. For audits spanning the turn of the year, it is therefore advisable to document the start date.
Incident reporting: deadlines run from discovery
Under Section 24, a significant incident must be reported through the single information system in three stages: an early warning within 24 hours of discovery, a notification within 72 hours, and a final report no later than one month after the notification. If an incident with cross-border impact is still ongoing when the report is filed, an update must follow once normal operations have been restored. The same reporting channel is used for a significant cyber threat, a near miss and an exploitable vulnerability. Responsibilities, contact persons and escalation procedures must be defined in advance; there is no time to do so during an incident.
What to check by December 31, 2026
For management, this is not about checking whether documents exist. It is about verifying that the organization understands its status and can demonstrate that its measures are effective. We recommend reviewing seven areas:
- Verify the NBÚ register entry, the scope of the services listed and any decision under Section 34b.
- Identify which transitional options are ending and whether the measures comply with Decree No. 227/2025 Coll.
- Check whether the risk analysis covers networks, information systems, operational technology, supporting assets and dependencies on third parties.
- Verify that the documentation is up to date and reflects actual operations, and that it is fit for use in an audit.
- Set the date of the next audit or self-assessment based on the entity’s status, registration date and the rules in force from September 1, 2026.
- Review suppliers’ access rights, contractual requirements, incident reporting and dependencies on external ICT and technology services.
- Test incident reporting, management decision-making authority, backup arrangements and the ability to restore the service. Assign an owner and deadline to each area.
These steps are not a one-off exercise. The Act requires ongoing risk management and the updating of measures. The statutory body and responsible senior employees should regularly receive the results of the analysis and the status of risk treatment.
AKI SR’s position: cybersecurity is part of operational security
The Critical Infrastructure Association of the Slovak Republic (AKI SR) considers the transition to the new regime part of protecting essential services. The success of implementation cannot be measured by the number of documents prepared, audits conducted or requirements formally met. What matters is the ability to identify risks, prevent incidents, detect disruptions in time, and maintain or restore service delivery. This requires cybersecurity to be connected with physical protection, operational technology security, supplier management and crisis management. The Association therefore recommends using the remaining weeks to verify measures in practice, rather than to finish writing documentation.
This is where AKI SR adds value. The Association brings together operators that face the same issues across different sectors and enables them to compare approaches where the law sets a framework but does not prescribe a specific solution. Where interpretations allow for more than one defensible reading - such as the scope of self-assessment under Section 34b(8), the boundary between an audit and self-assessment, or the alignment of obligations under Act No. 69/2018 Coll. and Act No. 367/2024 Coll. - the Association offers a shared perspective among operators and an opportunity to test it before it is reflected in documentation and an audit.
In practical terms, this means creating an environment in which operational experience can reach those who decide how rules are interpreted and shaped. The Association therefore provides space for exchange among operators, as well as between operators and state institutions and the technology sector. Concrete operational findings can thus inform legislation and methodological guidance, rather than remaining at the level of general recommendations. Membership does not replace an entity’s responsibility or the remit of public authorities. It does, however, create an environment in which legal requirements can be implemented through measures tested in practice.
The transition period will end, but cyber risks will not stay on the calendar. What matters is whether the new rules have been translated into the readiness of people, processes and technologies before a real incident puts them to the test.









