Slovakia transposed NIS2 by amending its existing Cybersecurity Act (No. 69/2018 Coll.) through Act No. 366/2024 Coll., in force since 1 January 2025, so organisations registered in 2025 now face a 12-month security measures deadline that has passed or is close, and a two-year audit deadline that falls in 2027. Slovakia kept its own vocabulary: instead of "essential" and "important" entities, the law regulates operators of basic services (prevádzkovateľ základnej služby) and, within them, operators of critical basic services, all registered with the National Security Authority (Národný bezpečnostný úrad, NBÚ). This guide covers registration, the security measures in Section 20, audits and self-assessment, incident reporting under Section 24 and Decree 226/2025, sanctions, management duties, and what the measures mean for service accounts, API keys and AI agents. It is for CISOs, compliance leads and auditors with Slovak operations. The Directive itself is in the NIS2 Directive Guide and the cross-country picture in the NIS2 Transposition Tracker.
Status, checked 14 November 2026: section references and figures come from the official Slov-lex texts: Act 366/2024 as promulgated, and the consolidated Act 69/2018 in the version effective from 30 April 2026, which also reflects later amendments by Acts 318/2025 (from 1 January 2026) and 67/2026 (from 30 April 2026). The entity estimate and size thresholds come from a single law firm commentary (Lansky, Ganzger, Goeth and Partners) and are attributed as such. The law has changed twice since transposition, so confirm against the current Slov-lex version before relying on it. This page is not legal advice.
Key takeaways
- Register within 60 days: Section 17(2) requires an entity to notify the NBÚ within 60 days of starting a covered activity; for entities in scope on 1 January 2025 two commentaries put the deadline at early March 2025.
- Two clocks start at registration: security measures within 12 months of entry in the register (Section 19(1)) and an audit within two years (Section 29(1)).
- Two tiers of operator: operators of basic services and operators of critical basic services, with fines up to EUR 7 million or 1.4% and EUR 10 million or 2% of worldwide annual turnover respectively (Section 31).
- Reporting runs 24 hours, 72 hours, one month: early warning, notification and final report under Section 24(3), with report content set by NBÚ Decree 226/2025 from 1 September 2025.
- Identity and access management is a named measure area: service accounts, keys and AI agents sit inside the Section 20 scope, not beside it.
Legal basis and how Slovakia framed NIS2
| Instrument | What it does | Status |
|---|---|---|
| Act No. 69/2018 Coll. on cybersecurity | The base law: register of operators, security measures, reporting, audits, supervision, fines | In force, consolidated on Slov-lex |
| Act No. 366/2024 Coll. | Transposes Directive (EU) 2022/2555 by amending Act 69/2018; adds supervision and sanctions (Sections 29a to 29n), certification (Section 5a) and transitional rules (Section 34b) | Effective 1 January 2025 (Article VII) |
| Act No. 318/2025 Coll. and Act No. 67/2026 Coll. | Later amendments to Act 69/2018 | Effective 1 January 2026 and 30 April 2026 |
| NBÚ Decree No. 226/2025 Coll. | Details of reports: initial and follow-up incident reports, threats, near misses and vulnerabilities, and criteria for serious disruption | Effective 1 September 2025 |
| NBÚ Decree No. 492/2022 Coll. | Knowledge standards for the cybersecurity manager (cited by SOMI Systems) | Listed as in force on Slov-lex |
The consolidated text defines the regulator in Section 5 as the Národný bezpečnostný úrad. The NBÚ keeps the register of operators of basic services, which is part of the public section of the Unified Cybersecurity Information System (Jednotný informačný systém kybernetickej bezpečnosti, Section 8(2)(b)). Section 8(6) says reports are made free of charge and without undue delay through that information system.
Scope: who is an operator of basic services
Section 17(1) lists the entities registered as operators. It includes central state administration bodies, critical entities, medium-sized and larger entities in sectors listed in the annexes, certain municipal and regional bodies, and some digital providers regardless of size, such as trust service providers, top-level domain managers, DNS providers and domain name registration providers. Section 18 defines the critical basic service, which places an operator in the higher tier.
- Size thresholds: the Lansky commentary summarises medium-sized as 50 to 249 employees or turnover above EUR 10 million, and large as 250 or more employees or turnover above EUR 50 million, in line with the EU SME definition.
- Estimated reach: the same commentary cites the explanatory memorandum's estimate of about 3,500 directly affected entities.
- Existing operators: under Section 34b(1), operators of basic services under the old law are treated as operators of critical basic services, and under Section 34b(3) former digital service providers are treated as operators of basic services. The NBÚ may decide by 31 December 2026 that an entity does not meet the new criteria (Section 34b(2) and (4)).
- Key service thresholds: Section 3(1)(y) defines a key service with thresholds such as more than 25,000 affected persons or a loss above EUR 250,000 for one user. Read the definition in full when assessing a service.
- Financial sector and digital providers: DORA applies to financial entities, and Implementing Regulation (EU) 2024/2690 sets measures for cloud, data centre, managed service and similar providers. See the DORA and NIS2 Overlap Mapping Guide and the NIS2 Implementing Regulation 2024/2690 Guide.
Timeline and deadlines
| Date or period | Milestone | Source |
|---|---|---|
| 1 January 2025 | Act 366/2024 takes effect | Act 366/2024, Article VII |
| 17 January 2025 | Date by which the NBÚ called on operators to meet the Section 21(3) duty | Section 34b(6) |
| 60 days from starting the activity | Notify the NBÚ for registration; for entities in scope on day one, early March 2025 | Section 17(2); Lansky; SOMI Systems |
| 12 months from entry in the register | Adopt and implement the general security measures, based on a risk analysis | Section 19(1) |
| 1 September 2025 | Decree 226/2025 on report content applies | Decree 226/2025 |
| 30 September 2025 | Last date to complete audits for 2024 under the transitional rule | Section 34b(9) |
| 31 December 2026 | End of transition: operators may rely on old security measures and audits until this date; NBÚ reclassification decisions due | Section 34b(2), (4), (5), (7) |
| Two years from entry in the register | Audit of the security measures (or self-assessment for non-critical operators) | Section 29(1) |
| Five years from entry in the register | Full audit for non-critical operators that used self-assessment | Section 29(8) |
The practical point: your deadlines run from your own entry in the register, not from 1 January 2025. Find the registration date in your NBÚ correspondence and work forward from it.
Security measures under Section 20
Section 19(1) requires the measures within 12 months of registration ("do 12 mesiacov odo dňa zápisu do registra prevádzkovateľov základnej služby"), based on a risk analysis. Section 20(4)(a) requires a cybersecurity manager to be designated, and SOMI Systems notes the manager must have no conflict of interest and meet the knowledge standards in Decree 492/2022. SOMI Systems lists the measure areas in Section 20 as follows.
| Area group | Section 20 areas (as summarised by SOMI Systems) | Where to go deeper |
|---|---|---|
| Governance | Information security organisation and management; asset and risk management; effectiveness assessment and compliance; human resource security | ISO 27001 Certification Guide |
| Identity and technical controls | Identity and access management; cryptography; network and communication security; malware protection; physical and endpoint security | Non-Human Identity (NHI) Guide |
| Detect and respond | Vulnerability and threat management; monitoring, logging and incident reporting; incident management; continuity, backup, disaster recovery and crisis management | Cyber Incident Reporting Requirements Map |
| Supply and lifecycle | Secure acquisition, development and maintenance; supply chain security; use of certified ICT products and services; records protection and classification | NIS2 Supply Chain Security Guide |
Section 20(4)(g) and (h) also require roles and training to be assigned and named people to be responsible for approving the measures, oversight, audit and resourcing. Write those names into the security documentation.
Audits and self-assessment
- First verification: within two years of entry in the register ("do dvoch rokov odo dňa zaradenia", Section 29(1)).
- Self-assessment route: operators that are not critical operators may use a self-assessment through the Unified Cybersecurity Information System instead of an audit for the initial check; the cybersecurity manager performs it (Section 29(1) and (8)).
- Five-year audit: those operators still need a full audit within five years of registration (Section 29(8)).
- Filing the report: the final audit report goes to the NBÚ within 30 days after the audit ends (Section 29(5)).
- Transitional self-assessment: operators of former category I and II networks may use self-assessment in place of an audit (Section 34b(8)); SOMI Systems reads this as applying in 2025 and 2026 and mainly affecting public administration.
Incident reporting
| Stage | Deadline (Section 24(3)) | Content (Decree 226/2025) |
|---|---|---|
| Early warning | No later than 24 hours after detection | Reporter and contacts, time of detection, description, consequences or expected scope, whether unlawful conduct may be the cause, possible cross-border effect |
| Notification | No later than 72 hours after detection (24 hours for trust service providers) | Updated details, preliminary assessment of severity and impact, timeline, response status and measures taken |
| Final report | No later than one month after the notification | Set by the Act; read Section 24 in full |
| Threats, near misses, vulnerabilities | Section 24(5) and (6) | Type and description, possible impact, time of detection; for vulnerabilities the affected ICT product, service or OT and, if known, its maker |
Annex 1 to Decree 226/2025 sets time and user-impact thresholds for what counts as a serious disruption to an operator. Build them into your incident classification so the 24-hour clock is not lost to debate. See the Cyber Incident Reporting Requirements Map for how this compares with other regimes.
Sanctions and management duties
| Provision | Measure |
|---|---|
| Section 31(2) | Operators of basic services: from EUR 300 up to EUR 7,000,000 or 1.4% of worldwide annual turnover, whichever is higher |
| Section 31(3) | Operators of critical basic services: from EUR 500 up to EUR 10,000,000 or 2% of worldwide annual turnover, whichever is higher |
| Section 31(1) and (4) to (11) | Other listed breaches: generally EUR 300 to EUR 500,000 |
| Section 31(13) | Repeat breach within one year of a final fine: up to double the maximum |
| Section 29j(2) | Periodic penalty of 0.5% of the maximum fine per day of delay |
| Section 29j(4) | For non-complying critical operators, members of the statutory body or senior managers can be barred from their roles until compliance |
| Section 31(17) | Fine must be imposed within two years of detecting the breach and at most four years after it |
Section 19(6)(h) requires a mechanism to inform the statutory body and responsible senior managers about threats, incidents and risk analysis results, and Section 19(6)(i) requires the NBÚ to be told of appointments or changes to the statutory body. See the NIS2 Management Liability Executive Briefing.
How to implement, in order
- Confirm status: check Section 17(1) and the annexes for each service, decide whether any is a critical basic service, and find your register entry date.
- Name the cybersecurity manager: check Decree 492/2022 knowledge standards and conflicts of interest; name a deputy.
- Risk analysis first: Section 19(1) bases the measures on it; scope it to the services in the register, including the identities and suppliers inside them.
- Map Section 20 areas: map each area to existing ISO/IEC 27001 controls and record gaps with owners and dates inside the 12-month window.
- Wire reporting: build the Decree 226/2025 fields and Annex 1 thresholds into the incident process and test access to the information system.
- Brief the statutory body: set up the Section 19(6)(h) reporting line and record approvals.
- Plan the audit: book a certified auditor or prepare the self-assessment well before the two-year date; note that transitional reliance on old measures ends on 31 December 2026.
What it means for AI agents and non-human identities
- Scope identities with the service: for each registered service, list service accounts, API keys, OAuth applications, certificates and AI agents, each with an owner. Identity and access management is one of the Section 20 areas.
- Logging for the 24-hour report: the early warning needs a description and expected scope; without machine identity logs you cannot say which credential was used.
- Vulnerability reports: Decree 226/2025 asks for the affected product or service; keep an inventory linking credentials to the systems they reach.
- Agents: give each AI agent its own scoped identity and a retained action log, so its activity can be reported like any other.
- Suppliers: record credentials and OAuth grants held by suppliers under the supply chain area.
- Review cadence: NHI Mgmt Group recommends quarterly review of privileged machine identities and annual review of the rest. This is our recommendation, not a Slovak rule.
Common failure patterns
- Wrong start date: counting the 12-month and two-year periods from 1 January 2025 instead of the register entry.
- Assuming the old tier: former operators are treated as critical operators unless the NBÚ decides otherwise, which raises the fine ceiling and removes the self-assessment route.
- Relying on old measures past 2026: the transitional allowance in Section 34b ends on 31 December 2026.
- No named owners: Section 20(4) expects named people for approval, oversight, audit and resourcing.
- Human-only access reviews: service accounts, keys and agents left out of the identity and access management measure.
- Statutory body changes not notified: Section 19(6)(i) is easy to miss after board changes.
Practitioner checklist
- Confirm each service against Section 17(1), the annexes and Section 18.
- Record the register entry date and the 12-month and two-year deadlines.
- Designate the cybersecurity manager and a deputy against Decree 492/2022.
- Complete and document the risk analysis behind the Section 20 measures.
- Inventory machine identities and AI agents inside each registered service.
- Build Decree 226/2025 fields and Annex 1 thresholds into incident triage.
- Rehearse 24-hour, 72-hour and one-month reporting.
- Schedule the audit or self-assessment and the 30-day report filing.
- Track Slov-lex for further amendments to Act 69/2018.
Standards and references
- Slov-lex: Act No. 69/2018 Coll. on cybersecurity, consolidated version from 30 April 2026
- Slov-lex: Act No. 366/2024 Coll., as promulgated
- Slov-lex: NBÚ Decree No. 226/2025 Coll. on details of reports
- EUR-Lex: Directive (EU) 2022/2555 (NIS 2)
- Lansky, Ganzger, Goeth and Partners: Amendment to the Cyber Security Act (NIS 2 transposition)
- SOMI Systems: Obligations under the amended Cybersecurity Act
Related NHI Mgmt Group resources: NIS2 Directive Guide · NIS2 Transposition Tracker · Czechia NIS2 Implementation · NIS2 Readiness Checklist · Non-Human Identity (NHI) Guide. This guide summarises the Slovak Cybersecurity Act as it stood on 14 November 2026 and is not legal advice.