Cloudflare Authorised Service Delivery Partner (ASDP)

DORA Compliance with Cloudflare

DORA is in force. National authorities are actively supervising. Every bank, insurer, asset manager, and fintech operating in the EU must demonstrate digital operational resilience, or face supervisory consequences. Yet most financial entities are still not fully compliant. Brixio deploys Cloudflare as the technical foundation for DORA compliance: ICT risk management, incident detection, resilience testing readiness, and auditable third-party oversight. One architecture covering five pillars.

  • Map the five pillars to a unified Cloudflare deployment
  • Detect ICT incidents within DORA's 4-hour window
  • Document third-party oversight to Article 28
  • Test resilience under TIBER-EU scenarios
dora-console · brixio.one DORA Compliance LIVE enforceable · 17 Jan 2025 FIVE PILLARS · STATUS PILLAR 1 ICT Risk Articles 5-16 PILLAR 2 Incidents Articles 17-23 PILLAR 3 Testing Articles 24-27 PILLAR 4 3rd Party Articles 28-44 PILLAR 5 Sharing Article 45 Incident reporting timeline Article 19 · per major ICT incident T+0 Detection T+4h Initial notification T+72h Intermediate report T+1 month Final report Article 28 third-party register 2 of 2 verified Brixio ASDP ISO 27001:2022 Cloudflare deployment partner · Article 30 aligned Cloudflare SOC 2 ISO 27001:2022 PCI-DSS Underlying platform · 5 pillars covered Lex specialis · DORA prevails for financial entities DORA Financial entities NIS2 160k+ entities (general) → Same Cloudflare architecture covers both
21
Categories of financial entities
DORA applies to 21 categories of regulated financial entities across the EU, from banks to crypto-asset service providers.
4h
Initial incident notification
Financial entities must provide an initial notification of a major ICT incident to competent authorities within 4 hours of classification.
5
DORA pillars
ICT risk management, incident management and reporting, resilience testing, third-party risk management, and information sharing.
400+
Brixio projects
Cloudflare projects delivered across regulated industries — banking, insurance, fintech, and financial services in EMEA and the GCC.
Trusted by financial entities across EMEA and the GCC
AXA
Vision Bank
Commercial Bank Of Dubai
Boubyan Bank
Investment Bank
GIG
DORA in force

DORA is enforceable. Most entities are not compliant.

The Digital Operational Resilience Act (Regulation EU 2022/2554) has been enforceable since 17 January 2025. Over a year later, studies show that the majority of financial entities have not achieved full compliance. National authorities (ACPR, BaFin, CSSF, AMF) are now in active supervision mode.
01

21 categories of financial entities

DORA applies broadly across the regulated financial sector:

  • Credit institutions, payment and electronic money institutions
  • Insurance and reinsurance undertakings
  • Investment firms, central securities depositories, central counterparties
  • Management companies (UCITS, AIFM)
  • Crypto-asset service providers (since MiCA alignment)
  • Crowdfunding service providers, credit rating agencies
02

Article 28: ICT third parties are caught

Financial entities must assess, monitor, and document the resilience of their ICT providers. If you provide cloud, security, or managed services to a bank or insurer, your compliance posture is their regulatory concern.

  • Mandatory register of ICT third-party arrangements
  • Audit rights, data access provisions, exit strategies
  • Contractual alignment with Article 30 requirements
03

Supervision is active, not theoretical

ACPR (France), BaFin (Germany), CSSF (Luxembourg), and the AMF are conducting inspections and can impose corrective measures, restrict activities, or publish findings. The grace period is over.

04

Lex specialis of NIS2

For financial entities, DORA takes precedence over NIS2. But the requirements overlap significantly: risk management, incident reporting, supply chain oversight. An architecture that addresses one typically addresses both.

The grace period is over. DORA does not ask for a compliance report. It asks for an architecture that can be tested, audited, and proven resilient.
BrixioOne
DORA × Cloudflare

The five pillars of DORA, mapped to Cloudflare

DORA organises digital operational resilience around five pillars. Each pillar maps to specific Cloudflare capabilities deployed by Brixio as a unified platform. One architecture, five pillars covered.

Articles 5-16

ICT Risk Management

Financial entities must implement a comprehensive ICT risk management framework covering identification, protection, detection, response, and recovery.

  • WAF and DDoS protection for online banking, trading platforms, insurance portals
  • Zero Trust Access for identity-based, context-aware access to critical financial systems
  • Magic WAN for network segmentation isolating trading, core banking, and payment infrastructure
  • Gateway SWG for DNS filtering and outbound traffic control
  • API Shield for open banking APIs, payment gateways, data exchange endpoints
Scope of DORA

Who is affected, directly and indirectly

DORA applies broadly across the regulated financial sector and reaches into the supply chain. Three audiences should pay attention. By sector, Brixio supports DORA compliance for banking, insurance, fintechs and asset managers.

01Direct scope

Financial entities

21 categories of regulated financial entities: credit institutions, payment and electronic money institutions, investment firms, central securities depositories, insurance and reinsurance undertakings, management companies (UCITS, AIFM), crypto-asset service providers (since MiCA alignment), central counterparties, credit rating agencies, crowdfunding service providers.

02Indirect scope

ICT third-party providers

Article 28 places explicit obligations on financial entities to monitor, assess, and document the resilience of third-party ICT providers. Cloud providers, MSSPs, infrastructure operators, and SaaS vendors serving regulated financial entities are indirectly but materially affected.

03Cross-border reach

Non-EU and global providers

Non-EU financial entities operating in EU markets, or serving EU-regulated clients, are caught through their contractual relationships. Brixio supports DORA compliance across EMEA and the GCC for banks and fintechs operating cross-border.

DORA × NIS2

Lex specialis, shared architecture

