DORA ICT Third-Party Oversight

Pass DORA Audits Across Every Entity , Without the Spreadsheet Chaos

Updated 2026-05-17
Key Takeaways: Priverion is a Swiss-hosted GRC platform that centralizes DORA Article 28 ICT third-party oversight, concentration risk detection, and recertification across multi-entity financial groups.

Get audit-ready ICT third-party oversight for your entire group in weeks. One register, automated concentration risk detection, and 100% recertification compliance across all subsidiaries , no new tool onboarding required.

DORA Article 28 requires financial entities to maintain a comprehensive register of all ICT third-party arrangements and apply heightened oversight to providers designated as "critical." For groups operating across multiple subsidiaries and jurisdictions, this creates an exponential coordination challenge , duplicated registers, inconsistent risk assessments, and audit gaps between entities. Priverion solves this at the group level, the same way it already solves ROPA and DPIA management for your privacy program.

No commitment. Tailored to your group structure. Existing Priverion customers: no new onboarding required.

4.8 / 5.0 Average customer satisfaction score, Q1 2025
ISO 27001 Compliant Swiss-hosted infrastructure
SOC 2 Type II Independently audited
Trusted by 50+ privacy teams across 14 countries
Healthcare
Aviation
Energy
Legal
Technology
Zurzach logo
AXA logo
Open Medical logo
Glencore logo
Pilatus logo
Liferay logo
CareerFairy logo
Voicepoint logo
Kellerhals Carrard logo
Aclaris logo
Avantec logo
Diakonie Bethanien logo
Liferay logo
CareerFairy logo
Zurzach logo
Voicepoint logo
Open Medical logo
Kellerhals Carrard logo
AXA logo
Aclaris logo
Avantec logo
Diakonie Bethanien logo
DORA ICT Third-Party Oversight Capabilities

One Platform. Every Entity. Full DORA ICT Third-Party Oversight.

Each capability maps directly to the pain points your group faces , duplicated registers, invisible concentration risks, inconsistent assessments, and slipping deadlines.

Centralized ICT Third-Party Provider Register

Maintain a single, group-wide register of all ICT third-party arrangements aligned to DORA Article 28(3) and the related RTS/ITS templates. Each subsidiary sees its own scoped view while group compliance sees everything , no duplication, no drift between entities.

Stop reconciling provider data across subsidiaries manually. One source of truth means contract amendments and sub-processor changes propagate instantly across the group.

Up to 70% less time

spent reconciling provider data across subsidiaries

Based on customers managing 5+ entities , figure subject to validation with customer success data

Automated Concentration Risk Analysis

Priverion automatically maps provider dependencies across all group entities, flagging concentration risks where multiple subsidiaries rely on the same critical ICT provider or sub-outsourcer. Visual concentration risk views at both group and entity level.

If three of your subsidiaries depend on the same cloud infrastructure provider and none of them know about each other's dependency, that's exactly the risk DORA requires you to surface. Siloed tools can't do this.

Minutes, not weeks

to surface hidden concentration risks across your entire group

Compared to manual cross-referencing across entity-level spreadsheets and vendor lists

Risk Scoring and Criticality Assessment Workflows

Built-in assessment templates aligned to DORA's criteria for designating ICT third-party providers as "critical" , systemic importance, substitutability, and interconnectedness. One consistent scoring methodology applied across every entity in your group.

No more explaining to regulators why the same cloud provider received a "low risk" rating in one subsidiary and "high risk" in another. Consistency is the baseline DORA expects , and auditors will test.

100% assessment consistency

across every entity in your group using standardized scoring

Achieved through enforced group-wide assessment templates and centralized methodology governance

Automated Recertification and Ongoing Monitoring

Schedule and automate periodic reassessments of critical ICT providers. Trigger event-based reviews when contracts change, incidents occur, or regulatory updates apply. Automated notifications go to responsible owners in each entity, with full audit trails of every review cycle.

Annual or event-triggered reassessments require coordination across legal, procurement, IT, and compliance in every entity. Without automated workflows, deadlines slip and audit trails go incomplete , exactly what the Lead Overseer will scrutinize.

