Latest feature: Compare your cloud architecture against known frameworks such as NIS and SOC2.Compare your cloud against NIS and SOC2.

Book a demo
AKRIBOS AI
ProductComplianceEngineersSecurityFAQ
Sign InTry AKRIBOSTry AKRIBOS
Home/Compliance/NIS2

NIS2

EU-wide cyber risk-management obligations for essential and important entities.

Updated 13 October 2026

Directive (EU) 2022/2555 widens the sectors in scope and sets minimum measures in Article 21: access control, multi-factor authentication, cryptography, secure acquisition and maintenance of systems, and incident handling. Member states enforce it through national law.

NIS2 took effect across the EU on 18 October 2024 through national transposition. Essential entities face proactive supervision and fines of up to 10 million euro or 2% of global turnover; important entities face reactive supervision and fines of up to 7 million euro or 1.4%. Management bodies are personally accountable for approving and overseeing the measures.

Official text: Directive (EU) 2022/2555 on EUR-Lex.

Who needs it

Essential and important entities in eighteen sectors, among them energy, transport, banking, financial market infrastructure, health, water, digital infrastructure, ICT service management, public administration, space, postal services, waste, chemicals, food, manufacturing, digital providers and research. Medium-sized and larger organisations in those sectors are in scope, as are some smaller ones because of their role.

Article 21 in cloud terms

Article 21(2) lists ten families of measures. Several are configuration questions in AWS, Google Cloud or Azure: access control policies and asset management, the use of multi-factor authentication, policies on cryptography and encryption, security in the acquisition, development and maintenance of systems including vulnerability handling, and incident handling, which depends on logs that actually exist.

Proving the measures work

Article 21(2)(f) asks for policies and procedures to assess the effectiveness of your measures. Supervisors and auditors will look for evidence, not intentions. Scheduled reviews, a record of findings and a trail of fixes are the simplest way to show that the measures are applied in practice and kept up as the cloud changes.

What NIS2 asks of your cloud

The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.

Art. 21(2)(i) · Access control and asset management

Policies for who can reach what, with an inventory of the systems and data they protect, which in the cloud means identities, roles, bindings and the resources they cover.

Art. 21(2)(j) · Multi-factor authentication

MFA or continuous authentication wherever appropriate, starting with privileged and remote access.

Art. 21(2)(h) · Cryptography and encryption

Policies on the use of cryptography, applied as encryption at rest and in transit across storage, databases and endpoints.

Art. 21(2)(e) · Secure acquisition, development and maintenance

Security in how systems are set up and kept, including vulnerability handling, secure configurations and network boundaries.

Art. 21(2)(b) · Incident handling

Detecting, analysing and reporting incidents, which depends on complete audit and network logs.

Art. 21(2)(d) · Supply chain security

Security of relationships with direct suppliers and service providers, including the cloud providers and integrations with access to your environment.

How AKRIBOS checks NIS2

Mapped to your resources

Every NIS2 control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.

Findings come with the fix

A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.

Evidence over time

Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.

Common issues under NIS2

Misconfigurations that fail NIS2 controls, with the control reference for each.

Storage bucket open to the internet

Critical

Object storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.Art. 21(2)(i) access control and asset management.

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.Art. 21(2)(j) multi-factor authentication.

Read more

Database reachable from the internet

Critical

A managed database with a public address and a firewall that lets the world in.Art. 21(2)(e) and 21(2)(i).

Read more

Snapshots or machine images shared publicly

Critical

Disk snapshots, database snapshots or machine images that anyone with a cloud account can copy.Art. 21(2)(i) access control and asset management.

Read more

Over-permissive IAM policies

High

Identities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.Art. 21(2)(i) access control policies.

Read more

SSH or RDP open to 0.0.0.0/0

High

Management ports reachable from any address on the internet.Art. 21(2)(e) security in systems acquisition and maintenance; 21(2)(a) information system security.

Read more

Audit logging incomplete

High

Gaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.Art. 21(2)(b) incident handling, 21(2)(f) assessing effectiveness.

Read more

Long-lived or unused credentials

High

Access keys, service account keys and client secrets that never rotate and are no longer needed.Art. 21(2)(i) access control, 21(2)(j) authentication.

Read more

Instance metadata without session tokens

High

Compute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.Art. 21(2)(e) vulnerability handling and secure maintenance.

Read more

Trust policies open to any account

High

Roles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.Art. 21(2)(d) supply chain security, 21(2)(i) access control.

Read more

Data at rest without the encryption you intended

Medium

Volumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.Art. 21(2)(h) cryptography and encryption.

Read more

Transport encryption not enforced

Medium

Endpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.Art. 21(2)(h) cryptography and encryption.

Read more

Network flow logs off

Medium

No record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.Art. 21(2)(b) incident handling.

Read more

Default network with permissive rules

Medium

Workloads running in the cloud-created default network, which ships with rules nobody would write deliberately.Art. 21(2)(e) secure configuration and maintenance.

Read more

NIS2 questions

Are we an essential or an important entity?

It depends on your sector and size: essential entities are mostly large organisations in the highest-criticality sectors of Annex I, important entities are medium-sized ones there and organisations in the Annex II sectors. Your national authority publishes the criteria, and member states can designate entities individually.

What are the deadlines?

Member states had to apply NIS2 from 18 October 2024. National laws set registration and compliance dates, and some countries are still finalising theirs, so check your own transposition.

Which NIS2 measures can a cloud review cover?

Access control and asset inventory, multi-factor authentication, encryption, secure configuration and vulnerability handling, and the logging that incident handling relies on. Governance, training, business continuity and supply-chain contracts remain yours.

Is NIS2 relevant if we are already working on DORA?

DORA takes precedence for financial entities' ICT risk, but the technical expectations overlap almost completely. One set of cloud evidence covers both.

Other frameworks

CIS Benchmarks

The baseline configuration standard for AWS, Google Cloud and Azure.

Read more

SOC 2

Evidence that your cloud controls work, not just that they exist.

Read more

ISO/IEC 27001

The international standard for an information security management system, applied to your cloud.

Read more

DORA

The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.

Read more

PCI DSS v4

Requirements for every environment that stores, processes or transmits cardholder data.

Read more

NIST CSF 2.0

The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.

Read more

BSI C5

Germany's cloud computing compliance criteria catalogue.

Read more

DNB Good Practice Information Security

What De Nederlandsche Bank expects of the financial institutions it supervises.

Read more
All frameworks

Attackers don't wait for your next audit. Neither does AKRIBOS.

Connect AWS, Google Cloud or Azure and get your first review today.

Run your first reviewRun your first review
Cinematic desert landscape at dusk with a lone silhouette standing before a warm amber glow, surrounded by dark rolling hills and a deep blue sky.
AKRIBOS

The AI agent that reviews and hardens your cloud, right from your terminal or our dashboard.

Navigation

How It WorksAttack PathsContinuous ReviewsComplianceCommon Cloud IssuesFor EngineersSecurityFAQ

Information

ContactPrivacy PolicyTerms of ServiceData Processing AgreementResponsible Disclosure

Socials

LinkedIn

© 2026 AKRIBOS AI B.V. All rights reserved.

AKRIBOS is a trade name of AKRIBOS AI B.V., registered with the Netherlands Chamber of Commerce (KvK) under number 83548335, Amsterdam, The Netherlands.