DORA is explicitly defined as a lex specialis of NIS2 (Article 1(2) of NIS2). For financial entities subject to both, DORA's sector-specific requirements take precedence. An architecture that satisfies DORA's five pillars simultaneously covers NIS2's technical requirements for financial entities. This is why Brixio designs compliance architectures that address both regulations from a single Cloudflare deployment.

01Incident reporting

Tighter timelines on DORA

DORA: 4h initial / 72h intermediate / 1 month final.
NIS2: 24h early warning / 72h full notification.
Same Cloudflare capability covers both: real-time logging, single-pane correlation, SIEM export.

02Third-party oversight

Detailed under DORA

DORA: Articles 28-44 (detailed register, due diligence, contractual provisions, audit rights).
NIS2: Article 21 (general supply chain security).
Brixio's ASDP and ISO 27001:2022 evidence supports both regimes.

03Resilience testing

Mandatory under DORA

DORA: Articles 24-27 (regular testing, mandatory TLPT for significant entities).
NIS2: implied in Article 21.
Cloudflare configuration audit and policy validation are aligned with TIBER-EU testing requirements.

Why Brixio

A compliance deployment partner, not a consultant

DORA compliance requires more than policies on paper. It requires an ICT infrastructure that can be tested, audited, and proven resilient. Brixio delivers the technical architecture.

100% Cloudflare

WAF, DDoS, Zero Trust, Magic WAN, API Shield, Gateway deployed as a unified platform. One architecture, five pillars covered.

ASDP & ISO 27001:2022

Cloudflare Authorised Service Delivery Partner with direct escalation to Cloudflare engineering. Compliance governance built into our own operations, supporting your Article 28 due diligence.

4-hour incident ready

Single-pane Cloudflare correlation qualifies a major ICT incident in time to meet DORA's 4-hour initial notification, where stacked tooling typically does not.

EMEA & GCC coverage

Engineers in Luxembourg, Paris, Dubai, and Singapore. Deep knowledge of ACPR (France), CSSF (Luxembourg), BaFin (Germany), and GCC financial regulators (CBUAE, SAMA, CBB).

Compliance-first delivery

Every configuration mapped to DORA's five pillars and documented for audit readiness. Compliance evidence is an output, not an afterthought.

400+ projects delivered

Cloudflare projects across regulated industries, including banking institutions in the Gulf and Europe.

Get started

Turn DORA compliance into operational resilience.

DORA is not a checkbox exercise. Brixio's professional services team deploys the Cloudflare architecture mapped to your supervisor's expectations, and an assessment is the natural starting point.

Trusted and certified
  • ASDPAuthorised Service Delivery Partner
  • ISO27001:2022 certified
  • 400+Projects in regulated industries
FAQs

DORA Compliance FAQ

DORA (Digital Operational Resilience Act, Regulation EU 2022/2554) is a European regulation that imposes digital operational resilience obligations on financial entities. It covers ICT risk management, incident reporting (initial notification within 4 hours), resilience testing, third-party ICT oversight, and information sharing. It applies directly across all EU member states and has been enforceable since January 2025. National authorities are now actively supervising compliance.

DORA applies to 21 categories of financial entities, including banks, payment institutions, insurance undertakings, investment firms, asset managers, and crypto-asset service providers. It also affects ICT third-party service providers serving these entities through Article 28's oversight requirements.

DORA is a lex specialis of NIS2: it takes precedence for financial entities. DORA's requirements are more detailed, with specific incident reporting timelines (4h/72h/1 month vs NIS2's 24h/72h), mandatory resilience testing including TLPT, and comprehensive third-party ICT oversight provisions. The underlying technical requirements overlap significantly.

Cloudflare covers a significant portion of DORA's technical requirements across all five pillars. However, DORA also includes organisational requirements (governance frameworks, internal policies, testing programmes, contractual arrangements with ICT providers) that require internal action. Brixio handles the technical deployment and compliance mapping.

As an ASDP-certified and ISO 27001:2022-certified partner, Brixio provides the documentation, audit trails, and compliance evidence that your Article 28 due diligence requires. Every configuration decision is documented. Engagement terms align with DORA's contractual requirements (Article 30).

Yes. Payment institutions, electronic money institutions, and crypto-asset service providers are directly in scope. Additionally, fintechs providing ICT services to regulated financial entities fall under Article 28's third-party oversight requirements, even if the fintech itself is not directly regulated by DORA.

In France, the ACPR (Autorite de Controle Prudentiel et de Resolution) is the competent authority for DORA supervision of credit institutions and insurance undertakings. The AMF supervises investment firms and management companies. Both authorities can request evidence of digital operational resilience at any time.

Turn DORA compliance into operational resilience

DORA is not a checkbox exercise. It is a mandate to prove that your financial infrastructure can withstand, respond to, and recover from ICT disruptions. Brixio deploys the Cloudflare architecture that makes that proof auditable.

Talk to an expert

Your DORA gap, mapped to a compliance roadmap.

Tell us where you are with this solution. A Brixio engineer comes back to you with a clear next step — workshop, free assessment, or scoping call.

  1. You send a short messageTwo minutes, no qualification questionnaire.
    ≤ 5 min
  2. An engineer reads itWe pick the right next step based on your context and the solution(s) you flagged.
    ≤ 4 hours
  3. Callback scheduledA 30-min call with a certified Cloudflare engineer.
    ≤ 24 hours
  4. Engagement startsWorkshop, free assessment, scoping call — whichever fits your situation.
    Day 1+
We help scope the right next step.You decide whether to engage. ISO 27001:2022.
Step 01 · Send your message

Tell us a bit, get a callback.

Other Cloudflare solutions you're exploring (optional)

By submitting, you accept that a Brixio engineer will reach out. No newsletter, no spam. ISO 27001:2022.