DORA: Outsourcing ICT does not transfer the financial entity's responsibility
Can an ICT outsourcing contract transfer our DORA accountability?
A financial entity using ICT services for its business remains responsible for its obligations under DORA and applicable financial-services law. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(1)(a) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Financial entity subject to DORA Article 2; no supplier certification or transfer of statutory responsibility is inferred. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Contractual delegation does not by itself discharge the financial entity's statutory responsibility.
- Contractual delegation does not by itself discharge the financial entity's statutory responsibility.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: The third-party strategy duty has explicit entity exceptions
Which entities must maintain the Article 28(2) strategy?
Financial entities other than Article 16(1), first-subparagraph entities and microenterprises must adopt and regularly review an ICT third-party risk strategy, including the critical/important-function ICT-services policy. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(2) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Article 2 scope plus Article 28(2) exclusions; individual and, where relevant, sub-consolidated/consolidated levels. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Do not turn the strategy exception into a blanket exemption from DORA.
- Do not turn the strategy exception into a blanket exemption from DORA.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: The information register is broader than critical-function suppliers
Can our DORA register omit non-critical ICT services?
Financial entities must maintain and update the information register for all contractual arrangements for ICT services, distinguishing critical/important-function arrangements from others. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(3), first and second subparagraphs · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Financial entities in DORA scope; entity, sub-consolidated and consolidated levels as applicable. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A list of critical vendors alone does not establish coverage of all in-scope ICT arrangements.
- A list of critical vendors alone does not establish coverage of all in-scope ICT arrangements.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Conflict assessment belongs before contracting
What conflict evidence belongs in the pre-contract ICT review?
Before entering an ICT-services contractual arrangement, the financial entity must identify and assess conflicts of interest that the arrangement may cause. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(4)(e) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
In-scope financial entity and proposed ICT arrangement; not limited in this provision to critical functions. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A signed contract alone does not show that conflicts were assessed before entry.
- A signed contract alone does not show that conflicts were assessed before entry.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Technical complexity requires competent auditors
What competence evidence is needed for a technically complex ICT audit?
For ICT contractual arrangements entailing high technical complexity, the financial entity must verify appropriate skills and knowledge of internal, external or pooled auditors. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(6), second subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Article 2 financial-entity scope; trigger is high technical complexity; separate from audit scheduling. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A generic auditor designation does not establish skills for the actual complex service.
- A generic auditor designation does not establish skills for the actual complex service.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: An exit document needs a tested and reviewed plan
What distinguishes a documented DORA exit plan from evidence of a tested plan?
For ICT services supporting critical or important functions, financial entities must have exit strategies; exit plans must be comprehensive, documented, sufficiently tested under Article 4(2), and periodically reviewed. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(8) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical/important-function ICT services, proportionate testing under Article 4(2); no invented fixed test interval. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A plan or vendor export promise is not proof that an exit test ran successfully.
- A plan or vendor export promise is not proof that an exit test ran successfully.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Concentration review includes substitutability and connected providers
What concentration evidence is needed before another critical-function ICT contract?
For envisaged ICT arrangements supporting critical or important functions, financial entities must consider difficult substitution and multiple arrangements with the same or closely connected providers, and weigh alternative solutions' costs and benefits. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 29(1) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical/important-function arrangement assessment under Article 28(4)(c); not Article 31 critical-provider designation. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Different brands or contract references do not establish independent substitutable providers.
- Different brands or contract references do not establish independent substitutable providers.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: The full ICT contract must include the service levels
What complete contract evidence should the ICT procurement file contain?
Financial-entity and ICT-provider rights and obligations must be clearly allocated in writing; the full contract includes SLAs in one written document available on paper or another downloadable, durable, accessible format. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(1) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
ICT-services contractual arrangement in DORA scope; source does not prescribe a particular file format. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A marketing SLA page alone is not the full durable contractual record.
- A marketing SLA page alone is not the full durable contractual record.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Location terms include advance change notification
Which location and change-notice terms belong in our ICT contract?
ICT contracts must state regions or countries for contracted/subcontracted service delivery and data processing, including storage, and require advance notification of envisaged location changes. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(2)(b) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All in-scope ICT-service arrangements under Article 30(2); actual location and notice performance require separate facts. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A selected cloud region does not establish the full contracted/subcontracted location boundary.
- A selected cloud region does not establish the full contracted/subcontracted location boundary.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Incident assistance cost determined beforehand
What cost and assistance terms should an ICT incident clause specify?
ICT contracts must require provider assistance for an ICT incident related to the supplied service, at no additional cost or at a cost determined ex ante. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(2)(f) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Related ICT incident and the contracted ICT service; does not make all supplier support universally free. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A general support subscription does not establish the required related-incident assistance cost terms.
- A general support subscription does not establish the required related-incident assistance cost terms.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Critical-function audit rights have a specific microenterprise alternative
Can a provider audit summary replace our critical-function contractual audit rights?
Critical/important-function ICT contracts require ongoing performance-monitoring rights with access, inspection and audit provisions. The final subparagraph permits a microenterprise financial entity to agree delegation to an independent third party appointed by the provider, with information and assurance available at any time. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(3)(e) and Article 30(3), final subparagraph (microenterprise derogation) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical/important-function ICT arrangement; include Article 30(3)(e)(ii) alternative assurance where other clients' rights are affected; microenterprise exception is specific. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A supplier certificate does not automatically replace rights; neither may the express microenterprise derogation be ignored.
- A supplier certificate does not automatically replace rights; neither may the express microenterprise derogation be ignored.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Exit clauses need an adequate transition period
What transition evidence is needed for a critical ICT exit clause?
Critical/important-function ICT contracts must include exit strategies with a mandatory adequate transition period during which services continue and migration to another provider or in-house solution is possible, consistent with complexity. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(3)(f) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical/important-function ICT services; no fixed number of transition days is specified here. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A termination right alone does not establish a transition period adequate for this service.
- A termination right alone does not establish a transition period adequate for this service.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Provider selection must assess subcontractor visibility
What subcontractor visibility should we assess before approving the ICT arrangement?
Before entering the relevant arrangement, the financial entity must assess the provider's ability to identify all subcontractors providing critical/important-function ICT services or material parts, notify/inform the entity and supply information necessary for the Article 3 assessment. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 3(1)(b) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Delegated Regulation 2025/532; financial entity deciding whether the provider may subcontract critical/important-function ICT services or material parts. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A partial supplier list does not establish the provider's ability to identify the entire relevant subcontracting scope.
- A partial supplier list does not establish the provider's ability to identify the entire relevant subcontracting scope.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Periodic reassessment of subcontracting risks
Does periodic reassessment address changes in the business environment, supported functions, ICT threats, concentration and geopolitical risks?
Financial entities using relevant subcontracted ICT services must periodically repeat the Article 3(1)(f)-(j) assessment against business-environment changes, including supported functions, ICT threats, concentration and geopolitical risks. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 3(2) read with 3(1)(f)-(j) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical/important-function ICT services or material parts; periodic duty covers the specified f-j assessments, not an invented uniform frequency. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unchanged initial onboarding assessment does not show periodic reassessment against changed conditions.
- An unchanged initial onboarding assessment does not show periodic reassessment against changed conditions.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: The contract must place continuity responsibility across the chain
What chain-continuity term is needed when a subcontractor fails?
The financial-entity/provider contract must specify that the provider ensures continuity of critical/important-function ICT services throughout the subcontractor chain if a subcontractor fails to meet its contractual obligations. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 4(1)(g) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Delegated Regulation 2025/532 Article 4 conditions; critical/important-function services; contractual obligation is distinct from demonstrated continuity. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A subcontractor's separate availability promise does not establish the provider's full chain-continuity obligation or actual continuity.
- A subcontractor's separate availability promise does not establish the provider's full chain-continuity obligation or actual continuity.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Material subcontract changes need the contractual review window
When can a material subcontracting change proceed under the agreed notice process?
The contract must provide timely information about intended material subcontracting changes and a reasonable approval/objection notice period; changes may be implemented after approval or after no objection by the end of that period. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 5(1)-(3) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical/important-function ICT services or material parts under 2025/532; timely approval may permit an earlier change; no objection is not proof of a positive approval event. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Do not invent an unconditional explicit-consent requirement or infer positive approval from silence.
- Do not invent an unconditional explicit-consent requirement or infer positive approval from silence.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Register rank identifies contractual distance
Does register rank measure supplier risk or supply-chain position?
The financial entity assigns supply-chain rank as an integer at least one: the direct provider is rank one and a subcontractor is higher than one. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 2 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
2024/2956 definitions and Article 3(2) register inclusion scope; rank indicates position, not risk quality. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Rank is not a trust score, criticality classification or evidence of provider quality.
- Rank is not a trust score, criticality classification or evidence of provider quality.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Direct-provider and subcontractor register scopes differ
Which direct providers and subcontractors belong in the register?
Register templates must include relevant information on all ICT services from direct providers, and information on all subcontractors effectively underpinning critical/important-function ICT services or material parts. Annex I B_05.02 additionally includes all ICT intra-group service providers and, where an intra-group provider uses subcontractors, at least the first extra-group subcontractor even if the service does not support a critical or important function. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 3(2); Annex I instructions for B_05.02 (ICT service supply chains) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
2024/2956 Article 3(2), subject to DORA scope; do not generalise the subcontractor limb to every downstream service irrespective of function. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A complete direct-provider list does not prove completeness of the relevant underpinning subcontractor chain. Excluding the first extra-group subcontractor behind an intra-group provider solely because the service is non-critical conflicts with Annex I B_05.02.
- Excluding the first extra-group subcontractor behind an intra-group provider solely because the service is non-critical conflicts with Annex I B_05.02.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Provider names do not replace the required legal identifiers
Which legal identifiers must support the provider register entry?
Financial entities identify ICT providers that are legal persons with a valid active LEI or EUID, both where available; for relevant registered underpinning subcontractors they ensure this through the direct provider. Individuals acting in a business capacity are excepted. Under Annex I B_05.01.0020, legal persons not established in the Union use LEI only; the 19 September 2025 corrigendum retains this restriction. Establishment and legal-person status must be established before selecting the identifier type. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 3(5)-(6); Annex I B_05.01.0020, as corrected by OJ L 90725 of 19 September 2025 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
2024/2956 Article 3(5)-(6); direct and subcontractor scope differs; do not require both identifiers where both are not available. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A trading name or an expired LEI alone does not establish the required identification; individuals have an express exception. A non-EU legal person identified only with EUID does not satisfy the LEI-only register instruction; an individual acting in a business capacity has a different permitted identifier boundary.
- A non-EU legal person identified only with EUID does not satisfy the LEI-only register instruction; an individual acting in a business capacity has a different permitted identifier boundary.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Multiple valid register values need additional rows
How should multiple valid values be represented in register templates?
Each register data element must contain a single value; when multiple values are valid for a data element, the financial entity adds one corresponding-template row for each valid value. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 4(2) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
2024/2956 Article 4(2); apply the relevant Annex template instructions and keys; no claim of regulator submission acceptance. Applicable only after the entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A comma-separated list in one data element is not the specified additional-row representation.
- A comma-separated list in one data element is not the specified additional-row representation.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Register reporting and supervisory access
What reporting and register-access evidence must the financial entity retain for its competent authority?
Financial entities report at least yearly on the number of new ICT arrangements, provider categories, contract types, services and functions, and make the full register or requested sections and necessary supervisory information available on competent-authority request. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(3), third and fourth subparagraphs · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All ICT contractual arrangements within DORA Article 28(3); no single EU-wide annual submission date is specified here. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An internal supplier list alone is not evidence of the required reporting or response.
- An internal supplier list alone is not evidence of the required reporting or response.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Notify planned critical arrangements and changed criticality
Has the planned arrangement or changed function classification been notified through the applicable supervisory process?
Financial entities inform the competent authority in a timely manner about planned ICT arrangements supporting critical or important functions and when a function becomes critical or important. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(3), fifth subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical or important functions; timely notification does not establish supervisory approval or a universal fixed deadline. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A catalogue entry or signed supplier contract is not proof of notification.
- A catalogue entry or signed supplier contract is not proof of notification.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Precontract classification, conditions and due diligence
Is the decision to contract supported by a dated classification, risk and provider-suitability assessment?
Before entering an ICT arrangement, financial entities assess critical-function support and supervisory contracting conditions, identify relevant risks including concentration, and undertake due diligence to establish prospective provider suitability. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(4)(a)-(d) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All ICT arrangements; enhanced critical-function conditions apply only where classification supports them. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A provider marketing claim or ISO badge alone does not establish this financial entity's suitability assessment.
- A provider marketing claim or ISO badge alone does not establish this financial entity's suitability assessment.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Assess appropriate information-security standards
What evidence supports the provider's use of security standards appropriate to the contracted service?
Financial entities may contract only with ICT providers complying with appropriate information-security standards; for critical or important functions they take due consideration, before concluding, of the provider's use of the most up-to-date and highest-quality standards. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(5) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All ICT contracts with the stated additional critical-function consideration; no single certification is mandated by this clause. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Naming a standard without evidence of service-specific compliance is insufficient.
- Naming a standard without evidence of service-specific compliance is insufficient.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Predetermine risk-based audit scope and frequency
Is the audit programme tied to risk, defined scope and applicable supervisory instructions?
When exercising provider access, inspection and audit rights, financial entities predetermine audit and inspection frequency and areas on a risk basis, following commonly accepted audit standards and supervisory instructions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(6), first subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Exercise of ICT-provider audit rights; no mandatory universal audit interval is imposed by this clause. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An annual audit template without a risk-based rationale is not sufficient evidence.
- An annual audit template without a risk-based rationale is not sufficient evidence.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Preserve contractual termination circumstances
Does the contract preserve termination rights for each relevant DORA circumstance?
Financial entities ensure ICT arrangements may be terminated for significant legal or contractual breach, monitored circumstances capable of altering the performance of functions, evidenced ICT-risk-management weaknesses, or impeded effective supervision. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 28(7)(a)-(d) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All ICT arrangements; the provision requires terminability, not automatic termination upon every allegation. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unverified allegation is not an established breach or automatic instruction to terminate.
- An unverified allegation is not an established breach or automatic instruction to terminate.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Consider insolvency, data recovery and foreign enforcement
Would insolvency or third-country enforcement barriers impede urgent recovery of the financial entity's data?
For critical-function ICT arrangements, financial entities consider applicable provider-insolvency law and constraints on urgent data recovery; where the provider is established in a third country they also consider Union data-protection compliance and effective enforcement there. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 29(2), second and third subparagraphs · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
ICT services supporting critical or important functions; third-country considerations depend on provider establishment. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A contractual return clause does not demonstrate enforceability or successful recovery during insolvency.
- A contractual return clause does not demonstrate enforceability or successful recovery during insolvency.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Assess complex subcontracting chains and supervision
Can the financial entity and supervisor monitor the function through the documented subcontracting chain?
Where critical-function ICT arrangements permit subcontracting, financial entities assess whether and how long or complex chains affect full monitoring of contracted functions and effective supervision by the competent authority. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 29(2), fourth subparagraph · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical or important functions and permitted subcontracting; chain length alone is not a risk score or prohibition. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A count of subcontractors does not establish monitorability or an authorised maximum depth.
- A count of subcontractors does not establish monitorability or an authorised maximum depth.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Define services and permitted subcontracting
Does the contract identify the services and any permitted critical-function subcontracting conditions?
ICT contracts include a clear and complete description of all functions and ICT services, indicating whether subcontracting of services supporting critical or important functions or material parts is permitted and the applicable conditions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(2)(a) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All ICT contracts for service description; the subcontract-permission limb is tied to critical or important functions or material parts. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A public subprocessor list does not itself establish the negotiated permission or service scope.
- A public subprocessor list does not itself establish the negotiated permission or service scope.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Contract for protected data access, recovery and return
Do the executed clauses cover data protection and accessible recovery across the specified exit events?
ICT contracts contain provisions on data availability, authenticity, integrity and confidentiality, and access, recovery and return of personal and non-personal data in an easily accessible format on provider insolvency, resolution, discontinuation or contract termination. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(2)(c)-(d) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All covered ICT contracts; documentary clauses do not prove runtime protection, completed return or deletion. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A privacy policy addressing only personal data or deletion is not the complete DORA return provision.
- A privacy policy addressing only personal data or deletion is not the complete DORA return provision.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Provide cooperation with competent and resolution authorities
Does the contract provide the required authority cooperation while preserving verification of the requesting authority?
ICT contracts oblige the provider to cooperate fully with the financial entity's competent and resolution authorities, including persons appointed by them. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(2)(g) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
All covered ICT arrangements; a clause does not itself grant an unverified caller authority to obtain data. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A caller declaring itself a regulator is not thereby authorised to receive records.
- A caller declaring itself a regulator is not thereby authorised to receive records.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Set provider participation conditions for resilience training
Are the relevant provider participation conditions documented for security awareness and resilience training?
ICT contracts state conditions for provider participation in the financial entity's security-awareness programmes and digital operational-resilience training under Article 13(6); provider inclusion is where appropriate under that provision. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(2)(i), referring to Article 13(6) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Covered ICT arrangements; contract conditions do not require every provider employee to attend every internal programme. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An unspecified obligation to train all subcontractor staff is not established by this clause.
- An unspecified obligation to train all subcontractor staff is not established by this clause.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Specify measurable critical-service levels and change reporting
Can the financial entity monitor agreed critical-service performance and receive material-change reports?
Critical-function ICT contracts include full service-level descriptions with precise quantitative and qualitative performance targets for monitoring and timely corrective action, plus notice periods and provider reporting of developments that may materially affect delivery against agreed levels. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(3)(a)-(b) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
ICT services supporting critical or important functions; no numerical availability target or universal notice period is prescribed here. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A marketing uptime claim without the contracted scope, measurements and reporting duties is insufficient.
- A marketing uptime claim without the contracted scope, measurements and reporting duties is insufficient.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Contract for implemented and tested contingency plans
Does the contract require contingency implementation and testing, and what dated evidence is available for the relevant service?
Critical-function ICT contracts require the provider to implement and test business-contingency plans and maintain security measures, tools and policies appropriate to the financial entity's regulatory framework. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(3)(c) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
ICT services supporting critical or important functions; the legal requirement alone is not evidence a test was performed or passed. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion An untested generic continuity policy does not establish the provider's tested service capability.
- An untested generic continuity policy does not establish the provider's tested service capability.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Contract for participation in applicable threat-led testing
Does the contract support provider cooperation if the financial entity is subject to an authorised TLPT exercise?
Critical-function ICT contracts oblige the provider to participate and cooperate fully in the financial entity's threat-led penetration testing as referred to in Articles 26 and 27. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 30(3)(d), referring to Articles 26 and 27 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
This contractual provision does not make every financial entity subject to mandatory TLPT or authorise any live testing; entity selection and test governance must separately be established under Articles 26 and 27. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A legal-source record or MCP discovery response is not permission to execute a penetration test.
- A legal-source record or MCP discovery response is not permission to execute a penetration test.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Apply subcontracting conditions consistently across the group
Who owns the group-wide consistency review of critical-function subcontracting conditions?
Where the regulation applies on a consolidated or sub-consolidated basis, the parent responsible for those financial statements ensures permitted critical-function subcontracting conditions are consistent across group financial entities and adequate at all relevant levels. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 2 · Operator: Parent undertaking responsible for consolidated or sub-consolidated financial statements where the regulation applies at that level; relevant group financial entities remain within DORA scope.
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Consolidated or sub-consolidated application; the stated parent undertaking has this duty and group membership is not an exemption. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A group policy alone does not establish consistent implementation in each relevant financial entity.
- A group policy alone does not establish consistent implementation in each relevant financial entity.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Assess provider ability to select and monitor subcontractors
What demonstrates the direct provider's capacity to assess and monitor its proposed subcontractors?
Before contracting for permitted critical-function subcontracting, the financial entity assesses the provider's ability to select and assess subcontractors' operational and financial abilities, including testing participation when required, and the provider's expertise and resources to monitor subcontractor ICT risk. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 3(1)(a),(e) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
ICT services supporting critical or important functions or material parts; financial-entity final responsibility is retained. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A list of subcontractor names without assessment methods or monitoring capacity is insufficient.
- A list of subcontractor names without assessment methods or monitoring capacity is insufficient.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Assess the financial entity's own monitoring capacity
Can the financial entity itself oversee the subcontracted service and assess a subcontractor failure?
Before permitting critical-function subcontracting, the financial entity assesses its own expertise and financial, human and technical resources to monitor related ICT risks, and the impact of subcontractor failure on its resilience and financial soundness. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 3(1)(f)-(g) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical or important functions or material parts; outsourcing monitoring does not remove final financial-entity responsibility. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Provider assurance alone does not establish the financial entity's own adequate monitoring resources.
- Provider assurance alone does not establish the financial entity's own adequate monitoring resources.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Flow down access, inspection and audit rights
Do subcontractor terms and the chain of contracts preserve exercisable access, inspection and audit rights?
The financial entity's contract specifies subcontractor access, inspection and audit rights for the entity and relevant competent and resolution authorities corresponding to DORA Article 30(3)(e); precontract assessment also checks granted access and inspection rights and obstacles to exercising them. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 4(1)(j), read with Article 3(1)(d),(j) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical-function subcontracting or material parts; Article 30(3)(e) and its relevant qualifications control the rights, not a new unrestricted data entitlement. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A direct-provider audit clause that is not supported through the relevant subcontract cannot alone establish flow-down.
- A direct-provider audit clause that is not supported through the relevant subcontract cannot alone establish flow-down.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Specify monitoring and reporting along the subcontract chain
Are monitoring and reporting responsibilities assigned at both contractual levels?
The direct contract requires provider monitoring of relevant subcontracted services and reporting towards the financial entity; the provider's subcontract specifies monitoring and reporting back to the provider and, where agreed, to the financial entity. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 4(1)(b),(c),(f) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical or important functions or material parts; direct subcontractor reporting to the financial entity is qualified by 'where agreed'. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Mandatory direct reporting from every subcontractor to the financial entity is not established without the agreement qualification.
- Mandatory direct reporting from every subcontractor to the financial entity is not established without the agreement qualification.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Flow down contingency and security requirements
Are the relevant contingency service levels and security requirements present in the subcontract?
The direct contract requires provider-subcontractor arrangements to contain the DORA Article 30(3)(c) business-contingency requirements with subcontractor service levels and the specified ICT security standards and additional requirements. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 4(1)(h)-(i) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical-function subcontracting or material parts; contract flow-down does not establish implementation or successful tests. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A generic promise to follow industry practice does not identify the required contingency service levels and security terms.
- A generic promise to follow industry practice does not identify the required contingency service levels and security terms.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Document the timeline for necessary contract adjustments
Is there a documented and justified plan for necessary subcontracting contract changes?
Contract changes necessary to comply with the subcontracting regulation are implemented in a timely manner and as soon as possible, and the financial entity documents the planned implementation timeline. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 4(2) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Relevant financial-entity/provider contracts for critical or important functions or material parts; no universal grace-period date is created by this clause. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A self-selected future deadline is not an exemption from timely implementation.
- A self-selected future deadline is not an exemption from timely implementation.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Preserve remedies for unacceptable subcontract changes
Do objection handling and termination clauses cover each of the specified subcontracting violations?
If an intended material subcontract change exceeds risk tolerance, the financial entity informs the provider, objects and requests modifications before the notice period ends. The contract preserves termination rights for implementation despite such objection and requested modifications, early implementation without approval, or subcontracting not explicitly permitted. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-07-22
Provision: Article 6(a)-(c), read with Article 5(4) and Article 4(1)(l) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical-function subcontracting or material parts; these are contractual remedies, not instructions for an agent to terminate a service. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred. Delegated Regulation (EU) 2025/532 entered into force on 22 July 2025.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Silence at the end of a reasonable notice period is not the same as an unresolved objection; a record does not execute termination.
- Silence at the end of a reasonable notice period is not the same as an unresolved objection; a record does not execute termination.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Review register accuracy and correct errors promptly
What review and correction evidence supports the register's accuracy and consolidation consistency?
Financial entities ensure accurate and consistent register information, review it regularly and promptly correct detected errors or discrepancies; responsible group entities ensure entity-level information is correct and consistent with consolidation, applying the stated six data-quality principles. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Article 3(3)-(4) · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Register at the relevant entity, sub-consolidated or consolidated level; schema validity alone is not complete data quality. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A technically accepted submission does not demonstrate factual accuracy, completeness or effective correction.
- A technically accepted submission does not demonstrate factual accuracy, completeness or effective correction.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Keep missing assessments distinct from recovery targets
Does the register distinguish unperformed assessments and undefined recovery objectives from assessed operational values?
The corrected function template records criticality as Yes, No or Assessment not performed, uses 9999-12-31 when its assessment is not performed, and reports RTO/RPO in hours: values below one hour as 1, and undefined objectives as 0. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Annex I B_06.01.0050, .0070, .0080 and .0090, as corrected · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Corrected function fields B_06.01.0050, .0070, .0080 and .0090; these are reporting conventions, not evidence of zero downtime or actual recovery performance. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A reported 0 for undefined RTO is not a zero-hour recovery commitment; the sentinel date is not an assessment date.
- A reported 0 for undefined RTO is not a zero-hour recovery commitment; the sentinel date is not an assessment date.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Distinguish storage and processing locations in the register
Does the reporting evidence distinguish temporary storage, data at rest and processing locations without collapsing multiple countries?
The register asks whether the ICT service foresees storage even temporarily, records data-at-rest countries when storage is Yes, and processing countries where processing is foreseen; multiple countries use additional rows and the fields have their stated applicability conditions. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Annex I B_02.02.0140-.0160 · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
B_02.02.0140 is mandatory for critical/important-function services; .0150 is mandatory if .0140 is Yes; .0160 is mandatory if the service is based on or foresees processing. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion A supplier headquarters address is not evidence of where data is stored or processed.
- A supplier headquarters address is not evidence of where data is stored or processed.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
DORA: Distinguish alternatives from an unperformed assessment
Has the alternatives assessment been performed, and is the result represented without confusing absence of assessment with absence of alternatives?
For each provider supporting a critical or important function the alternative-provider assessment is performed; corrected B_07.01.0110 distinguishes Yes, No and option 3 Assessment not performed, while additional identification information in .0120 is optional when Yes. Review implication: Compare the cited requirement with the specified documentary evidence for this decision. A source requirement does not prove that a supplier or financial entity has satisfied it.
Legal status: CONDITIONALLY_APPLICABLE — 2025-01-17
Provision: Annex I B_07.01.0110-.0120, as corrected · Operator: Financial entity within DORA Article 2, subject to exclusions and applicable Member State option; relevant contractual obligations involve its ICT provider
DORA Article 2 financial entities, with stated exclusions and any applicable Member State option; no automatic applicability to a UK-only enterprise.
Critical-function ICT-service assessment template; an available 'not performed' reporting code does not waive the assessment requirement or mean no alternatives exist. Applicable only after entity, service and function classification is established. DORA applies from 17 January 2025; no UK-only entity coverage is inferred.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-16. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Unresolved entity, territorial or function applicability Stale, superseded, incomplete or conflicting source or contract evidence Missing artefacts or dates needed for the proposed conclusion Reporting option 3 does not establish either compliance with the assessment duty or that there are no alternative providers.
- Reporting option 3 does not establish either compliance with the assessment duty or that there are no alternative providers.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice