Several contracts can lead back to the same dependency.
A financial institution may use different applications, work with several providers and maintain separate arrangements across its group. Yet those services may depend on the same provider, related companies or common infrastructure further along the supply chain.
Understanding those connections helps firms investigate where a disruption could affect more than one part of their operations.
What does DORA ask firms to consider?
Article 29 requires financial entities to consider concentration risk before entering into arrangements for ICT services supporting critical or important functions.
This includes whether a provider is difficult to replace and whether the arrangement would result in multiple contracts with the same provider or closely connected providers. Firms must also weigh the benefits and costs of alternative solutions against their business needs and digital resilience strategy.
A practical review therefore considers both the extent of the dependency and the options available if the service becomes unavailable.
Look beyond the number of contracts
Contract counts can provide a starting point, but their significance depends on what sits behind them.
Ten arrangements for services with readily available alternatives may present a different exposure from one arrangement supporting a function that cannot operate without the service.
Useful questions include which functions depend on the provider, how heavily those functions rely on its services and what would happen if several services became unavailable together.
Connecting the information helps teams investigate those questions in context.
Consider providers within the same corporate group
Different provider names do not always represent independent dependencies.
Two counterparties may belong to the same corporate group. Reviewing their recorded parent relationships can help a firm identify connections that are less apparent when contracts are considered separately.
Common ownership is a reason to investigate further. The assessment should also consider whether the providers share infrastructure, operational resources or other dependencies that could allow disruption to affect both.
The relationship identifies a question. Supporting evidence helps explain its significance.
Follow shared dependencies through the supply chain
Consider an illustrative example involving two applications used by a financial entity.
Each application has a different direct provider. Both providers rely on the same cloud infrastructure provider for the relevant services.
A review organised only by direct counterparty could overlook that shared dependency. Connecting the recorded supply chains allows the firm to investigate whether a disruption at the common provider could affect both applications.
The next questions concern the actual arrangements. Are the services hosted in separate environments? What recovery measures are available? Could both applications be affected by the same event?
A shared provider alone does not answer those questions.
Examine how realistic the alternatives are
Replacing a provider can involve more than selecting another supplier.
The Register standards recognise that substitutability may be affected by limited alternatives, technical complexity, proprietary technology, and the cost, time or risk of migrating data and workloads.
A useful review considers whether an identified alternative could support the required service and what would be needed to move to it.
For example, a potential replacement may exist, but migration could require application changes, data conversion, testing and coordination across several teams. Those practical steps matter when assessing the dependency.
Turn the findings into focused review
A connected view can help teams decide where to investigate first.
One finding might lead to a review of a provider’s recovery arrangements. Another might prompt questions about shared infrastructure, the availability of alternatives or the practicality of an exit plan.
The purpose is to understand the consequences of the dependency and the measures available to manage it.
See the shared dependency. Examine the evidence. Understand the exposure.