Pillar IV: ICT Third-Party Risk Management
42

Chapter V — Managing of ICT third-party risk

Section II — Oversight framework for critical ICT third-party service providers

Follow-up by competent authorities

follow-upcompetent-authoritiesrecommendationsoversight

Summary

Creates the enforcement bridge between the oversight framework and financial entity supervision. When a critical provider fails to comply with the Lead Overseer's recommendations, competent authorities must take supervisory action at the entity level, potentially requiring financial entities to reduce or terminate their dependency on the non-compliant provider.

Key Requirements

  1. 1

    Competent authorities must act on Lead Overseer findings affecting their supervised entities

  2. 2

    May require entities to implement contingency measures or exit plans

  3. 3

    May require entities to suspend or terminate arrangements with non-compliant providers

  4. 4

    Must coordinate response with the Lead Overseer and other NCAs

  5. 5

    Financial entities must demonstrate adequate vendor risk management in response

Detailed Analysis

Article 42 is the enforcement keystone of the entire oversight framework. Since the Lead Overseer cannot directly impose binding orders or fines on critical ICT third-party providers (which are not financial entities), Article 42 creates an indirect enforcement mechanism through the financial entities that depend on these providers.

When the Lead Overseer identifies serious deficiencies at a critical provider or finds that a provider has failed to comply with recommendations, it communicates its findings to the relevant national competent authorities. Those authorities must then consider what supervisory action to take at the entity level — that is, against the financial entities that use the non-compliant provider's services.

The range of supervisory actions is significant. Competent authorities may require financial entities to activate contingency plans, accelerate exit strategies, implement additional risk mitigation measures, or in extreme cases, suspend or terminate their arrangements with the non-compliant critical provider. This creates a powerful economic incentive for critical providers to cooperate with the oversight framework — non-compliance risks the loss of their financial sector client base.

For financial entities, Article 42 underscores the importance of maintaining robust exit strategies and contingency plans for critical third-party arrangements, as required by Article 30. An entity that has not prepared for the possibility of being required to terminate a critical provider relationship could face severe operational disruption if this article is invoked. Prudent institutions maintain tested exit plans, identified alternative providers, and sufficient internal capabilities to bridge any transition period. Auditors assessing compliance should verify that entities' contingency plans are realistic, tested, and capable of execution within reasonable timeframes.

Ready to automate compliance with Article 42?

Valendir maps every DORA requirement to actionable controls, evidence, and workflows.

Automate with Valendir