General Counsel

Apr 29, 2025

5 min. read

NIS2 directive regulations and implementation in Liechtenstein

Share:

NIS2 directive regulations and implementation in Liechtenstein

When I first heard that Liechtenstein would be revising its Cyber-Security Act to meet the requirements of the updated European Union (EU) cybersecurity legislation, my initial thought was: “Here comes another round of compliance headaches.” But diving deeper, I found that the principality’s approach to the Network and Information Security Directive 2 (NIS2) and its Critical Entities Resilience (CER) twin is not only methodical but also remarkably ambitious for such a small state. Without further ado, let me guide you through what the NIS2 Liechtenstein implementation means for businesses and public bodies.

Key take-aways from Liechtenstein’s NIS2 rollout

By early 2025, Liechtenstein completed a comprehensive overhaul of its cybersecurity framework. The Cyber-Security Act (CSG) was amended to directly transpose Directive (EU) 2022/2555, commonly referred to as NIS2, alongside its CER “twin.” These changes are not merely cosmetic; they redefine obligations, reporting duties, and supervisory practices for hundreds of entities.

Before we dive into the specifics, it’s important to have a clear view of where things currently stand:

Summary of NIS2 implementation status in Liechtenstein

ThemeStatus
Transposition LawTotal revision of the Cyber-Security Act (CSG); entered into force 1 February 2025
TimelineBill proposed May 2024; adopted after two readings in autumn 2024; effective 1 February 2025
Scope ExpansionFrom ~350 to ~1,800-2,200 entities, including district heating, wastewater, food, research sectors
Entity ClassesEssential (≥250 FTE/€50m), Important (≥50 FTE/€10m); some sectors regardless of size
Maximum FinesUp to CHF 10 million or 2% of global turnover for essentials
Incident Reporting24h initial, 72h update, 30-day final report
Supervision ModelCentralized under Stabsstelle Cyber-Sicherheit with sectoral audits by regulators
Public SectorExempt from fines but bound by corrective orders

This structured implementation allows a smoother transition for both legacy and newly regulated entities.

Timeline and deadlines: the road to full compliance

Implementation of the NIS2 directive in Liechtenstein follows a clear and legally binding timeline. Each phase is carefully scheduled to ensure organisations have enough time to adapt, yet the pressure to comply is unmistakably firm.

Key milestones in Liechtenstein’s NIS2 timeline

DateMilestoneStatus
17 May 2024Bill submitted to LandtagCompleted
18 Sept 2024First reading (general debate)Completed
21 Nov 2024Second reading (detailed adoption)Completed
31 Jan 2025Publication in LandesgesetzblattCompleted
1 Feb 2025CSG and ordinance effective; registration portal launchedCompleted
31 Mar 2025Deadline for re-registration of NIS-1 operatorsPending at article time
1 Feb 2026Organisational measures must be implementedUpcoming
1 Feb 2027Technical controls due; first audits commenceUpcoming

With clear expectations set, organisations have no excuse for delay.

How Liechtenstein is implementing the NIS2 directive

The revised CSG brings Liechtenstein fully into alignment with EU cybersecurity goals. This law is not just a formality; it provides detailed guidance on risk management, incident response, and supervision protocols.

Core contents of the revised Cyber-Security Act

ChapterContent Highlights
I-IIScope and definitions covering all 18 NIS2 sectors plus national additions
III (Art. 16)Risk management obligations mapped to ISO 27001 standards
IV (Art. 19)Incident notification protocols (24h/72h/30d)
VSupervision powers, audits, compulsory penetration tests
VI (Art. 32-35)Sanctions including fines, coercive measures, and director disqualification
TransitionalAutomatic reclassification of NIS-1 critical service operators

The Stabsstelle Cyber-Sicherheit, reporting to the Prime Minister’s Office, emerges as the critical node managing everything from incident reporting to sanction enforcement.

Sanctions and supervisory enforcement

Under the NIS2 Liechtenstein transposition, penalties for non-compliance are designed to deter negligence at both corporate and executive levels. Fine structures are clearly defined and remarkably steep compared to the earlier framework.

Overview of sanctions under Liechtenstein’s CSG

CategoryMaximum Penalty
Essential EntitiesUp to CHF 10 million or 2% of global turnover
Important EntitiesUp to CHF 7 million or 1.4% of global turnover
Daily coercive finesUp to CHF 100,000

In addition to financial penalties, senior executives face serious personal risks. Directors who repeatedly neglect cybersecurity obligations can be barred from management roles for up to three years under the Personen- und Gesellschaftsrecht (Law on Persons and Companies).

It’s worth noting that while public sector entities cannot be fined, the Stabsstelle’s corrective orders are binding and subject to public disclosure, creating reputational risks.

Impact on key industries

The implementation of NIS2 extends regulatory pressure across a much broader range of industries than its predecessor.

Sector-specific changes under NIS2 in Liechtenstein

SectorKey changes
Manufacturing (electronics, food)Now regulated as “important”; requires OT/IT segmentation and supplier audits
Energy & UtilitiesAdds district heating and wastewater; mandates quarterly board KPIs
HealthcareExpands beyond hospitals to all clinics and labs; demands ISO 27001 governance
Digital InfrastructureCloud providers, DNS operators are in scope regardless of size
FinanceDual compliance with NIS2 and Digital Operational Resilience Act (DORA)
Public AdministrationMinistries and municipalities deemed essential but face no monetary fines

The regulation promotes a culture of proactive cyber governance, particularly pressing for sectors like energy, healthcare, and finance.

What companies should know and do next

If you operate in Liechtenstein, the message is clear: do not underestimate NIS2 compliance. Whether you’re an essential or important entity, the obligations are serious and resource-intensive.

Registration is mandatory through the official portal launched on 1 February 2025. Existing NIS-1 entities had until 31 March 2025 to re-register, while newcomers must act within 30 days of qualifying.

Companies should immediately undertake an Article 21 gap analysis against NIS2 requirements. Typical problem areas include multi-factor authentication rollout, cybersecurity clauses in supplier contracts, and incident simulation exercises.

Planning for audits starting 2027 is also critical. Management boards must document approval of cybersecurity programs now to mitigate potential personal liabilities later.

Preparing today for tomorrow’s cybersecurity challenges

As Liechtenstein’s NIS2 transposition becomes a living reality, the smartest move organisations can make is to treat cybersecurity not just as a technical necessity, but as an executive priority. The NIS2 framework sets a clear expectation: resilience is now part of the cost of doing business.

Companies that embrace these changes early will not only stay compliant but will also strengthen their operational integrity and public trust. The clock is ticking, and readiness today defines resilience tomorrow.

Automate Your Cybersecurity and Compliance

It's like an in-house cybersecurity & compliance team for a monthly subscription! No prior cybersecurity or compliance experience needed.

Share this article

Post on Linkedin
Post on Facebook
Post on X

How useful was this post?

0 / 5. 0

General Counsel

He is regulatory compliance strategist with over a decade of experience guiding fintech and financial services firms through complex EU legislation. He specializes in operational resilience, cybersecurity frameworks, and third-party risk management. Nojus writes about emerging compliance trends and helps companies turn regulatory challenges into strategic advantages.
  • DORA compliance
  • EU regulations
  • Cybersecurity risk management
  • Non-compliance penalties
  • Third-party risk oversight
  • Incident reporting requirements
  • Financial services compliance

Explore further