DORA: Changing an ICT Subcontractor – Notice, Objection and Exit
A critical ICT supplier plans to change a subcontractor. Learn how regulated financial entities should assess material changes, contractual notice, approval, objection and exit under DORA and EU 2025/532.
Has your cloud provider, managed services partner or other ICT supplier announced a subcontractor change? For a regulated financial entity, the change could affect cybersecurity, data location, audit rights and continuity. But not every supplier change automatically triggers the same process. This specific rule covers material changes to subcontracting arrangements for ICT services supporting critical or important functions or material parts of them.
In short: Article 5 of Commission Delegated Regulation (EU) 2025/532 requires contractual advance notice sufficiently early to assess risk and delivery capability, together with a reasonable contractual period for approval or objection. It sets no universal seven-, fourteen- or thirty-day period. Depending on the contractual mechanism, the material change may be implemented after approval or where there has been no objection by the end of that period. Timely internal decisions are essential.
Who is covered?
DORA, Regulation (EU) 2022/2554, applies to the financial entities specified in the legislation, subject to its scope and exceptions. Regulation 2025/532 supplements DORA Article 30(5) for subcontracting ICT services supporting critical or important functions. First determine whether the organisation is covered, which business function relies on the service, and whether the subcontracted work is a material part of that function. Ordinary SaaS use alone does not prove these specific rules apply.
What is a material change?
Review the substance, not merely a subcontractor's legal name. New hosting countries, data access or processing locations, chains of subcontractors, infrastructure, continuity arrangements, security controls or the ability to audit may significantly change the risk profile. An administrative name change without operational effect may be different. Record why a change is, or is not, material in relation to the specific critical service.
What do Articles 5 and 6 require?
Under Article 5(1), the supplier must give notice of intended material changes in sufficient time for the financial entity to evaluate risk exposure and contractual delivery. Article 5(2) requires a reasonable notice period in the contract for approval or objection. Article 5(3) permits implementation only after approval or no objection by the end of that period. Under Article 5(4), if the change exceeds risk tolerance, the entity must notify the supplier, object and request modifications before the period ends. Silence under the contract is not the same as a positive security assessment. No universal thirty-day period appears in this provision.
Decision matrix: seven checks before responding
| Check | Evidence to request | Decision question |
|---|---|---|
| Critical business function | Dependency map and classification | Does this service or material part qualify? |
| Contract permission | Master contract, schedules and permitted outsourcing | Is subcontracting or this particular change authorised? |
| Notice | Receipt date, proposed implementation, former and new provider | Does the contract provide adequate decision time? |
| Data and jurisdictions | Data types, locations, access and onward processing | Are privacy, jurisdiction or transfer risks increased? |
| Resilience | Recovery tests, concentration, incidents and service levels | Are continuity, SLA and fallback capabilities affected? |
| Audit rights | Contractual access, inspection and regulator rights | Will effective audit and supervision remain possible? |
| Decision record | Risk appetite, decision maker, approval or objection date | Was an effective decision communicated in time? |
Seven steps for a traceable decision
- Record notice. Save the original communication, receipt date, contract reference, proposed change and intended effective date.
- Confirm scope. Identify the financial entity, critical or important function, main ICT supplier and subcontracted component.
- Request evidence. Obtain the new party's identity, jurisdiction, data flows, security information, access and audit rights and continuity plans.
- Assess risk. Evaluate concentration, outages, cyber exposure, privacy, service performance and supervisory access against risk tolerance.
- Decide before the deadline. Have an authorised person approve, seek clarification or object and request changes before the agreed period ends.
- Notify and archive. Send the response to the proper contract party, retain delivery proof and update applicable risk and information registers.
- Monitor or activate exit. Verify implementation and controls. If a breach occurs, assess contractual termination and continuity measures before taking action.
When is termination available?
Article 6 of Regulation 2025/532 requires the contractual framework to allow the financial entity to provide for termination where the supplier implements objected-to changes despite requested modifications; implements material changes before the notice period expires without approval; or subcontracts a critical/important service not expressly permitted by contract. This does not mean every subcontractor change allows immediate cost-free termination. Review the precise contract, evidence and continuity impact, together with relevant DORA termination rights.
Two practical scenarios
A new hosting country and subcontractor
An ICT provider wants to relocate backup operation to a new subcontractor abroad. Assess data location, access, audit rights, cyber controls and recovery tests. If the risk exceeds tolerance, object and request modifications within the contractual period. Calling it a technical upgrade does not settle the risk classification.
The supplier changes before the notice period ends
A material part of a critical service is moved before the agreed period expires, without approval. Record dates and evidence, examine Article 6 and the contract's termination provisions, and safeguard alternative operations. Contract termination must not leave the critical function without continuity.
Frequently asked questions
Is thirty days' notice always required?
No. Article 5 requires a reasonable period set in the contract, not a fixed number of days. The period must enable a real assessment and response.
Does it apply to every IT subcontractor?
No. These rules are directed at relevant financial entities and subcontracting of services that support critical or important functions or their material parts.
Can the supplier proceed if we remain silent?
The contractual Article 5 process permits implementation after approval or where no objection was received by the end of the agreed period. Monitor the deadline; non-objection does not establish positive risk acceptance.
Who remains responsible for ICT risk?
The regulated financial entity remains accountable for managing its risks even where contracted providers and subcontractors perform the technical services.
Official sources and further reading
- EUR-Lex – Delegated Regulation EU 2025/532, Articles 3–6
- EUR-Lex – DORA EU 2022/2554, Articles 28–30
- Swedish Financial Supervisory Authority – ICT risks and DORA
- European Banking Authority – subcontracting RTS
- Mallbutiken – general guide to DORA ICT supplier agreements
Editorial legal review: 19 November 2026. Regulation 2025/532 has applied since 22 July 2025. General EU financial regulatory information; not a substitute for checking regulated entity status, contract wording or applicable exceptions. No product purchase is required.
Explore the topic
Business guides – contracts, HR, AI & complianceDORA and ICT provider agreements – what contractual requirements apply?
Guide to DORA's requirements for agreements with ICT providers, critical or important functions, subcontractors, SLAs, data, audit, and exit.