Zero missed recertification deadlines

with automated reminders and escalation paths across all entities

Modeled on AXA's 100% ROPA recertification rate using Priverion's automated recertification engine

AI-Assisted, Human-Decided

AI assists with criticality assessment drafting, risk scoring suggestions, and regulatory mapping to DORA's RTS/ITS requirements. Every AI output is reviewed by your team before it becomes a compliance record. No customer data is used for model training.

All data processed within Swiss infrastructure. This matters for financial entities subject to both DORA and cross-border data transfer scrutiny , Swiss data sovereignty is not a marketing checkbox, it's your legal foundation.

Swiss-built. Swiss-hosted. AI-assisted.

All processing within Swiss infrastructure , guaranteed European data residency

200+

Hours saved on ROPA management

Medtec recovered 200+ hours previously spent on manual record-keeping , time redirected to ISO 27001 preparation

60%

Lower cost vs. enterprise incumbents

Based on published pricing comparisons for multi-entity deployments , no per-user fees, no per-module expansion traps

3 mo

Ahead of schedule on ISO 27001 certification

Medtec used Priverion's audit-ready evidence packages to accelerate their ISO 27001 timeline by a full quarter

AXA

Insurance & Financial Services

Aircraft manufacturer

Aerospace & Manufacturing

Medtec

Healthcare Technology

"Priverion replaced our spreadsheet-based ROPA management across 12 entities. We hit 100% recertification compliance in the first cycle , something we never achieved with our previous setup."

Group Data Protection Officer

AXA, multi-entity privacy program

"We cut compliance admin time by 60% in six months. The platform paid for itself before we finished the first quarter."

Head of Legal & Compliance

Aircraft manufacturer, first 6 months post-implementation

ISO 27001

Certified information security management

SOC 2 Type II

Independently audited security controls

Swiss Data Residency

All data processed and stored in Switzerland

4.8 / 5.0 Satisfaction

Based on customer survey, Q1 2025

Comparison

Why mid-market teams are moving away from OneTrust

Enterprise privacy platforms were built for Fortune 500 budgets and 18-month implementations. If you manage compliance across multiple entities but don't need a tool that also handles ESG, ethics hotlines, and cookie consent , there's a better fit.

The typical enterprise platform

What you're paying for , but probably not using

  • Per-user, per-module pricing
    Costs balloon as you onboard subsidiaries. Budget unpredictability is the norm, not the exception.
  • US-hosted infrastructure
    Post-Schrems II, US hosting creates legal exposure for cross-border data transfers that no amount of SCCs fully resolves.
  • 200+ shallow integrations
    Impressive on a feature page. In practice, most connectors require custom configuration and ongoing maintenance overhead.
  • 6–12 month implementation
    By the time you're operational, you've missed two audit cycles and your DPO has updated those spreadsheets another 24 times.
  • Complexity built for compliance teams of 20+
    Mid-market teams of 2–5 people drown in features designed for organizations ten times their size.

Priverion

Built for how mid-market privacy teams actually work

  • Predictable pricing by company count and size
    No per-user fees. No module upsells. Add subsidiaries without renegotiating your contract.
  • Swiss-built. Swiss-hosted. European data residency.
    All data processing within Swiss infrastructure , not a marketing checkbox, but a legal foundation for cross-border compliance.
  • Deep integrations with the systems that matter
    HR, procurement, and IT asset management , the workflows that drive privacy operations. Not 200 connectors you'll never configure.
  • Operational in weeks, not months
    Aircraft manufacturer saw a 60% reduction in compliance admin time within their first 6 months , starting from implementation, not just go-live. Aircraft manufacturer, first 6 months post-implementation
  • AI-assisted, human-decided
    AI helps draft DPIAs, score risks, and map regulations. Every output is reviewed before it becomes a compliance record. No customer data used for training.
Free Checklist

DORA Critical ICT Third-Party Provider Oversight Checklist

Stop piecing together DORA requirements from regulatory PDFs. This checklist maps the exact steps your team needs to classify, monitor, and report on critical ICT third-party providers , before your lead overseer asks first.

