Law / United Kingdom

Critical third parties: fundamental rules, operational risk and resilience requirements, assurance, self-assessment and information sharing with firms

PRA Rulebook, Critical Third Parties, chs. 3 to 7, with FSMA 2000 ss. 312L and 312M

In force since .

A sector security regimes rule binding private bodies.

Enforcement body
Prudential Regulation Authority, Financial Conduct Authority and Bank of England
Instrument type
a regulation made under an act
Obligation class
Security, Governance, Reporting, Disclosure

What it requires

  • It reaches you only if HM Treasury has designated you as a critical third party under section 312L of the Financial Services and Markets Act 2000; the Critical Third Parties (Designation) Regulations 2026 (S.I. 2026/777) designate Amazon Web Services EMEA SARL, Google Cloud EMEA Limited, Microsoft Ireland Operations Limited and Oracle Corporation UK Limited from , and the duties concern the systemic third party services you provide to firms.
  • Conduct your business with integrity, due skill, care and diligence, in a prudent manner, with effective risk strategies and risk management systems, and organise and control your affairs responsibly and effectively, in respect of your systemic third party services; deal with each regulator in an open and cooperative way for all services you provide to firms (CTP Fundamental Rules 1 to 6, Rules 3.1 to 3.7).
  • Have sound, effective and comprehensive strategies, controls, processes and systems to comply with the Part, proportionate to the nature, scale and complexity of your activities (Rules 4.1, 4.2).
  • Appoint one or more individuals as the central point of contact with the regulators, notify the regulators in writing of their names, addresses and contact details, and notify changes as soon as is practicable (Rule 4.3).
  • Manage effectively the risks to your ability to deliver a systemic third party service, and identify and manage risks in your supply chain (Rules 4.4, 4.5).
  • Take reasonable steps to ensure your key nth-party providers are informed of your duties under the Part, cooperate with you in meeting them, and give the regulators access to information relevant to their oversight functions (Rule 4.6).
  • Take reasonable steps to ensure the resilience of the technology that delivers, maintains or supports a systemic third party service, with sound strategies, processes and systems for technology and cyber resilience and regular testing and exercising of them (Rule 4.7).
  • Risk-assess, record, test, verify and approve any change to a systemic third party service before you implement it (Rule 4.8).
  • Within 12 months of designation, identify and document the resources, persons and technology used to deliver each systemic third party service and their interdependencies, and update that mapping regularly (Rule 4.9).
  • Set a maximum tolerable level of disruption for each systemic third party service, and within 12 months of designation have an incident management playbook in place (Rule 4.10).
  • Have measures to respond to termination of a systemic third party service, including arrangements for its orderly and timely termination or transfer and for access to, recovery and return of each firm's assets (Rule 4.11).
  • Carry out regular scenario testing of your ability to keep each systemic third party service within its maximum tolerable level of disruption in a severe but plausible disruption, and assess your incident management playbook with a playbook exercise within 12 months of designation and at least every two years after (Rules 5.2 to 5.4).
  • Provide the regulators with an interim self-assessment within three months of designation and an annual self-assessment after, and keep each for at least three years (Rules 6.1, 6.2).
  • Have effective and secure processes to give each firm to which you provide systemic third party services sufficient and timely information, including results of testing, your annual self-assessment and the maximum tolerable level of disruption you set (Rules 7.1, 7.2).

These lines are LexLint's reading of the law's text.

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

The Critical Third Parties Part of the PRA Rulebook sets the PRA's rules for a provider of services to the financial sector that HM Treasury has designated as a critical third party, made under the power in section 312M of the Financial Services and Markets Act 2000. Section 312L of the Financial Services and Markets Act 2000 lets the Treasury designate a critical third party. Section 312M lets a relevant regulator make rules imposing duties on critical third parties.

The Treasury designated Amazon Web Services EMEA SARL, Google Cloud EMEA Limited, Microsoft Ireland Operations Limited and Oracle Corporation UK Limited as critical third parties from . Rules 3.1 to 3.5 apply to a critical third party only for its provision of systemic third party services. Rule 4.1 requires a critical third party to have sound, effective and comprehensive strategies, controls, processes and systems to comply with the Part.

Rule 4.7 requires reasonable steps to ensure the resilience of the technology that delivers, maintains or supports a systemic third party service. Rule 4.9 requires mapping of the resources used to deliver each systemic third party service within 12 months of designation. Rule 6.1 requires an interim self-assessment within three months of designation. Rule 7.1 requires effective and secure processes to give firms sufficient and timely information.

When LexLint raises it

When your app profile says your app provides financial services.

Back to the example  ·  Lint your app

Page updated .