Topic starter
13/10/2026 1:21 pm
TL;DR: Financial institutions are deploying AI agents that move funds, sign transactions, and operate custody systems with limited human direction, according to Halborn, while Gartner and PwC figures point to rapid adoption and expanding exposure. Autonomy changes the problem from protecting outputs to governing action, privilege, and transaction boundaries in regulated systems.
Editorial analysis by NHI Mgmt Group, based on content published by Halborn: “Securing AI Agents In Financial Infrastructure: Halborn's Threat Models And Controls (2026)”.
By the numbers:
- According to Gartner, 40 percent of enterprise applications will embed task-specific AI agents by the end of 2026, up from less than 5 percent in 2025.
- PwC's AI Agent Survey reports that 79 percent of companies say AI agents are already being adopted in their organizations.
Key questions
Q: How should banks handle AI agents that initiate payments or data access?
A: Treat agent-driven actions as an exposure test for existing authorization design.
Q: Why do AI agents create more risk than traditional automation?
A: AI agents create more risk because they can interpret context, choose actions, and invoke tools autonomously.
Q: What breaks when an AI agent is allowed direct access to custody or payment systems?
A: The control boundary breaks when the agent can turn a legitimate identity into a live transaction path without independent validation.
Practitioner guidance
- Define proposal-versus-execution boundaries Allow agents to prepare or recommend financial actions, but require deterministic policy engines to authorise the final payment, trade, or signing step.
- Bind controls to transaction intent Validate decoded transaction fields such as destination, value, counterparty, and context before any custody or banking action is executed.
- Scope agent privileges by workflow Separate treasury, payments, trading, custody, and accounting permissions so one agent identity cannot cross business domains without explicit re-authorisation.
Bottom line: Financial AI agents change the security problem because they can act inside treasury, payments, custody, and accounting systems, not just generate outputs.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
13/10/2026 1:22 pm
Autonomous finance collapses the assumption that authorisation can be reviewed after the fact: access review processes were designed for principals whose privileges persist long enough to be observed, certified, and revoked. That assumption fails when an agent can request, use, and chain access inside a single operational loop. The implication is not merely tighter review cadence, but a rethinking of where governance must attach in the execution path.
A few things that frame the scale:
- Organisations that describe themselves as confident in their AI deployment actually experience a 72% security incident rate, compared to 33% for those who remain cautious, according to the 2026 Infrastructure Identity Survey.
- A May 2025 Gartner poll of 147 CIOs and IT leaders found that 24% had already deployed AI agents, 50% were experimenting and 17% planned to deploy by the end of 2026.
A question worth separating out:
Q: How do security teams decide how much autonomy to give a financial AI agent?
A: Teams should classify the workflow by blast radius, then match autonomy to the highest consequence the agent can trigger. Start with low-risk proposal work, then expand only when policy checks, logging, and human accountability are proven at each step. If the system can move assets, autonomy should remain tightly constrained.
👉 Read our full editorial: AI agent autonomy in finance demands new controls and governance