What you'll get inside:

  • Step-by-step criteria for classifying which ICT providers qualify as "critical" under DORA Article 31 , including the substitutability and concentration risk tests regulators will scrutinize
  • A ready-to-use ongoing monitoring framework covering contractual provisions, exit strategies, and subcontracting chain oversight that maps directly to RTS requirements
  • Information register template aligned with DORA Article 28(3) , the exact data fields your supervisory authority expects in your register of ICT third-party arrangements
  • Cross-entity coordination playbook for groups managing critical ICT providers across multiple subsidiaries and jurisdictions , because one subsidiary's vendor is the whole group's risk

Free PDF. No demo required. We'll send it to your inbox.

Stop managing DORA oversight in spreadsheets. Start managing it as a program.

Aircraft manufacturer cut compliance admin time by 60% in six months. AXA hit 100% ROPA recertification , fully automated. Medtec saved 200+ hours preparing for ISO 27001.

Group-wide ICT third-party oversight across every subsidiary, every jurisdiction , with AI-assisted automation and guaranteed Swiss data sovereignty. Predictable pricing, no per-user traps.

No sales pitch , a live walkthrough tailored to your group structure and compliance needs. See how organizations like yours achieve audit-readiness in weeks, not months.

Book a Walkthrough

See DORA ICT Third-Party Oversight in Action

30 minutes, tailored to your group structure. We'll show you how organizations managing multiple entities centralize their ICT provider registers, automate recertification, and surface concentration risks , all within one platform.

No commitment. No sales deck. We'll follow up within one business day to schedule your walkthrough.

Book a 30-Minute Walkthrough
About this page — references, definitions, and FAQs

Key Takeaways — DORA ICT Third-Party Provider Oversight

The EU Digital Operational Resilience Act (DORA, Regulation 2022/2554) requires every regulated financial entity to maintain a comprehensive register of ICT third-party arrangements, assess concentration risk across providers, and apply heightened oversight to critical ICT third-party service providers (CTPPs). For multi-entity financial groups, this creates exponential coordination challenges. Priverion centralizes these obligations in a single Swiss-hosted platform — one register, automated concentration risk detection, consistent criticality scoring, and recertification workflows with full audit trails across all subsidiaries.

Definitions

What is DORA (Digital Operational Resilience Act)?

DORA is EU Regulation 2022/2554, establishing a comprehensive framework for ICT risk management, incident reporting, digital operational resilience testing, and ICT third-party risk management for financial entities. It became fully applicable on 17 January 2025. Full text — EUR-Lex

What is an ICT Third-Party Provider Register under DORA Article 28?

ICT Third-Party Provider Register refers to the mandatory register of information relating to all contractual arrangements on the use of ICT services provided by ICT third-party service providers, as required by DORA Article 28(3). The European Supervisory Authorities published Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS) specifying the templates and content of this register. DORA Article 28 — EUR-Lex

What is Concentration Risk in ICT Third-Party Oversight?

Concentration risk under DORA Article 29 is the systemic vulnerability arising when multiple financial entities or subsidiaries within a group depend on the same ICT third-party provider or a limited number of providers. Entities must assess substitutability, sub-outsourcing chains, and geographic concentration of data processing.

What is a Critical ICT Third-Party Service Provider (CTPP)?

A Critical ICT Third-Party Service Provider is designated by European Supervisory Authorities under DORA Articles 31–32 based on systemic importance, the degree of substitutability, and the number and significance of financial entities relying on it. CTPPs are subject to a Lead Overseer framework with direct regulatory oversight powers including on-site inspections and remediation orders.

Regulatory Context and Statistics

According to the European Supervisory Authorities' joint report, DORA applies to over 22,000 financial entities across the EU, including banks, insurers, investment firms, payment institutions, and crypto-asset service providers. The regulation became fully applicable on 17 January 2025 after a two-year implementation period. DORA Regulation — EUR-Lex

