EU DORA Intelligence Managerby LupaLynx
Request free validation

DORA Insights Guidance article

Critical or Important Functions Under DORA: Understanding ICT Dependencies

Trace the ICT services, contractual arrangements and providers supporting critical or important functions, and investigate shared dependencies.

Identifying a function as critical or important is a significant decision. Understanding the ICT services that support it gives that assessment practical meaning.

Which services does the function rely on? Who provides them? Through which contractual arrangements? Could a disruption affecting one provider reach several functions across the organisation?

The DORA Register of Information brings together information that can help firms investigate these questions.

What makes a function critical or important?

DORA’s definition focuses on the consequences of disruption or failure.

A function falls within the definition where its disruption would materially affect the financial entity’s financial performance or the soundness or continuity of its services and activities. The definition also covers failures that would materially affect continuing compliance with authorisation conditions or other obligations under financial services law.

The assessment therefore requires consideration of what the function does and what could happen if it stopped working properly.

A useful starting point is to ask which activities would be interrupted, what consequences could follow and how those consequences would affect the particular financial entity.

Keep the function connected to the entity

A function name alone may not provide enough context.

Different entities within a group may perform similarly named functions, while using different services, providers and arrangements. The same function may also support more than one licensed activity.

The Register standards recognise this distinction. Function identifiers are assigned to each combination of financial entity, licensed activity and function.

Preserving that context helps teams distinguish between functions that sound similar and the specific activities, entities and dependencies they need to assess.

Trace the services supporting the function

Once the function has been identified, the next step is to understand the ICT services supporting it.

The Register’s contractual arrangement information connects the entity using an ICT service with the function, service type, provider and contractual arrangement. Where an arrangement covers several services and functions, the template instructions require those combinations to be recorded with appropriate detail.

This helps a firm investigate the particular relationship behind a dependency.

For example, knowing that a provider supports an organisation is useful. Knowing which service that provider delivers to a particular entity, under which arrangement and in support of which function gives the team a more precise starting point for review.

Consider how much the function relies on each service

Services supporting the same function may have different operational significance.

A short interruption to one service might be manageable through an established workaround. Another service might be needed continuously for the function to operate.

The Register includes a field for the assessed level of reliance on an ICT service supporting a critical or important function.

Reviewing this information alongside the recorded relationships helps teams ask more focused questions. What would stop working? How quickly would the impact become significant? Is the workaround practical, available and understood by the people who would use it?

The answers require evidence and operational knowledge from the relevant teams.

Explore dependencies shared by several functions

Consider an illustrative example in which a financial entity has assessed two functions as critical or important.

Each function uses a different application. Both applications depend on services from the same ICT provider.

Looking at each function separately may leave that shared dependency less visible. Connecting the records allows the firm to investigate whether a disruption could affect both functions and whether the services depend on common infrastructure or subcontractors.

The presence of a shared provider does not establish the severity of the risk. It identifies a relationship worth examining alongside the service arrangements, available alternatives and continuity measures.

Connect the review with recovery and exit information

Understanding a dependency also involves considering what could happen if the service became unavailable or the arrangement had to end.

The Register captures function recovery objectives and service assessment information, including provider substitutability, the existence of an exit plan and the identification of alternative providers.

Those records can help teams identify where further review is needed. A recorded exit plan, for example, provides a starting point for examining whether the plan remains suitable for the service and the functions it supports.

The information becomes more useful when it can be considered together.

Bring the dependency into view

Connecting functions, ICT services, contractual arrangements and providers helps teams investigate how their operations depend on external and group services.

Identify the function. Understand its dependencies. Investigate what matters.

Official sources

Start with a clearer view of your Register.

Explore missing information, inconsistent entries and relationships that need review through a free Register validation review.

Request free validation