Cloud Tests

Automated infrastructure resilience testing for DORA compliance.

What are Cloud Tests?

Cloud Tests are automated checks that verify your infrastructure behaves correctly under stress, failure, and recovery scenarios. They run against your connected cloud environments and produce pass/fail results that serve directly as DORA evidence.

DORA (Digital Operational Resilience Act) requires significant financial entities to conduct Threat-Led Penetration Testing (TLPT) and demonstrate operational resilience. Cloud Tests in Matproof automate the technical layer of this requirement.

Cloud Tests are primarily relevant for organizations in scope for DORA. If you are pursuing ISO 27001 or SOC 2, the results can also support resilience and availability controls in those frameworks.

Why DORA requires resilience testing

DORA Article 25 mandates that ICT systems supporting critical functions are tested for their ability to:

• Withstand disruptions and continue operating
• Recover from failures within defined time objectives
• Maintain data integrity during incidents

Manual testing alone is not sufficient for continuous compliance. Cloud Tests give you automated, repeatable proof.

Supported cloud providers

Connect your infrastructure before running tests:

Provider	Status
AWS	Available
Azure	Available
GCP	Available
Hetzner	Available

To connect a provider, go to Settings → Integrations and follow the setup guide for your cloud.

Test types

Availability tests

Verify that services remain accessible under expected load conditions. Confirms uptime SLAs are achievable.

Recovery tests

Simulate failures and measure how quickly systems restore to normal operation. Tests your RTO (Recovery Time Objective).

Failover tests

Trigger failover to redundant systems and confirm traffic reroutes correctly without data loss or extended downtime.

Data integrity tests

Validate that data remains consistent and uncorrupted after failures, restores, or replication events.

Setting up your first test

1. Go to Cloud Tests in the sidebar
2. Click New test
3. Fill in the test details:
   • Name — a descriptive label (e.g., “EU production failover — monthly”)
   • Target environment — select your connected cloud account and region
   • Test type — choose from the four types above
   • Schedule — one-time, weekly, or monthly
4. Click Run test or Save schedule to activate

Run tests in staging environments first. Failover and recovery tests interact with live infrastructure and can cause brief disruptions if misconfigured.

Scheduling recurring tests

DORA requires ongoing resilience validation, not just point-in-time audits. Use recurring schedules to stay compliant continuously.

Recommended schedule:

• Availability tests: weekly
• Recovery and failover tests: monthly
• Data integrity tests: after every major infrastructure change and monthly

Tests run automatically at the scheduled time. You receive an alert if a test fails or produces a partial result.

Reviewing results

Each test run produces a result record with:

Field	Description
Result	Pass / Fail / Partial
Duration	How long the test took to complete
Target	The environment and service tested
Timestamp	When the test ran
Details	Breakdown of what was tested and what failed

A Partial result means some sub-checks passed and others failed. Expand the result to see which components need attention.

To view results:

1. Go to Cloud Tests
2. Click any test to open its history
3. Filter by date range or result type

Using results as DORA evidence

Passed test results are automatically available as evidence in the Evidence module.

To link a test result to a DORA control:

1. Open the relevant DORA control in Controls
2. Click Add evidence
3. Select Cloud test result and choose the test
4. The result is attached and the control status updates when evidence is sufficient

Map each test type to its corresponding DORA control when you set the test up. This keeps evidence collection automatic and removes manual work during audits.

Alerts on failure

When a test fails, Matproof sends an alert to:

• The test owner
• Any team members subscribed to compliance alerts

Alerts include the test name, what failed, and a direct link to the result. Resolve the underlying infrastructure issue, then re-run the test to generate a fresh pass result for your evidence trail.