Why Institutional Digital Assets Require a New Operational Trust Framework

From Key Custody to Operational Trust

According to Blair Canavan, Director of Alliances for the Post Quantum Cryptography Portfolio at Thales, the conversation has moved past private key custody and into something more structural: the operational environment surrounding it.

"The real question is how institutions build the trust, governance and resilience needed to operate digital financial services securely and at scale," Canavan notes. Stablecoins and tokenised real-world assets, in his assessment, are no longer pilot projects. They are being tested for payments and treasury operations, while tokenisation is opening new pathways for issuing, managing, and transferring traditional instruments. Canavan attributes the move to business demand rather than novelty: institutions want settlement efficiency and new value-based services, while regulatory frameworks in several markets have clarified and the underlying technology has matured.

Expanding Risk Surfaces

Private key protection remains foundational. But institutions are now managing risk across the entire transaction lifecycle, including operational risk and insider risk. Policy controls and governance checks prevent any individual from holding unchecked authority. Compliance is sustained through auditability and the transparency regulators increasingly expect. Business continuity is treated as a serious consideration, with infrastructure required to recover from failures without exposing sensitive cryptographic assets to compromise.

In Canavan's framing, a complete trust framework combines five complementary capabilities:

• Security: protection of cryptographic keys and sensitive assets throughout their lifecycle.
• Governance: definition of who approves transactions, how authority is delegated, and how policies are enforced consistently across the organisation.
• Compliance: evidence, through audit records and reporting, that the controls function as designed.
• Interoperability: consistent security and operational controls across multiple blockchains, networks, and existing banking infrastructure.
• Resilience: service availability and secure recovery from failures or cyber incidents.

"The key question is no longer just whether a private key is protected, but whether the entire ecosystem around it can be trusted to operate securely, consistently and transparently," Canavan explains. Trust, in his view, cannot stop at organisational boundaries. It must extend across industry partners, platforms, and networks in a uniform way.

What Institutions Should Examine

For neobanks and incumbent banks building digital asset services, the implication is structural rather than technical. A hardware security module or a managed key vault does not constitute a trust framework. What regulators, auditors, and institutional counterparties will increasingly examine is the full stack: governance hierarchies, policy enforcement mechanisms, cross-network interoperability, and recovery procedures tested under stress.

The hidden liability, as adoption scales, is the assumption that key custody alone satisfies the compliance burden. It does not. Institutions that recognise the gap early will face fewer architectural rewrites when the regulatory perimeter tightens. Those that do not will discover, at audit or incident, that a signed transaction and a trustworthy transaction are not the same thing.