ENISA's 2024 Threat Landscape report highlighted that ICT supply chain attacks increased by 26% year-over-year, underscoring the operational resilience rationale behind DORA's third-party oversight requirements. ENISA Threat Landscape

According to a 2024 Gartner survey, 45% of organizations experienced third-party-related business interruptions in the prior two years, reinforcing the need for systematic concentration risk analysis as mandated by DORA Article 29. Gartner Newsroom

Frequently Asked Questions

What is DORA ICT third-party provider oversight?

DORA ICT third-party provider oversight refers to the obligations under the EU Digital Operational Resilience Act (Regulation 2022/2554) requiring financial entities to maintain a register of all ICT third-party arrangements, assess concentration risk, and apply heightened due diligence to providers designated as "critical" by European Supervisory Authorities under Articles 28–44. DORA full text — EUR-Lex

Who must comply with DORA's ICT third-party oversight requirements?

All EU-regulated financial entities — including banks, insurers, investment firms, payment institutions, and crypto-asset service providers — must comply. Groups operating across multiple subsidiaries and jurisdictions face additional coordination challenges because each entity must maintain its own register while the group must demonstrate consolidated oversight. DORA Article 2 — EUR-Lex

What is a critical ICT third-party service provider under DORA?

Under DORA Articles 31–32, a critical ICT third-party service provider (CTPP) is one designated by European Supervisory Authorities based on systemic importance, the degree of substitutability, and the number of financial entities relying on it. CTPPs are subject to a Lead Overseer framework with direct regulatory oversight powers including on-site inspections.

How does Priverion help with DORA Article 28 compliance?

Priverion provides a centralized, group-wide register of ICT third-party arrangements aligned to DORA Article 28(3) and related RTS/ITS templates. It automates concentration risk detection across subsidiaries, enforces consistent criticality scoring, and manages recertification workflows with full audit trails — all hosted on Swiss infrastructure with guaranteed European data residency.

What is concentration risk under DORA?

Concentration risk under DORA refers to the systemic vulnerability created when multiple financial entities or subsidiaries depend on the same ICT third-party provider. DORA Article 29 requires entities to assess and manage this risk, including evaluating sub-outsourcing chains and geographic concentration of data processing. DORA Article 29 — EUR-Lex

When did DORA become applicable?

DORA (Regulation 2022/2554) entered into force on 16 January 2023 and became fully applicable on 17 January 2025. Financial entities must have their ICT third-party registers, risk management frameworks, and oversight processes operational by this date.

How does DORA relate to existing outsourcing guidelines like EBA Guidelines?

DORA supersedes and consolidates previous sector-specific outsourcing guidelines (such as EBA Guidelines on Outsourcing Arrangements) into a single cross-sectoral framework. It introduces mandatory ICT third-party registers, concentration risk assessments, and the Lead Overseer framework for critical providers — requirements that go beyond the scope of prior guidelines.

What are the penalties for non-compliance with DORA?

DORA empowers national competent authorities to impose administrative penalties and remedial measures for non-compliance. For critical ICT third-party service providers, the Lead Overseer can impose periodic penalty payments of up to 1% of average daily worldwide turnover for each day of non-compliance, for up to six months. DORA Article 35 — EUR-Lex

DORA vs. Traditional Outsourcing Compliance — Comparison

DimensionPre-DORA Outsourcing GuidelinesDORA (Regulation 2022/2554)
ScopeSector-specific (EBA, EIOPA, ESMA separately)Cross-sectoral, unified framework for all financial entities
ICT Provider RegisterRecommended but not standardizedMandatory with RTS/ITS templates (Article 28)
Concentration RiskMentioned in guidance, no formal assessment requiredMandatory assessment and reporting (Article 29)
Critical Provider OversightNo direct regulatory oversight of providersLead Overseer framework with inspection powers (Articles 31–44)
Incident ReportingVaries by sectorHarmonized ICT incident reporting (Articles 17–23)
Penalties for ProvidersNone (only regulated entities penalized)Up to 1% daily worldwide turnover for CTPPs (Article 35)
Sub-outsourcingDue diligence recommendedMandatory monitoring of entire ICT supply chain