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).
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
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
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).
Article 10 asks for mechanisms to promptly detect anomalous activities. A configuration change nobody sees until the next review is exactly the opposite.
Inventory, incidents, backups and providers live in different places, and gathering them for each review takes days.
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.
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.
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.
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.
How many the scan checks, how many more carry platform evidence and how many your team answers.
| Provider | Chapter | Articles in the questionnaire | Automatic check | Platform evidence | Your team answers |
|---|---|---|---|---|---|
| II | ICT risk management (5 to 14) | 10 | 4 | 1 | 5 |
| III | ICT-related incidents (17 to 19) | 3 | 0 | 2 | 1 |
| IV | Digital operational resilience testing (24 to 27) | 4 | 0 | 0 | 4 |
| V | ICT third-party risk (28 to 30) | 3 | 0 | 1 | 2 |
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.
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
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.
Pro + add-on
Business + add-on
Since 17 January 2025. It is a regulation: it applies directly in every Member State, with no national law transposing it.