Back to Guides

    NIS2 in Hungary

    A guide to NIS2 implementation and compliance in Hungary.

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

    1. Quick SME Applicability Snapshot in Hungary

    Does NIS2 apply to SMEs in Hungary?

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

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

    2. Overview of NIS2 Implementation in Hungary

    Hungary is implementing the Directive through amendments to the Act on Cybersecurity of State and Municipal Bodies and related national cybersecurity legislation.

    The updated framework aligns Hungary's regime with Directive (EU) 2022/2555 and strengthens obligations concerning governance, incident reporting, risk management, and administrative sanctions.

    The legislation integrates Directive standards into Hungary's established oversight model for critical infrastructure and digital service providers.

    3. Scope of Application in Hungary

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

    4. Size Thresholds and SME Applicability in Hungary

    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 considered critical to national security, economic stability, or essential service continuity.

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

    5. Entity Classification Framework in Hungary

    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 supervision.

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

    6. Cybersecurity Risk Management Requirements in Hungary

    Hungary'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 Hungary 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 Hungarian cybersecurity guidance is encouraged.

    7. Management Liability and Governance in Hungary

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

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

    8. Incident Reporting Obligations in Hungary

    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 Cyber Security Center (NCSC Hungary)
    Incident Notification72 hoursNational Cyber Security Center (NCSC Hungary)
    Final Report1 monthNational Cyber Security Center (NCSC Hungary)

    Hungary follows the Directive structure for NIS2 reporting deadlines Hungary. Sector regulators may coordinate with the NCSC where applicable.

    9. Supervisory Authorities and Enforcement Model in Hungary

    Primary authority: National Cyber Security Center (NCSC Hungary).

    Hungary operates a centralized supervisory model supported by sector-specific regulators 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 Hungary

    Hungary 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 Hungary 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 Hungarian legislation.

    11. NIS2 Supply Chain and Vendor Security in Hungary

    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

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

    12. Registration and Self-Identification Duties in Hungary

    Entities within scope must:

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

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

    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 Hungarian cybersecurity legislation

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

    14. Cross-Border Applicability

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

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

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

    15. Implementation Timeline in Hungary

    • 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

    Hungary's transposition timeline aligns with EU implementation requirements.

    16. Key Takeaways for SMEs in Hungary

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

    Does NIS2 apply to small companies in Hungary?

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

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

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

    Who enforces NIS2 in Hungary?

    The National Cyber Security Center (NCSC Hungary) serves as the primary supervisory authority, coordinating with sector regulators where applicable.

    Can directors be personally liable under NIS2 in Hungary?

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

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

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