Bank of England Deputy Governor Sarah Breeden has pushed the banking sector towards a harder cyber-resilience assumption: critical systems may need to be rebuilt independently from bare metal if an AI-enabled attacker or compromised agent defeats normal controls. Reuters reported that the Bank is working with firms on deep recovery options and also assessing quantum risks to payments and clearing.

The important change is not a new prediction that AI will inevitably break a bank. It is the control standard implied by the scenario. Backups that share credentials, management planes or compromised dependencies may not provide independent recovery. Institutions therefore need tested rebuild paths, clean configuration sources, protected keys, decision rights and realistic recovery priorities.


Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury's approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don't run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab's own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer's agents.

Share this post
The link has been copied!