UK financial regulators proposed cyber resilience guidance on 19 November 2026 that would cover qualifying cryptoasset firms from 25 October 2027. The Financial Conduct Authority (FCA), Prudential Regulation Authority and Bank of England say the guidance would explain how they expect firms to meet regulatory requirements, rather than create new rules.
The draft would put responsibility for cyber risk with boards and senior management, including a named senior manager. Firms would need to keep track of essential assets and dependencies, detect incidents quickly, and demonstrate that their response and recovery plans work. The regulators propose using the National Cyber Security Centre’s assessment framework to help firms judge their controls.
The consultation closes on 26 February 2027, with final guidance expected in the first half of the year. The regulators intend to use the expectations when supervising compliance with existing rules. Separately published practices for artificial intelligence and quantum computing are outside this consultation and do not set supervisory expectations.
What crypto firms already need to prepare for
The June 2026 Handbook package explains who counts as a qualifying cryptoasset firm: it is a firm with permission under Part 4A of the Financial Services and Markets Act that includes a qualifying cryptoasset activity. These activities include issuing qualifying stablecoins, safeguarding cryptoassets, operating qualifying trading platforms and arranging qualifying staking.
That same package already adds qualifying cryptoasset firms to the Handbook’s operational resilience chapter, SYSC 15A, from the October 2027 start of the new regime. The November consultation names this population rather than creating it. The June instrument also adds authorised cryptoasset firms to the material third party register rules in SUP 16.33.
The FCA’s separate final guidance on cryptoasset operational resilience gives firms a way to translate that framework into service design. For a stablecoin issuer, redemption is an example of an important service: its dependencies can include the smart contracts used to process redemptions as well as reserve custodians, banking partners handling fund flows and staff responsible for transaction validation.
Custody has a different set of dependencies. An example in the guidance maps wallets used for immediate transactions, offline storage, key management and outside suppliers. A custodian setting its tolerance for disruption can consider withdrawal volumes and how loss of wallet access during volatile markets could affect clients and related services.
The FCA distinguishes mapping and contingency planning from control over the underlying network. Where a public blockchain is outside the firm’s control, the guidance expects arrangements for disruption, not a guarantee that the network will never fail. Where a supplier cannot give enough information to assess resilience, the firm should review and, if needed, change the arrangement.
Incident reporting runs on a different timetable
Incident reporting sits on a different timetable. The FCA’s March 2026 policy statement set 18 March 2027 as the start date for final rules covering operational incident reporting, including firms already holding Part 4A permission. The reporting framework is designed to capture significant incidents against thresholds reflecting consumer, market or financial stability risks.
Most FCA solo-regulated firms in that framework will use a short standard report. A smaller group will update one enhanced form across the initial, intermediate and final phases. A firm that owes the same report to both the FCA and the Prudential Regulation Authority is expected to make one submission through the shared portal.
The March package also sets up a separate process for recording and reporting material arrangements with outside providers. In-scope firms maintain a register and generally submit it annually; notifications cover new arrangements or significant changes. That register is distinct from an incident report, which concerns an actual operational incident meeting the applicable reporting threshold.
The FCA’s authorisation timetable adds another date for crypto firms preparing for the new regime. Its application window opened on 30 September 2026 and runs to 28 February 2027. That window is separate from the cyber consultation closing two days earlier. The FCA’s preparation guidance says firms should identify gaps against the incoming requirements and agree a board-level plan assigning responsibility, resources and delivery dates. It distinguishes a new application from a variation where a firm is already authorised.
Related coverage: Aave’s response to the separate FCA DeFi consultation and UK Commons approval of crypto amendments.









