General Counsel

Apr 30, 2025

6 min. read

NIS2 directive regulations and implementation in Latvia

Share:

NIS2 directive regulations and implementation in Latvia

When I first heard discussions about the new cybersecurity obligations sweeping across Europe, Latvia wasn’t the first country that came to mind. Yet today, it’s at the forefront of digital resilience with an ambitious rollout of the EU’s latest directive. The Network and Information Systems 2 Directive (NIS2) marks a monumental leap from its predecessor, aiming to tighten cybersecurity across critical and important sectors. Latvia’s adaptation and implementation story offers a fascinating lens into how a smaller EU member state grapples with major regulatory change. Without further ado, let’s dive into the nuances of NIS2 Latvia developments.

Key take-aways: where Latvia stands today

Latvia’s journey towards full NIS2 transposition has been deliberate yet swift. The country is set to implement the directive through the “Nacionālās kiberdrošības likums” (National Cyber-Security Bill, Saeima print 553/Lp14). This legislation is now moving under an urgent two-reading process in Parliament, indicating Latvia’s strong commitment to timely compliance.

The scope of coverage under Latvia’s NIS2 implementation is set to skyrocket, expanding from around 1,000 essential service operators under the original NIS1 Directive to approximately 6,000–8,000 essential and important entities. Every municipality with over 50,000 inhabitants, a swathe of manufacturing firms, and cloud service providers are newly in-scope.

Here’s a snapshot of Latvia’s current position:

Latvia’s NIS2 status overview (April 2025)

ThemeStatus
Transposition BillDraft approved by Cabinet (Mar 2024); 1st reading passed (Apr 2024); final reading planned (May 2025)
Scope Expansion6,000 – 8,000 entities
Entity ClassesEssential (≥250 FTE/€50M); Important (≥50 FTE/€10M)
Lead AuthoritiesCERT-LV, sector regulators, Digital Security Oversight Committee
Public Sector InclusionMinistries, large municipalities essential but exempt from fines
Maximum Fines€10M/2% turnover for essential; €7M/1.4% for important

From this baseline, it is clear that NIS2 transposition is aggressively expanding obligations beyond the traditionally critical sectors.

Implementation timeline: critical deadlines ahead

The Latvian government is following an accelerated, but detailed path toward full NIS2 compliance. Here’s a closer look at the expected rollout phases:

Latvia’s NIS2 implementation milestones

DateMilestoneStatus
Nov 2023 – Jan 2024Public consultation on draft billCompleted
19 Mar 2024Cabinet approval and referral to SaeimaCompleted
17 Apr 2024First reading in Parliament (urgent procedure)Completed
May 2025Expected final debate and adoptionPending
Q3 2025Law enters into force (15 days after publication)Pending
D + 3 monthsMandatory self-registration at CERT-LVPending
D + 12 monthsGovernance controls deadlinePending
D + 24 monthsFull technical compliance and start of auditsPending

This phased approach means companies will have to act quickly after Q3 2025, especially considering the self-registration obligation within three months. Companies that delay will face enforcement action without the luxury of prolonged adjustment periods.

How Latvia is implementing the NIS2 directive

Unlike some other EU nations that tend to “gold-plate” regulations, Latvia has pledged “minimum implementation” — strictly sticking to NIS2 requirements without adding national extras, save for optional inclusion of the research sector.

Key contents of the Latvian National Cybersecurity Bill

ChapterContent
I–IIScope and definitions (18 sectors + research)
IIIRisk-management duties aligned with EU standards
IVIncident notification rules (24h early alert, 72h update, 30-day final report)
VSupervision and audit powers for CERT-LV and sector regulators
VISanctions, fines, director liabilities
TransitionalAuto-conversion for existing NIS1 entities, new entities on 3/12/24-month compliance timeline

The government has introduced several practical innovations, such as a single self-registration portal managed by CERT-LV and audit cycles (every 3 years for essential entities, every 5 years for important ones).

For more detailed information, you can refer to the Ministry of Culture’s page on cybersecurity and the Latvian Parliament’s document portal.

Sanctions and liability under Latvia’s NIS2

The stakes for non-compliance are high. The fines structure prioritizes global turnover percentages when that leads to higher penalties, reflecting the EU’s ambition to make cybersecurity an executive priority.

Escalation mechanisms move from warnings to binding directions, periodic penalties, and then to monetary fines. In egregious cases, essential entities may even face service suspensions. Particularly notable is that directors themselves can be banned from management roles for up to three years after repeated negligent breaches.

Public bodies, while exempt from monetary penalties, still face mandatory corrective directions from CERT-LV. Failures are publicly disclosed, adding reputational risk even in the absence of financial fines.

Impact on industries: from manufacturing to healthcare

One of the biggest consequences of Latvia’s NIS2 directive is its vast expansion into previously underregulated sectors. Companies once considered peripheral to national cybersecurity are now firmly in scope.

Sectoral changes under Latvia’s NIS2 implementation

SectorChangesNew Obligations
ManufacturingNew regulation for companies ≥50 FTEOT/IT segregation, supplier risk management, red-team testing
Energy & UtilitiesExpanded to LNG, hydrogen, district heating24/7 monitoring, SBOM sharing, board KPIs
HealthcareGrowth from ~40 to >200 regulated providersISO 27001 governance, rapid incident response
Digital InfrastructureSize-agnostic inclusion (e.g., cloud providers)Zero-trust architecture, vendor registry
FinanceMerging NIS2 with DORA regulationsICT third-party management, dual-reporting channels
Public AdministrationMinistries, regions, and major cities essentialCERT-LV baseline adoption, no fines but strict oversight

For a deeper understanding of the NIS2 obligations across sectors, EU NIS2 guidance provides a valuable reference.

What companies should do now to prepare

Latvian businesses cannot afford to wait. Whether you are a mid-sized manufacturer, a public hospital, or a global cloud provider operating in Riga, early preparation is crucial.

First, companies must consult the CERT-LV portal to determine whether they are classified as an “essential” or “important” entity. This classification will define your obligations and audit cycles.

Companies should also immediately:

  • Prepare basic registry data (company registration number, NACE codes, designated cyber contact).
  • Conduct gap analyses against Article 21 of NIS2, focusing on common shortfalls such as multi-factor authentication (MFA), supply chain risk management, and breach drills.
  • Draft standard operating procedures for the 24-hour and 72-hour incident reporting deadlines.
  • Educate board members about the new compliance expectations and liability exposures.

Preparing now ensures companies aren’t caught scrambling once the law officially enters into force.

Building a stronger digital Latvia, step by step

Latvia’s NIS2 journey is far more than an exercise in regulatory compliance. It’s a national strategy to elevate cyber resilience across all sectors of society. From energy to healthcare, from the local grocer to cloud titans, everyone now shares responsibility for securing the country’s digital foundations.

As the final reading approaches in May 2025, organizations have a golden window to not only meet legal obligations but also to genuinely strengthen their cybersecurity posture. By taking proactive measures today, companies can turn NIS2 from a compliance burden into a competitive advantage.

Are you ready to be part of Latvia’s new cybersecurity era?

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?

4.7 / 5. 9

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