Back to Guides

    NIS2 in Greece

    A guide to NIS2 implementation and compliance in Greece.

    Greece is strengthening its national cybersecurity regime to align with the enhanced obligations introduced under the NIS2 Directive. The updated framework expands sector coverage, formalizes management accountability, and reinforces reporting and enforcement mechanisms. This guide provides a structured overview of NIS2 compliance Greece requirements for SMEs operating in regulated sectors.

    1. Quick SME Applicability Snapshot in Greece

    Does NIS2 apply to SMEs in Greece?

    Yes — depending on size and sector.

    • 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 Greece and, in certain cases, foreign digital providers serving the Greek market.

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

    2. Overview of NIS2 Implementation in Greece

    Greece is implementing the Directive through amendments to the Law on Cybersecurity and the Security of Network and Information Systems, which forms the foundation of the national cybersecurity framework.

    The revised legislation aligns Greece's regime with Directive (EU) 2022/2555 and strengthens obligations related to governance, risk management, incident reporting, and supervisory authority powers.

    The framework integrates Directive standards into Greece's existing cybersecurity oversight model.

    3. Scope of Application in Greece

    Greece's scope mirrors Directive minimum sector categories without confirmed structural expansion.

    4. Size Thresholds and SME Applicability in Greece

    The Directive baseline thresholds apply:

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

    Entities meeting both criteria in covered sectors fall automatically within scope.

    Small and micro enterprises may be designated where they are considered critical to public security, economic stability, or societal functioning.

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

    5. Entity Classification Framework in Greece

    Entities are categorized as:

    • Essential Entities — Subject to proactive supervision, including audits 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.

    Greece follows the Directive's two-tier supervisory model.

    6. Cybersecurity Risk Management Requirements in Greece

    Greece'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 Greece 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 national cybersecurity guidance is encouraged.

    7. Management Liability and Governance in Greece

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

    Under Greece'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 Greece expectations elevate cybersecurity governance to executive level responsibility.

    8. Incident Reporting Obligations in Greece

    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 hoursNational Cybersecurity Authority (NCSA)
    Incident Notification72 hoursNational Cybersecurity Authority (NCSA)
    Final Report1 monthNational Cybersecurity Authority (NCSA)

    9. Supervisory Authorities and Enforcement Model in Greece

    Primary authority: National Cybersecurity Authority (NCSA).

    Greece operates a centralized supervisory model coordinated by the NCSA, with sector-specific regulators involved where necessary.

    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 Greece

    Greece 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 Greece enforcement may also include:

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

    Criminal liability applies only where explicitly provided under Greek legislation.

    11. NIS2 Supply Chain and Vendor Security in Greece

    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

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

    12. Registration and Self-Identification Duties in Greece

    Entities within scope must:

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

    Procedural deadlines follow Greece's implementing framework. As of the current transposition status, Greece 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 Greece

    The General Data Protection Regulation continues to apply concurrently.

    Overlap considerations include:

    • 72-hour personal data breach notification
    • Supervisory authority coordination
    • Parallel cybersecurity and data protection investigations
    • Sector-specific Greek cybersecurity legislation

    A single cyber incident may trigger reporting obligations under both regimes.

    14. Cross-Border Applicability

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

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

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

    15. Implementation Timeline in Greece

    • 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

    Greece's transposition timeline aligns with EU implementation requirements.

    16. Key Takeaways for SMEs in Greece

    • 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 Greece SME Guide

    Does NIS2 apply to small companies in Greece?

    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 Greece?

    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 Greece?

    Greece is updating its national cybersecurity legislation to align with the Directive. Entry into force follows national legislative publication.

    Who enforces NIS2 in Greece?

    The National Cybersecurity Authority (NCSA) serves as the primary supervisory authority, coordinating with sector regulators where applicable.

    Can directors be personally liable under NIS2 in Greece?

    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 Greece?

    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 Greece?

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