Financial services

What the FCA actually expects from your penetration test

Many compliance teams assume the FCA requires a penetration test. The accurate answer is more useful: for most firms the FCA doesn’t prescribe pen testing by name — but independent security testing is one of the best sources of operational resilience evidence you can have.

The rules that matter

The FCA and PRA operational resilience framework (FCA PS21/3, PRA SS1/21) requires in-scope firms to:

  • identify their important business services — those whose disruption would cause intolerable harm to clients or market integrity;
  • set an impact tolerance for each — the maximum disruption they can withstand;
  • map the people, processes, technology and third parties behind those services;
  • test, using severe but plausible scenarios, whether they can stay within tolerance;
  • keep a written self-assessment, signed off by the board.

The transition period ended on 31 March 2025. Firms are now expected to remain within their impact tolerances — not simply to have a plan to get there.

Where pen testing fits

For almost every important business service, a cyber attack is the most obvious severe but plausible scenario. Your self-assessment needs to explain why an attacker couldn’t push a service past tolerance — and independent testing is how you evidence that.

The problem is that most pen tests aren’t designed for this. They’re scoped as “test the website” or “test 40 IP addresses” and return a CVSS list nobody can connect to a business service.

How to scope a test that works as resilience evidence

  1. Start from the service, not the asset. Pick one or two important business services — client onboarding, payments, the client portal — and scope the technology that supports them end to end.
  2. Include the paths attackers actually use. Phished credentials, your Microsoft 365 tenant, a supplier connection or an exposed remote access service. An assumed-breach test from a compromised user often tells you more than another external scan.
  3. Ask “how far could they get?” The question is whether an attacker could disrupt or corrupt the service. Reports should show attack paths, not just individual findings.
  4. Translate the findings. Every significant finding should state the service affected, the plausible impact and who owns the fix.
  5. Close the loop. Retest and record that issues are fixed, so your evidence reflects the current position.

What a supervisor or auditor will look for

  • Testing proportionate to the firm’s size and the importance of the service.
  • A clear link between test scope and important business services.
  • Independence — testers who didn’t build or run the system.
  • Evidence of remediation and retest, not just a report on file.
  • Board visibility of the results.

The bottom line

You don’t need CBEST-scale red teaming to meet operational resilience expectations. You need testing that starts from your important business services, follows realistic attack paths and produces findings a board can understand. That’s a scoping decision more than a budget decision.

Frequently asked questions

Does the FCA require penetration testing?

Not by name for most firms. Firms must test their ability to stay within impact tolerances under severe but plausible scenarios, and independent testing is a strong way to evidence cyber scenarios.

How often should FCA-regulated firms pen test?

The FCA expects an up-to-date scenario-testing plan that is reviewed regularly. Set testing frequency by your risks, your important business services and any material change.

Sources & further reading

Need testing that doubles as resilience evidence?

Fixed-price testing, scoped and delivered by a senior tester, with live findings on the SMARTSEC client platform.