FCA and PRA cyber requirements

There is no single FCA or PRA cyber rulebook. Firms must already meet operational resilience rules, new incident and third party reporting rules apply from 18 March 2027, and the first critical third parties were designated in July 2026. The Cyber Security and Resilience Bill (CSRB) is separate and does not make banks a regulated sector.

Last updated · Precursor Security
Where this stands

Status checked : the Bill passed the House of Lords on 2 November 2026 and returns to the Commons to consider Lords amendments (no date set). On 4 November 2026 the Commons extended its carry-over, so it lapses if not passed by the end of 29 April 2027. It is not yet law. References are to HL Bill 62 (as amended on Report), so wording and numbering may still change in the final Act. This guide is general information, not legal advice.

Key points

  • FCA and PRA operational resilience rules have been fully in force since 31 March 2025.
  • New operational incident reporting applies from 18 March 2027, ordinarily within 24 hours of a firm determining a threshold is met.
  • HM Treasury designated the first four critical third parties, all large cloud providers, with effect from 13 July 2026.
  • Banking is not a NIS subsector, but a fintech or group IT company could still be regulated under the Bill.
  • FCA-regulated firms cannot insure against FCA fines.

Is there an FCA or PRA cyber rulebook?

No. Cyber security for UK financial firms sits inside wider rules on operational resilience, outsourcing, third-party risk and incident reporting, alongside UK GDPR. The Cyber Security and Resilience Bill (CSRB) is a separate regime, and it does not make banks or insurers a new regulated sector.

That means a bank's cyber obligations mostly come from the FCA Handbook and the PRA Rulebook, not from the NIS Regulations 2018. The Bill can still reach parts of a financial group, as explained below.

Which rules apply, and when?

The core operational resilience rules are already in force. New incident and third party reporting rules apply from 18 March 2027, and the critical third parties regime became operational in July 2026.

Requirement Who it reaches Status
FCA operational resilience rules (PS21/3, SYSC 15A) Banks, building societies, PRA-designated investment firms, insurers, recognised investment exchanges, enhanced scope SM&CR firms, payment and e-money institutions In force. The transition period ended on 31 March 2025
PRA operational resilience expectations (SS1/21) Banks, building societies, PRA-designated investment firms and insurers In force. The transition period ended on 31 March 2025
Critical third parties regime (PS16/24, SS6/24) Third parties designated by HM Treasury Rules in force from 1 January 2025. First designations took effect on 13 July 2026
Operational incident and third party reporting (FCA PS26/2, PRA PS7/26) See below Applies from 18 March 2027
UK GDPR Anyone processing personal data In force
Cyber Security and Resilience Bill Regulated persons only, not banks as a class Passed the Lords on 2 November 2026; not yet law

What does operational resilience require?

Firms must identify their important business services, set impact tolerances for how much disruption each can bear, map the people, technology and suppliers behind them, and test whether they can stay within tolerance in severe but plausible scenarios. A cyber attack is the most obvious of those scenarios.

In practice, supervisors expect to see:

  1. A map for each important business service, down to the systems and third parties it depends on.
  2. Scenario testing that includes cyber, such as ransomware on a core platform or the loss of a cloud provider.
  3. Self-assessment documents that the board approves and that explain vulnerabilities and remediation.
  4. Recovery plans that actually meet the tolerance, not just restore systems eventually.

A common gap is testing that stops at the firm's edge. If a key supplier would take three days to recover and your tolerance is four hours, the supplier's recovery plan is part of your problem.

What do the new incident reporting rules require?

From 18 March 2027, firms must report operational incidents that meet set thresholds, using one aligned FCA, PRA and Bank of England process. The FCA's finalised guidance says firms should report as soon as practicable and ordinarily within 24 hours of determining that a threshold is met.

Key points from PS26/2 and the FCA's FG26/3 guidance, as summarised by law firms:

  • The clock starts at determination, not at first detection. Firms should not wait for the full 24 hours.
  • Firms on enhanced reporting submit an initial report, update it when there are significant developments, and close it with a final report, usually within 30 working days of resolution.
  • Firms on standard reporting submit a single report.
  • Payment service providers keep a shorter deadline for major operational or security incidents: four hours from first detection.
  • Scope for the FCA covers all firms with a Part 4A permission, payment service providers, UK recognised investment exchanges, registered trade repositories and registered credit rating agencies.

Thresholds are set out in FG26/3. Reportability is not limited to incidents affecting an important business service, so check the thresholds directly rather than relying on summaries.

What are the new third party reporting rules?

In-scope firms must tell the FCA and PRA about new or significantly changed material third party arrangements, and submit a register of material third parties every year, from 18 March 2027.

The FCA scope for third party reporting is narrower than for incidents. It includes banks, building societies, enhanced scope SM&CR firms, designated investment firms, Solvency II firms, CASS large firms, UK recognised investment exchanges, authorised payment and e-money institutions and consolidated tape providers. The regime covers non-outsourcing arrangements as well as outsourcing.

