DORA

DORA on your cloud, article by article, with evidence

For financial entities and their ICT third-party service providers on AWS, Azure or GCP: the questionnaire with the 20 articles on ICT risk management, incidents, testing and third parties of Regulation (EU) 2022/2554, with part of the technical side checked by the scan.

DORA · Regulation (EU) 2022/2554

II ICT risk10
III Incidents3
IV Testing4
V Third parties3
ScanPlatformTeam
  • 20

    articles of the Regulation in the questionnaire

  • 4

    checked automatically

  • 4

    more with platform evidence

  • 20 €

    per account a month, on top of Pro or Business

The problem

Why DORA is so hard to demonstrate

Your cloud is a third party

AWS, Azure or Google Cloud are ICT third-party service providers: the risk that comes from them is managed as part of ICT risk (Article 28).

Detect, not only protect

Article 10 asks for mechanisms to promptly detect anomalous activities. A configuration change nobody sees until the next review is exactly the opposite.

The evidence is scattered

Inventory, incidents, backups and providers live in different places, and gathering them for each review takes days.

Your ICT risk also lives with your providers

The solution

How AAA Sentinel helps

  1. The 20 articles, one by one

    Start from the DORA template, with Articles 5 to 14, 17 to 19 and 24 to 30, or import the questionnaire you are sent. Each article says what the scan checks and what your team answers, with a summary of what it requires.

  2. Part of the technical side checks itself

    4 articles are checked automatically by scanning your accounts: protection and prevention (9), detection (10), continuity (11) and backups (12). Another 4 carry platform evidence: inventory (8), incidents (17 and 19) and providers (28). Coverage is partial and varies by cloud.

  3. Alerts when something changes

    It reads the AWS, Azure and GCP audit log every 10 minutes and alerts on critical changes (37 checks across the three clouds: 22 on AWS, 8 on Azure and 7 on GCP), such as opening an admin port or making storage public.

  4. Answer and export

    AI drafts answers with the scan’s evidence, you link documents from your evidence archive and your team approves: AI never approves on its own. What you approve stays in your library and you return the Excel file you were sent filled in, format intact, or export it to PDF.

At a glance

The 20 articles, by chapter

How many the scan checks, how many more carry platform evidence and how many your team answers.

The 20 articles, by chapter
ProviderChapterArticles in the questionnaireAutomatic checkPlatform evidenceYour team answers
IIICT risk management (5 to 14)10415
IIIICT-related incidents (17 to 19)3021
IVDigital operational resilience testing (24 to 27)4004
VICT third-party risk (28 to 30)3012

The risk management framework, continuity, testing and provider contracts cannot be seen from the cloud: they are answered in the questionnaire, helped by the drafts and your documents. Where there is platform evidence, the article is still asked and the data backs it; for Article 25, the evidence also shows the status of each account’s vulnerability scanner.

Worked example with a fictitious company

Verdial Pagos SL gets ready for its internal audit’s DORA review

Verdial Pagos SL does not exist: it is a payment institution invented for this example, with accounts on AWS, Azure and Google Cloud. We walk through what an auditor usually asks about DORA and what the team shows from AAA Sentinel; what the platform cannot see, the team provides as a document.

Verdial Pagos SL

AWS Azure Google Cloud DORA
  1. The auditor asksArt. 8

    «Have you identified your ICT assets in the cloud?»

    AAA Sentinel

    The evidence comes from the architecture map: how many resources are inventoried, in how many accounts and on each cloud, with the date of the oldest map. Which business functions each one supports is answered by the team.

  2. The auditor asksArt. 9.4

    «Who has privileged access and how do you protect it?»

    AAA Sentinel

    The rules check privileged roles on the three clouds, credential rotation on AWS and Google Cloud, console MFA on AWS and administrator MFA on Azure, and admin ports and public exposure on all three. Google Workspace MFA is not checked and the team answers it.

  3. The auditor asksArt. 9.2

    «Do you encrypt data at rest and in transit?»

    AAA Sentinel

    The rules check encryption at rest of databases on AWS and Azure, encryption in transit on Azure and Google Cloud, key rotation on AWS and Google Cloud, Key Vault purge protection on Azure and customer-managed keys (CMEK) on Google Cloud. That Google Cloud always encrypts at rest is explained as a provider guarantee.

  4. The auditor asksArt. 10

    «How do you promptly detect anomalous activity?»

    AAA Sentinel

    Every 10 minutes the platform reads the audit log of the three clouds and alerts on critical changes; the 30-day list exports as CSV. The rules also check activity logging and security alerting on AWS, network logs on the three clouds, audit log retention on AWS and, on Azure and Google Cloud, that logs are exported to a destination of your own, and data access logging on Google Cloud.

  5. The auditor asksArt. 12

    «Which backups do you have and how do you restore?»

    AAA Sentinel

    The rules check that databases on AWS and Google Cloud and virtual machines on Azure are backed up. The team shows the backup policy and restore tests with its own document.

  6. The auditor asksArt. 17 · 19

    «Show me the incident register and how you report major ones.»

    AAA Sentinel

    The team keeps the register in the platform: detection, closure and each notification it makes, with its date and reference (one to the financial supervisor is recorded as “Other”); the platform neither reports on its behalf nor classifies severity. If you use AAA Monitoring, the evidence adds its availability incidents.

  7. The auditor asksArt. 28

    «Which ICT third-party service providers do you use, and under which contracts?»

    AAA Sentinel

    The platform provides the supplier inventory as evidence: the connected clouds and AI providers. The register of information, contracts and concentration risk assessment are provided by the team as documents, with an expiry date so the platform warns when they are due for renewal.

In the end, the questionnaire comes out as a PDF with each answer and its evidence per account, and the linked documents go in a zip package with an index of which question each one supports.

Company and situation invented to show how the product is used. AAA Sentinel does not certify or rule on DORA compliance: it gathers the evidence and prepares the questionnaire.

What the add-on includes

Pro + add-on

  • DORA questionnaire, plus ENS, NIS2, ISO 27001 and SOC 2
  • 4 articles checked automatically and 4 more with platform evidence: inventory, incidents and providers
  • “What does this measure require?” on all 20 articles: a summary of what each one requires
  • Critical-change alerts every 10 minutes
  • Security incident register, with the notifications you record
  • Editable questions and the Excel file you are sent returned filled in
  • Encrypted EU evidence archive (1 GB; 5 GB on Business), with malware scanning and expiry alerts
  • Evidence package: a zip with the linked documents and an index with their SHA-256 fingerprint and expiry date
  • Read-only /v1 API and MCP

Business + add-on

  • Everything in Pro
  • Owner, due date and review per question, with email and Slack alerts
  • Four-eyes approval, if you turn it on for the questionnaire: whoever writes an answer cannot approve it
  • A fixed snapshot of each submission, with its SHA-256 fingerprint, downloadable as a PDF
  • Renewal for the next year: approved answers come back as drafts
  • Your clients’ accounts, if you are a service provider
See plans

What it does not do

  • It does not tell you whether DORA applies to you or which regime you fall under: that depends on your type of entity (Article 2) and the proportionality that applies to you.
  • It does not classify or report major incidents for you, nor does it keep the register of information on provider contracts.
  • It does not run penetration tests or threat-led testing: the scan reads your accounts’ configuration.
  • AI drafts answers, but it never approves one on its own.

Frequently asked questions

Since 17 January 2025. It is a regulation: it applies directly in every Member State, with no national law transposing it.