
In this article
The law and regulation in brief
| What it sets out | |
|---|---|
| National Cybersecurity Law | In force since 01.09.2024 (KPMG); transposes the NIS2 Directive (EU) 2022/2555. Latest amendments adopted 04.06.2026. |
| Essential service providers (section 20) | For example electronic communications and trust service providers, public administration, and large companies in sectors such as energy, transport, health, drinking water and digital infrastructure. |
| Important service providers (section 21) | For example medium-sized companies in the section 20 sectors, and medium or large companies in sectors such as postal services, waste management, food, manufacturing and online platforms. |
| Size (section 1) | Large: at least 250 employees, or turnover above €50M, or balance sheet above €43M. Medium: up to 249 employees and turnover of €10–50M or balance sheet of €10–43M. |
| Duty (section 27) | The entity takes "appropriate and proportionate technical and organisational measures to manage cyber risks". |
| Cabinet Regulation No. 397 (section 26) | Adopted 25.06.2025, in force from 02.07.2025 (iFinanses); sets the minimum cybersecurity requirements for entities. |
What Regulation No. 397 says about access and authentication
Paraphrased from the regulation on likumi.lv; point numbers in brackets.
- The entity manages user access rights (49), sets the access level and authentication methods for identified users (50.2), and grants rights on a need-to-know basis (50.3).
- A user may act on information resources only after successful authentication (51.1).
- Mandatory multi-factor authentication (52): for administrator and standard user accounts on class A systems (52.1); for administrator accounts on class B systems (52.2); and for standard user accounts on class B systems when accessed remotely without an encrypted VPN that itself uses MFA (52.3).
- System class follows the confidentiality, integrity and availability classes: class A if at least one is A; class B if at least one is B and none is A (33).
Does the law require eID login in customer portals?
Not directly. Neither the law nor the regulation prescribes a particular method such as Smart-ID or eParaksts, and their rules mainly concern users and accounts of the entity's own information systems. Whether your customer portal accounts count as "users" under the regulation, and which class the system falls into, must be assessed as part of your cybersecurity governance.
Where multi-factor authentication is needed, e-identities are a practical way to provide it: Smart-ID and eParaksts mobile combine a device the person has with a PIN they know. Login with an e-identity also ties the account to a verified person rather than an email address and password.
How Dorvis can help
Strong customer login
Smart-ID, eParaksts mobile, the eID card and banks in one OpenID Connect integration; your system receives a verified first name, last name and personal code.
Learn moreEmployee and admin access
Dorvis can be added as an identity provider in Keycloak or Microsoft Entra if you want e-identity login for internal systems too.
Learn moreAudit log and data in Latvia
Every login is recorded in an audit log, keys are held in a separate secure vault, and infrastructure is in Latvia.
Learn more