Who are the critical third parties?

HM Treasury made the first designations under the Critical Third Parties (Designation) Regulations 2026, taking effect on 13 July 2026. Four large cloud and technology providers were designated, with reports naming entities in the Microsoft, Google, Amazon and Oracle groups.

Designated providers now face the regulators' fundamental rules, resilience requirements, testing and incident reporting duties for the services they provide to UK financial firms. Two points are often missed:

  • Firms keep their own duties. Designation of your cloud provider does not reduce your outsourcing and operational resilience obligations.
  • More designations may follow. HM Treasury has said the list is not exhaustive, though it expects only a small number of designations overall.

See critical third parties and critical suppliers for how this differs from the Bill's own critical supplier regime.

How could the Bill still reach a financial firm?

Banking and financial market infrastructure are not subsectors in Schedule 2 of the NIS Regulations 2018, and HL Bill 62 (as amended on Report) does not add them. A financial group can still be caught in three ways:

  • It provides a regulated service. A fintech or group IT company could be a relevant digital service provider or relevant managed service provider if it meets the tests, including the size test.
  • It is designated as a critical supplier. A regulator could designate a supplier to an operator of essential services under regulation 14H. See critical supplier designation notices.
  • It relies on regulated suppliers. Once commenced, HL Bill 62 would give your managed service provider or cloud provider duties to notify you after its 72-hour full notification of an incident, then to send you updates.

There is also a possible future route. Clause 66 of HL Bill 62 requires a review within 12 months of Royal Assent of whether more sectors should come into scope, including all critical national infrastructure. Financial market infrastructure is part of UK CNI, so watch that review.

How do the reporting deadlines compare?

A cyber incident at a regulated financial group could trigger several reports. Plan for all of them in one process.

Regime First report Who receives it
FCA/PRA operational incident rules (from March 2027) Ordinarily within 24 hours of determining a threshold is met FCA and/or PRA through one process
Payment services (major incident) Within 4 hours of detection FCA
UK GDPR personal data breach Within 72 hours of becoming aware, if reportable Information Commission (formerly the ICO)
The Bill, if a group entity is regulated Within 24 hours of awareness, full notice within 72 hours That entity's regulator, copied to the CSIRT

See incident reports under the Bill and UK GDPR for dual reporting.

Can a firm insure FCA fines?

No. GEN 6.1 of the FCA Handbook prohibits FCA-regulated firms from insuring against FCA financial penalties. See cyber insurance and the Bill for the wider position on fines.

What should firms do now?

  1. List which regimes apply to each legal entity in your group, including any entity that could be an RMSP or RDSP.
  2. Build one incident decision process that covers FCA, PRA, the Information Commission (formerly the ICO) and, where relevant, Bill notifications, with named decision-makers out of hours.
  3. Prepare your register of material third parties now, if you are in scope of the 2027 rules.
  4. Ask critical suppliers whether they expect to be regulated under the Bill, and what they will tell you after an incident.
  5. Include supplier recovery times in your impact tolerance testing.
  6. Treat Cyber Essentials as a baseline, not as evidence of meeting these rules.

For a sector view, see financial services under the Bill and does DORA apply to UK firms?.

Sources

Frequently asked questions

Not as a separate rulebook. Cyber risk is covered by the FCA and PRA operational resilience rules, outsourcing and third party risk rules, systems and controls requirements and, from 18 March 2027, new operational incident and third party reporting rules. UK GDPR also applies wherever personal data is processed, with breach reports going to the Information Commission (formerly the ICO).

Not as a sector. Banking and financial market infrastructure are not subsectors in Schedule 2 of the NIS Regulations 2018, and HL Bill 62 does not add them. A bank group could still be caught if one of its companies provides a regulated cloud or managed service, or is designated as a critical supplier to an operator of essential services.

On 18 March 2027, under FCA PS26/2 and PRA PS7/26. Firms must report operational incidents that meet set thresholds, ordinarily within 24 hours of determining that a threshold is met. Enhanced reporting firms then update and close the report, usually within 30 working days of resolution. Payment service providers keep a four-hour deadline for major incidents.

A regime letting HM Treasury designate suppliers whose failure could threaten UK financial stability or confidence. Designated firms face direct oversight by the Bank of England, PRA and FCA. The rules took effect on 1 January 2025, and the first four designations, of large cloud and technology providers, took effect on 13 July 2026.

Not FCA fines. GEN 6.1 of the FCA Handbook prohibits FCA-regulated firms from taking out insurance that indemnifies against FCA financial penalties. Whether fines under the Cyber Security and Resilience Bill or UK GDPR can be insured is untested, so firms should assume they would have to pay them.

Get ready

Know where you stand before the duties land.

Take the free readiness assessment to see how your organisation measures up against the Cyber Security and Resilience Bill, or talk to our team about a plan.