A financial institution may know which providers it pays and where its contracts are stored. Understanding how those arrangements support its operations requires a closer look at the connections between them.
Which entity uses the ICT service? Which agreement covers it? Does the direct provider depend on a subcontractor? Which functions could be affected if the service became unavailable?
Connecting these answers can help firms understand where their operational dependencies sit.
Start with the service being provided
A provider’s name alone tells us relatively little about the dependency.
The same provider may deliver several ICT services under different contractual arrangements. Those services may support different entities and functions within the organisation.
A useful starting point is therefore to identify the service, the entity using it and the arrangement through which it is provided. From there, the firm can examine the provider’s role and the functions that rely on that service.
This gives each relationship a clear context.
Understand how the contracts fit together
Contractual arrangements may include a master agreement and subsequent arrangements, such as statements of work or order forms.
Reading those documents together helps teams understand how the commercial relationship is structured and which services fall within it.
For example, a master agreement may establish the general terms of a relationship, while separate statements of work describe particular services. Looking only at the master agreement may leave important questions about service scope unanswered.
The Register provides a structure for recording these arrangements and their connections. The underlying documents remain important when reviewing the rights, obligations and service descriptions behind the records.
Follow the relevant supply chain
The organisation signing the contract may depend on other providers to deliver the service.
The Register technical standards distinguish between information about direct ICT providers and information about subcontractors that effectively underpin ICT services supporting critical or important functions, or material parts of them. The subcontractor requirement therefore has a defined scope.
Supply chains should also be considered in the context of the particular service and contractual arrangement. A subcontractor supporting one service should not automatically be treated as supporting every service delivered by the direct provider. The Register’s supply chain template links providers at this more specific level.
That distinction helps teams investigate the dependencies relevant to the service they are reviewing.
Include arrangements within the group
An ICT service may reach a financial entity through another entity in its own group.
For example, a group service company may contract with an external provider and supply services to several financial entities through internal agreements.
Understanding this structure requires visibility of both the internal arrangements and the relevant external arrangements. The Register standards include a template for connecting these contractual relationships.
This can help teams identify which entity contracts with the external provider, which entities receive the service and how the arrangements relate.
Consider a practical example
Imagine a financial entity using a hosted application to support a critical function.
It receives the service through a group service company. That company contracts with an application provider, which relies on a cloud infrastructure provider.
A review of the financial entity’s internal agreement provides one part of the picture. Connecting it with the external arrangement and the relevant supply chain can help the firm investigate the wider dependency.
The next questions become more specific. Which other entities use the same service? Do other arrangements depend on the same infrastructure provider? What information is available about continuity, recovery and alternatives?
These connections provide a starting point for assessment. The significance of the dependency still requires consideration of the circumstances and supporting evidence.
Use the connections to guide review
DORA requires firms to consider how long or complex subcontracting chains may affect their ability to monitor services supporting critical or important functions and the ability of competent authorities to supervise them.
A connected view can help teams identify where further investigation is needed and direct questions to the colleagues or counterparties best placed to answer them.
Understand the arrangement. Follow the service. Explore the dependency.