Back to Guides

    NIS2 in Slovenia

    A guide to NIS2 implementation and compliance in Slovenia.

    Slovenia is updating its national cybersecurity regime to align with the strengthened obligations introduced under the NIS2 Directive. The revised framework expands sector coverage, strengthens executive accountability, and enhances supervisory and enforcement mechanisms. This guide provides a structured overview of NIS2 compliance Slovenia requirements for SMEs operating in covered sectors.

    1. Quick SME Applicability Snapshot in Slovenia

    Does NIS2 apply to SMEs in Slovenia?

    Yes — depending on sector and size.

    • Automatic applicability to medium-sized entities (≥50 employees and ≥€10 million turnover or balance sheet total) operating in covered sectors.
    • Small or micro entities are included only if formally designated or operating in high-criticality sectors.
    • Applies to entities established in Slovenia and, in certain cases, foreign digital providers serving the Slovenian market.

    SMEs should assess qualification under Slovenia's national cybersecurity framework based on sector classification and statutory thresholds.

    2. Overview of NIS2 Implementation in Slovenia

    Slovenia is implementing the Directive through amendments to the Information Security Act, which governs national cybersecurity obligations.

    The revised legislative framework aligns Slovenia's regime with Directive (EU) 2022/2555 and strengthens requirements concerning governance, cybersecurity risk management, incident reporting, supervisory oversight, and administrative sanctions.

    The implementation builds upon Slovenia's established cybersecurity oversight structure while expanding scope in accordance with EU standards.

    3. Scope of Application in Slovenia

    Slovenia's scope reflects Directive minimum sector categories without confirmed structural expansion.

    4. Size Thresholds and SME Applicability in Slovenia

    The Directive baseline thresholds apply:

    • ≥50 employees, and
    • ≥€10 million annual turnover or balance sheet total.

    Entities meeting both criteria within covered sectors are automatically within scope.

    Small and micro enterprises may be designated if considered critical to national security, economic stability, or essential service continuity.

    Slovenian authorities retain formal designation powers where systemic risk justifies inclusion.

    5. Entity Classification Framework in Slovenia

    Entities are categorized as:

    • Essential Entities — Subject to proactive supervision, including inspections and structured compliance monitoring.
    • Important Entities — Primarily subject to reactive supervision triggered by significant incidents or compliance concerns.

    Classification is determined by sector and size. Authorities may reclassify entities where operational impact or risk exposure warrants enhanced oversight.

    Slovenia follows the Directive's two-tier supervisory structure.

    6. Cybersecurity Risk Management Requirements in Slovenia

    Slovenia's national regime aligns with the Directive baseline for cybersecurity risk management. In-scope entities must implement proportionate technical and organizational measures addressing:

    • Risk analysis and system protection
    • Incident detection and response
    • Business continuity and crisis management
    • NIS2 supply chain Slovenia risk controls
    • Secure acquisition and development of ICT systems
    • Access control and identity management
    • Encryption and cryptographic safeguards
    • Vulnerability management procedures
    • Staff cybersecurity training

    Measures must reflect state-of-the-art standards and organizational risk exposure. Alignment with ISO/IEC 27001 and Slovenian cybersecurity guidance is encouraged.

    7. Management Liability and Governance in Slovenia

    Management bodies must formally approve cybersecurity risk management measures and oversee implementation.

    Under Slovenia's framework:

    • Boards are accountable for compliance oversight.
    • Senior management must ensure sufficient cybersecurity competence.
    • Administrative sanctions may address governance failures.
    • Temporary suspension of managerial functions may be available under Directive-aligned enforcement mechanisms.

    NIS2 management liability Slovenia expectations elevate cybersecurity governance to executive level responsibility.

    8. Incident Reporting Obligations in Slovenia

    Definition of a Significant Incident

    A significant incident includes events causing:

    • Severe operational disruption
    • Significant financial loss
    • Substantial societal impact
    • Cross-border effects

    Reporting Timeline

    Reporting StageDeadlineAuthority
    Early Warning24 hoursInformation Security Administration (URSIV)
    Incident Notification72 hoursInformation Security Administration (URSIV)
    Final Report1 monthInformation Security Administration (URSIV)

    Slovenia follows the Directive structure for NIS2 reporting deadlines Slovenia.

    9. Supervisory Authorities and Enforcement Model in Slovenia

    Primary authority: Information Security Administration (URSIV).

    Slovenia operates a centralized supervisory model coordinated by URSIV, with sector-specific regulators involved where required.

    Supervisory powers include:

    • Requests for documentation and information
    • Security audits
    • On-site inspections
    • Binding compliance instructions
    • Participation in EU cybersecurity coordination mechanisms

    The enforcement structure aligns with Directive-level cooperation requirements.

    10. NIS2 Fines and Sanctions in Slovenia

    Slovenia applies Directive-aligned administrative penalties.

    Essential Entities

    Up to €10 million or 2% of total global annual turnover (whichever is higher)

    Important Entities

    Up to €7 million or 1.4% of total global annual turnover (whichever is higher)

    NIS2 fines Slovenia enforcement may also include:

    • Binding remediation orders
    • Public identification of non-compliant entities
    • Suspension of authorizations or certifications
    • Managerial suspension powers

    11. NIS2 Supply Chain and Vendor Security in Slovenia

    Entities must manage third-party cybersecurity exposure through:

    • Vendor risk assessments
    • Contractual security flow-down provisions
    • Continuous ICT supplier monitoring
    • Concentration risk analysis
    • Incident propagation mitigation

    Slovenia's approach aligns with Directive baseline expectations regarding supplier risk management.

    12. Registration and Self-Identification Duties in Slovenia

    Entities within scope must:

    • Register with competent authorities
    • Provide corporate identification details
    • Disclose sector classification
    • Maintain updated reporting contacts

    Procedural deadlines follow Slovenia's implementing framework. As of the current transposition status, Slovenia follows the NIS2 Directive baseline framework. National implementing details may refine specific obligations.

    Self-identification is mandatory where entities meet statutory thresholds.

    13. Interaction With GDPR and Other Laws in Slovenia

    The General Data Protection Regulation continues to apply concurrently.

    Overlap considerations include:

    • 72-hour personal data breach notification
    • Supervisory authority coordination

    14. Cross-Border Applicability

    Entities with their main establishment in Slovenia are supervised by Slovenian authorities for cross-border services.

    Foreign digital providers offering services in Slovenia may be subject to national obligations depending on establishment structure.

    Representation requirements follow Directive standards for non-EU providers serving the Slovenian market.

    15. Implementation Timeline in Slovenia

    • Directive adoption: 2022
    • National legislative amendments: 2024–2025
    • Entry into force: Upon national publication
    • Commission notification: In accordance with EU procedures
    • Compliance milestone: Directive-aligned deadlines

    Slovenia's transposition timeline aligns with EU implementation requirements.

    16. Key Takeaways for SMEs in Slovenia

    • Medium-sized entities in covered sectors are automatically within scope.
    • Small entities may be designated if critical to national or economic stability.
    • Board-level governance oversight is mandatory.
    • Incident reporting follows 24h / 72h / 1 month deadlines.
    • Financial penalties can reach €10 million or 2% of global turnover.
    • Vendor risk management is required.
    • Early compliance planning reduces enforcement exposure.

    FAQ: NIS2 Slovenia SME Guide

    Does NIS2 apply to small companies in Slovenia?

    Small companies are generally excluded unless designated or operating in highly critical sectors. Medium-sized entities meeting size thresholds are automatically covered.

    What are the NIS2 fines in Slovenia?

    Essential Entities face penalties up to €10 million or 2% of global annual turnover. Important Entities face up to €7 million or 1.4% of global annual turnover.

    When does NIS2 take effect in Slovenia?

    Slovenia is amending its Information Security Act to align with the Directive. Entry into force follows national legislative publication.

    Who enforces NIS2 in Slovenia?

    The Information Security Administration (URSIV) serves as the primary supervisory authority, coordinating with sector regulators where applicable.

    Can directors be personally liable under NIS2 in Slovenia?

    Management bodies must approve and oversee cybersecurity measures. Administrative enforcement tools may include managerial suspension powers in serious cases.

    How does NIS2 differ from GDPR in Slovenia?

    NIS2 governs cybersecurity resilience and operational risk management, while GDPR regulates personal data protection. Both frameworks may apply following a cyber incident.

    What qualifies as a significant incident under NIS2 in Slovenia?

    An incident causing severe disruption, significant financial loss, societal impact, or cross-border consequences typically meets the reporting threshold.