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/DORA

DORA

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

Updated 13 October 2026

Regulation (EU) 2022/2554 has applied since 17 January 2025. It requires banks, insurers, investment firms, payment institutions, crypto-asset providers and the other financial entities in Article 2 to run an ICT risk-management framework, with specific expectations on protection, detection, testing and third-party risk.

DORA is law, not a standard you can opt into. Financial entities must map their framework to it and show supervisors evidence that the controls operate, and critical ICT third-party providers come under direct oversight. Regulatory technical standards spell out the security measures in detail, from identity and access management to logging and encryption.

Official text: Regulation (EU) 2022/2554 on EUR-Lex.

Who needs it

Banks, payment and e-money institutions, investment firms, insurers and reinsurers, pension funds, crypto-asset service providers and the other financial entities listed in Article 2, plus the ICT providers that serve them. In the Netherlands, DNB and the AFM supervise it.

What Article 9 asks of your cloud

Article 9, protection and prevention, is where cloud configuration lands: a network and infrastructure management structure with segregation, policies that limit logical access on a least-privilege basis, strong authentication and protected cryptographic keys, documented change management, and patching. Article 10 adds detection: mechanisms that promptly spot anomalous activity across the estate, which presupposes complete logging.

Evidence for your supervisor

DORA expects a documented ICT risk-management framework, reviewed at least yearly and after major incidents, and the ability to show that controls actually operate. A continuous review with an audit trail gives you that record, and the register of information in Chapter V needs an accurate inventory of the cloud services behind each function.

What DORA asks of your cloud

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

Art. 8 · Identification

An inventory of ICT assets and dependencies, kept current, including the cloud accounts, networks and services that support critical or important functions.

Art. 9(4)(b) · Network and infrastructure management

A sound structure with network segregation and segmentation, so a compromised component cannot reach the rest.

Art. 9(4)(c)–(d) · Access and authentication

Logical access limited to what is required, least privilege, strong authentication, and protection of cryptographic keys.

Art. 9(3) · Data protection

Security of data in transit, protection against unauthorised access and loss, and preservation of confidentiality, integrity and availability.

Art. 10 · Detection

Mechanisms that promptly detect anomalous activities, with multiple layers of control and alert thresholds, which requires complete logging across accounts.

Art. 28–30 · ICT third-party risk

Contractual and monitoring requirements for ICT providers, and a register of information listing every arrangement, including cloud services.

How AKRIBOS checks DORA

Mapped to your resources

Every DORA 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 DORA

Misconfigurations that fail DORA 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. 9(3) data protection and Art. 9(4)(c) logical access.

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.Art. 9(4)(d) strong 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. 9(4)(b) network segregation, Art. 9(3) data protection.

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. 9(3) confidentiality of data.

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. 9(4)(c) least-privilege access management.

Read more

SSH or RDP open to 0.0.0.0/0

High

Management ports reachable from any address on the internet.Art. 9(4)(b) network and infrastructure management, segregation.

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. 10 detection of anomalous activities; Art. 17 incident management.

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. 9(4)(c)–(d) access management and protection of authentication secrets.

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. 9(4)(c) logical access, 9(4)(f) patches and updates.

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. 9(4)(c) access management, Art. 28 ICT third-party risk.

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. 9(3) protection of data, Art. 9(4)(d) cryptographic keys.

Read more

Transport encryption not enforced

Medium

Endpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.Art. 9(3)(a) security of the means of data transfer.

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. 10 detection.

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. 9(4)(b) network segregation.

Read more

DORA questions

Does DORA apply to us if we are not a bank?

Article 2 lists more than twenty types of financial entity, from payment institutions and investment firms to insurers, pension funds and crypto-asset service providers. If you are supervised under EU financial law, assume it applies and check the exemptions for microenterprises.

How does DORA relate to NIS2?

DORA is the specific law for the financial sector: where both could apply, DORA takes precedence for ICT risk. Both expect access control, strong authentication, encryption and logging, so the same cloud evidence serves both.

What does a DORA cloud review produce?

A control-by-control view of Articles 8 to 10 against your actual accounts: which networks are segregated, which identities hold privileged access, where strong authentication is missing, what is logged, and the fix for each gap, with a dated record for your supervisor.

Does AKRIBOS cover the register of information?

AKRIBOS gives you the inventory of cloud accounts, services and dependencies the register needs. Compiling and submitting the register itself remains your responsibility.

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

NIS2

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

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.