Back to Guides

    NIS2 in Cyprus

    A guide to NIS2 implementation and compliance in Cyprus.

    Cyprus is aligning its national cybersecurity regime with the strengthened obligations introduced under the NIS2 Directive. The updated framework expands sector coverage, strengthens governance accountability, and formalizes supervisory and sanction mechanisms. This guide provides a structured overview of NIS2 compliance Cyprus requirements for SMEs operating in regulated sectors.

    1. Quick SME Applicability Snapshot in Cyprus

    Does NIS2 apply to SMEs in Cyprus?

    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 Cyprus and, in certain circumstances, foreign digital providers serving the Cypriot market.

    SMEs should evaluate whether they fall within Cyprus' national cybersecurity regime based on sector classification and statutory thresholds.

    2. Overview of NIS2 Implementation in Cyprus

    Cyprus is implementing the Directive through amendments to the Security of Network and Information Systems Law, which forms the national legal basis for cybersecurity oversight.

    The updated law aligns with Directive (EU) 2022/2555 and modernizes obligations relating to governance, incident reporting, supervision, and sanctions.

    The legislative framework strengthens supervisory authority powers while maintaining structural consistency with the Directive.

    3. Scope of Application in Cyprus

    Cyprus' sectoral scope reflects Directive minimum categories without confirmed national expansion.

    4. Size Thresholds and SME Applicability in Cyprus

    The Directive baseline thresholds apply:

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

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

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

    Cypriot authorities retain formal designation powers where justified by systemic risk.

    5. Entity Classification Framework in Cyprus

    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.

    Cyprus' classification structure mirrors the Directive's two-tier model.

    6. Cybersecurity Risk Management Requirements in Cyprus

    Cyprus aligns with the Directive baseline for cybersecurity risk management. In-scope entities must implement proportionate technical and organizational measures addressing:

    • Risk analysis and system security
    • Incident prevention and response
    • Business continuity and crisis planning
    • NIS2 supply chain Cyprus risk controls
    • Secure system acquisition and development
    • Access control and identity management
    • Encryption and cryptographic safeguards
    • Vulnerability management procedures
    • Staff cybersecurity awareness and training

    Measures must reflect state-of-the-art standards and the organization's risk profile. Alignment with ISO/IEC 27001 and recognized Cypriot cybersecurity guidance is encouraged.

    Supply chain oversight includes contractual safeguards and vendor monitoring to mitigate cascading cyber risk.

    7. Management Liability and Governance in Cyprus

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

    Under Cyprus' national framework:

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

    NIS2 management liability Cyprus standards elevate cybersecurity responsibility to executive level.

    8. Incident Reporting Obligations in Cyprus

    Definition of a Significant Incident

    A significant incident includes events causing:

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

    Reporting Timeline

    Reporting StageDeadlineAuthority
    Early Warning24 hoursDigital Security Authority (DSA)
    Incident Notification72 hoursDigital Security Authority (DSA)
    Final Report1 monthDigital Security Authority (DSA)

    9. Supervisory Authorities and Enforcement Model in Cyprus

    Primary authority: Digital Security Authority (DSA).

    Cyprus operates a centralized supervisory model supported by sector regulators when required.

    Supervisory powers include:

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

    The enforcement structure aligns with Directive-level cooperation mechanisms.

    10. NIS2 Fines and Sanctions in Cyprus

    Cyprus 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 Cyprus 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 Cypriot legislation.

    11. NIS2 Supply Chain and Vendor Security in Cyprus

    Entities must manage third-party cybersecurity exposure through:

    • Vendor due diligence
    • Contractual security flow-down requirements
    • Ongoing ICT supplier monitoring
    • Concentration risk analysis
    • Incident propagation mitigation

    Cyprus' approach aligns with Directive baseline expectations regarding third-party risk management.

    12. Registration and Self-Identification Duties in Cyprus

    Entities within scope must:

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

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

    Self-identification is required where entities meet statutory thresholds.

    13. Interaction With GDPR and Other Laws in Cyprus

    The General Data Protection Regulation continues to apply concurrently.

    Overlap areas include:

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

    14. Cross-Border Applicability

    Entities with their main establishment in Cyprus fall under Cypriot supervision for cross-border services.

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

    Representation requirements follow Directive standards for non-EU providers serving Cypriot markets.

    15. Implementation Timeline in Cyprus

    • 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

    Cyprus' transposition process aligns with the EU implementation schedule.

    16. Key Takeaways for SMEs in Cyprus

    • Medium-sized entities in covered sectors are automatically in scope.
    • Small entities may be designated if critical to economic or public 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 a core obligation.
    • Early compliance planning reduces enforcement exposure.

    FAQ: NIS2 Cyprus SME Guide

    Does NIS2 apply to small companies in Cyprus?

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

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

    Cyprus is updating its Security of Network and Information Systems Law to align with the Directive. Entry into force follows national legislative publication.

    Who enforces NIS2 in Cyprus?

    The Digital Security Authority (DSA) serves as the primary supervisory authority, coordinating with sector regulators where relevant.

    Can directors be personally liable under NIS2 in Cyprus?

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

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

    What qualifies as a significant incident under NIS2 in Cyprus?

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