Back to DashboardIndustriesPhase 5 · Pilots & Migrationintermediate30 min

Custody Governance & Assurance

How a digital-asset custody design is evaluated, regulated, insured, and audited — six evaluation questions with Rule G1 checks, jurisdiction-scoped regulatory control maps, and assurance boundaries.

Why this matters: Regulatory citations, clean assurance reports, and crime-insurance certificates are frequently misread as proof that a custody architecture cannot be drained. Better governance decisions require testing where policy is enforced under explicit authority assumptions, separating binding statutory rules from guidance and accounting context, and checking the exact scope and exclusions of audits and insurance.

Start here: Choose a built-in custody architecture preset and two jurisdictions side by side, apply the applicability gates, and compare quoted regulatory obligations against market-practice insurer and auditor expectations.

Practice in the Simulation

Educational scope — not legal, regulatory, or insurance advice

This module teaches how to evaluate a digital-asset custody architecture, read primary regulatory texts with their applicability gates, and interpret custody insurance, audit reports, and proof-of-reserves statements. Every regulatory, insurance, and audit cell below either cites an admitted Library document with its edition/as-of date or explicitly states “not stated”. Completing this module does not certify a deployed system or constitute legal advice.

Related Hub resources: See the Compliance page and Compliance Strategy for general frameworks; PQC Governance and Executive Quantum Impact for general SOC 2 and insurance context; and Digital Assets (LM-045) for foundational blockchain curves and HSM certification quotes (linked, not repeated).

6. Six Questions to Test a Custody Design or Vendor Claim

Use these six evaluation patterns to test a vendor’s “policy enforced in hardware” claim. Each pattern states a strong answer, acceptable alternatives, residual risks, and the Rule G1 authority check — never a one-size-fits-all mandate.

Q1

Where is the policy checked?

When a vendor claims "policy is enforced in hardware", does the signing boundary itself evaluate transaction rules, or does a host broker check policy before calling a policy-free signer?

Strong pattern: Policy rules (spend limits, allowlists, quorum thresholds) are evaluated inside the signing boundary (HSM firmware/enclave/co-signer) before producing a signature.

Acceptable alternatives: Enough indispensable threshold or multisig signers independently enforce the policy, or an on-chain verifier contract enforces it.

Residual risk: A host application or API broker sitting in front of a policy-free signer is bypassable if the host, container, or API credential is compromised.

Rule G1 check: Who can modify the policy-engine code, firmware, or configuration, and what quorum gates that change?

Cross-reference: Module A1 §5 (Control combinations & signing boundaries)

ANALYSIS · as of 2026-11-21Q1 pattern

Q1 (Where is policy checked?): Strong pattern — policy is evaluated inside the signing boundary (HSM/enclave/co-signer) before signing. Acceptable alternatives — enough indispensable threshold/multisig signers enforce it independently, or an on-chain verifier enforces it. Residual risk — a host broker sitting in front of a policy-free signer can be bypassed if compromised.

Rule G1: Rule G1 check: Who can modify the policy-engine code, firmware, or configuration, and what quorum gates that change?

Premises: Module A1 §5, DA-18.2b

Q2

Does the signer see the full transaction or only a hash?

Can the signing boundary decode the full transaction calldata and recipient, or does it blind-sign a 32-byte digest supplied by a browser or backend?

Strong pattern: The signing boundary parses the full raw transaction it signs, or verifies a decoded form cryptographically bound to the exact bytes being signed.

Acceptable alternatives: Independent verifier devices decode the raw calldata locally before co-signing; clear-signing descriptors (such as ERC-7730) display human-readable fields on a trusted screen.

Residual risk: Blind-signing a hash lets a compromised UI or frontend substitute a malicious delegatecall or approval while displaying benign details.

Rule G1 check: Who controls the transaction parser, ABI metadata, and clear-signing descriptor registry (ERC-7730 registry trust)?

Cross-reference: Module A1 §5 & W1 (Clear signing); Module B §5d (hardware-wallet PQ specialisation — optional further reading)

Q2Industry Standard (Not Regulation)

Draft ERC-7730 defines a JSON clear-signing descriptor format so hardware and software wallets can display human-readable smart-contract fields, shifting part of the trust boundary to whoever publishes, reviews, and distributes the descriptor registry.

Source: Ethereum Draft ERC-7730, Specification & Security Considerations (descriptor trust)

ANALYSIS · as of 2026-11-21Q2 pattern

Q2 (Full transaction or hash only?): Strong pattern — the signing boundary parses the full transaction it signs, or verifies a decoded form cryptographically bound to the raw transaction bytes. Acceptable alternatives — independent verifier devices decode the raw calldata before co-signing. Residual risk — blind-signing a 32-byte digest allows UI/proxy substitution.

Rule G1: Rule G1 check: Who controls the transaction parser, ABI metadata, and clear-signing descriptor registry (e.g., ERC-7730 registry trust)?

Premises: Module A1 §5, DA-20.2-erc7730

Q3

Who can change the policy, and is that change checked inside the boundary?

If an attacker cannot bypass the spending policy directly, can they lower the quorum, add their own address to the allowlist, or swap a contract module?

Strong pattern: Policy changes require the same or a higher quorum than spending, enforced inside the signing boundary with a mandatory time delay and out-of-band governance alerts.

Acceptable alternatives: On-chain timelocked governance with independent guardian veto for smart-account policy updates.

Residual risk: A single admin console user, vendor support role, or unmonitored upgrade key can silently weaken rules before initiating a transfer.

Rule G1 check: Can a contract-upgrade key, smart-account module, vendor master key, or admin role bypass the policy-change quorum?

Cross-reference: Module A2 §5h (Governance-change monitoring) & §5i (Separation of duties)

ANALYSIS · as of 2026-11-21Q3 pattern

Q3 (Policy-change governance): Strong pattern — policy changes require at least the same or a higher quorum than spending, enforced inside the signing boundary with a time delay and out-of-band alerting (Module A2 §5h, §5i). Residual risk — a single admin or vendor support role that can lower thresholds or add allowlist entries collapses spending controls.

Rule G1: Rule G1 check: Can a contract-upgrade key, smart-account module, vendor master key, or admin role bypass the policy-change quorum?

Premises: Module A1 §5, Module A2 §5h, Module A2 §5i

Q4

Are approvers’ keys in attested hardware with a trusted display?

How does the signing boundary know an approval came from a genuine, unrevoked human approver who saw the real transaction?

Strong pattern: Approver keys live in attested hardware verified by the signing boundary or an independent verifier, with approvals bound to decoded transaction content and clean revocation.

Acceptable alternatives: Independent hardware security keys plus out-of-band transaction verification on a separate device where full trusted-display hardware is not deployed.

Residual risk: Device attestation alone proves neither display correctness nor that the signed approval matches the decoded content shown to the human.

Rule G1 check: Can a single operator, IT admin, or vendor enrol a new approver device or substitute attestation root certificates?

Cross-reference: Module A1 §5 (Approver devices); Module A2 §5e (Approver revocation) & §5i (Enrolment)

ANALYSIS · as of 2026-11-21Q4 pattern

Q4 (Attested approver hardware & trusted display): Strong pattern — approver keys live in attested hardware checked by the signing boundary or an independent verifier, with approvals cryptographically bound to decoded transaction content and revocable cleanly (Module A2 §5e). Residual risk — device attestation alone proves neither display correctness nor that the approval matches the decoded content.

Rule G1: Rule G1 check: Can a single operator, IT admin, or vendor enrol a new approver device or substitute attestation root certificates?

Premises: Module A1 §5, Module A2 §5e, Module A2 §5i

Q5

How are state, replay, and expiry enforced?

What stops an attacker from replaying an old approval, rolling back a daily spend counter, or abusing a long-lived pre-signed transaction?

Strong pattern: Approvals carry fresh nonces and short expiries; replay state (monotonic counters, velocity limits) lives inside the signing boundary, in bound on-chain state, or in distributed consensus state. No long-lived pre-signed transactions.

Acceptable alternatives: Authenticated external state anchored by monotonic hardware counters or on-chain nonces when signing hardware itself is stateless.

Residual risk: A stateless HSM cannot hold durable monotonic counters without authenticated state, and host-stored counters or VM snapshots can be rolled back.

Rule G1 check: Who can reset replay counters, restore a VM snapshot to roll back rate limits, or extend approval expiry?

Cross-reference: Module A1 §5; Module A2 §5j (No rollback of counters/nonces); Module B §5d (optional further reading)

ANALYSIS · as of 2026-11-21Q5 pattern

Q5 (State, replay, and expiry): Strong pattern — approvals carry fresh nonces and short expiries, with replay counters and rate limits held inside the signing boundary, in correctly bound on-chain state, or in distributed consensus state (Module A2 §5j); no long-lived pre-signed transactions. Residual risk — a stateless HSM cannot hold durable monotonic counters without authenticated external state, and host-stored state can be rolled back.

Rule G1: Rule G1 check: Who can reset replay counters, restore a VM snapshot to roll back rate-limit state, or extend approval expiry?

Premises: Module A1 §5, Module A2 §5j

Q6

How do recovery, rotation, and time locks work?

If operational keys are lost or rotated, does the recovery path become a weaker backdoor than day-to-day spending?

Strong pattern: Time locks and veto windows are enforced inside the signing boundary or on-chain; recovery has its own independently satisfiable trigger; key rotation never bypasses the operational quorum.

Acceptable alternatives: Geographically distributed offline key-share recovery ceremonies with dual-custody physical vaults and independent witness logs.

Residual risk: An opaque vendor recovery backdoor, unmonitored guardian quorum, or unauthenticated rotation procedure undermines every operational control.

Rule G1 check: Who holds recovery shares, guardian keys, and upgrade authority, and could they collude to bypass the operational quorum?

Cross-reference: Module A2 §5e (Rotation), §5f (Recovery), §5j (Backup/DR) & §5k (Key destruction)

ANALYSIS · as of 2026-11-21Q6 pattern

Q6 (Recovery, rotation, and time locks): Strong pattern — time locks and veto windows are enforced inside the signing boundary or on-chain; recovery uses an independently satisfiable trigger (Module A2 §5f); key rotation does not bypass the signing quorum (Module A2 §5e). Residual risk — an opaque recovery backdoor or unmonitored guardian set undermines day-to-day quorum controls.

Rule G1: Rule G1 check: Who holds recovery shares, guardian keys, and upgrade authority, and could a subset collude to bypass the operational quorum?

Premises: Module A2 §5e, Module A2 §5f, Module A2 §5j, Module A2 §5k

6b. Regulatory Requirements & Jurisdiction Control Map

What custody regulations and standards actually state per jurisdiction — separating binding statutes (“shall”) from supervisory guidance (“should”), international policy, voluntary industry standards, and US accounting/permissibility context.

EU · MiCABinding Statute / Rule

Regulation (EU) 2023/1114 (MiCA) Article 75 requires CASPs providing custody and administration of crypto-assets on behalf of clients to establish a custody policy with internal rules and procedures to ensure safekeeping or control of means of access (such as cryptographic keys), segregate client holdings from the CASP’s own assets operationally and legally, and maintain a register of positions.

Source: Regulation (EU) 2023/1114 (MiCA, OJ 9 June 2023; CASP rules applicable 30 Dec 2024), Art. 75(1)–(7) & Art. 70 (safekeeping)

EU · DORABinding Statute / Rule

Regulation (EU) 2022/2554 (DORA) applies to MiCA-authorised crypto-asset service providers (Art. 2(1)(f)), requiring an ICT risk-management framework, ICT-related incident classification and reporting (Arts. 17–19), digital operational resilience testing (Arts. 24–27), and ICT third-party risk management (Arts. 28–30).

Source: Regulation (EU) 2022/2554 (DORA, applicable 17 Jan 2025), Art. 2(1)(f), Arts. 17–19, Arts. 24–30

EU · DORA RTSBinding Technical Standard (RTS)

Commission Delegated Regulation (EU) 2024/1774 (DORA ICT Risk Management RTS) requires policies on encryption and cryptographic controls (Art. 6) and cryptographic key management covering the full key lifecycle — generating, renewing, storing, backing up, archiving, retrieving, transmitting, retiring, revoking, and destroying cryptographic keys (Art. 7) — without naming a specific HSM certification scheme or algorithm.

Source: Commission Delegated Regulation (EU) 2024/1774 (OJ 25 June 2024), Arts. 6–7 (Encryption and cryptographic key management)

EU · MiCA RTS 2025/305Binding Technical Standard (RTS)

Commission Delegated Regulation (EU) 2025/305 specifies the ICT security, custody policy, private-key management, and operational-resilience disclosures that CASP applicants must submit for MiCA authorisation.

Source: Commission Delegated Regulation (EU) 2025/305 (OJ 20 April 2025), CASP authorisation ICT & custody policy requirements

EU · ESMA ReportSupervisory Guidance

ESMA’s Final Report on MiCA First-Package Draft Technical Standards (ESMA18-72330276-1634) documents the technical rationale behind CASP governance, custody-policy, and ICT-security authorisation disclosures.

Source: ESMA Final Report ESMA18-72330276-1634 (March 2024), CASP authorisation & custody-policy RTS feedback

EU · EBA GuidelinesSupervisory Guidance

EBA Final Report EBA/GL/2025/02 amends the EBA Guidelines on ICT and Security Risk Management (EBA/GL/2019/04) for payment service providers to align supervisory expectations with DORA application.

Source: EBA Final Report EBA/GL/2025/02 (2025), Alignment of PSP ICT & security guidelines with DORA

HK · SFC VATPSupervisory Guidance

Hong Kong SFC Guidelines for Virtual Asset Trading Platform Operators state that, where practicable, seeds and private keys "should" be generated offline and kept in a secure environment such as an HSM with appropriate certification (§10.8(a)), and set the licensed-platform expectation that 98% of client virtual assets "should" be stored in cold storage except under limited SFC-approved circumstances (§10.6).

Source: Hong Kong SFC Guidelines for VATP Operators (effective 1 June 2023), §10.6 (cold-storage share) & §10.8(a) (key generation/storage)

HK · SFC 25EC44Supervisory Guidance

Hong Kong SFC Circular 25EC44 (15 August 2025) sets expected minimum custody standards for licensed VATP operators, addressing senior-management accountability, cold-wallet isolation and infrastructure controls, HSM/key-management governance, transaction verification, monitoring/alerting (cross-referenced to Module A2 §5h), and third-party/supply-chain threats.

Source: Hong Kong SFC Circular 25EC44 (15 August 2025), Minimum custody standards for licensed VATPs

Dubai · VARA CustodyBinding Statute / Rule

Dubai VARA Custody Services Rulebook (Version 2) sets custody-specific governance, client-asset segregation, wallet architecture, and key-safekeeping obligations for licensed Custody VASPs without mandating FIPS 140-2/3 or Common Criteria by name.

Source: VARA Custody Services Rulebook (Version 2, May 2025), Custody governance, segregation & key safekeeping parts

Dubai · VARA TechBinding Statute / Rule

Dubai VARA Technology and Information Rulebook (Version 2) establishes cryptographic key management, access control, incident reporting, and technology-risk governance rules for licensed VASPs, and contains zero occurrences of FIPS 140 or Common Criteria.

Source: VARA Technology and Information Rulebook (Version 2, May 2025), Cryptographic controls, access & incident governance parts

NY · 23 NYCRR 500Binding Statute / Rule

NYDFS 23 NYCRR Part 500 (Amendment 2) requires covered entities to maintain a cybersecurity program, limit and review user access privileges (§500.7), enforce multi-factor authentication (§500.12), maintain audit trails (§500.6), conduct penetration testing and vulnerability assessments (§500.5), and notify the Superintendent within 72 hours of determining a covered cybersecurity event has occurred (§500.17).

Source: NYDFS 23 NYCRR Part 500 (Second Amendment, adopted 1 Nov 2023; phased compliance through Nov 2025), §§500.5, 500.6, 500.7, 500.12, 500.17

NY · 23 NYCRR 200.9Binding Statute / Rule

NYDFS 23 NYCRR § 200.9 (BitLicense) requires licensees to hold virtual currency of the same type and amount owed to customers, maintain a surety bond or trust account for customer protection, and prohibits selling, transferring, assigning, lending, hypothecating, or pledging customer assets except at the customer’s direction.

Source: N.Y. Comp. Codes R. & Regs. Tit. 23 § 200.9 (BitLicense), §200.9(a)–(c)

NY · Sept 2025 GuidanceSupervisory Guidance

NYDFS Updated Guidance on Custodial Structures for Customer Protection in the Event of Insolvency (30 September 2025, replacing the January 2023 guidance) sets supervisory expectations for Virtual Currency Entities on customer-asset segregation, separate on-chain or omnibus accounting records, sub-custodian due diligence, and clear disclosure of custody arrangements.

Source: NYDFS Industry Letter (effective 30 September 2025; supersedes 23 Jan 2023 guidance), Segregation, sub-custody due diligence & customer disclosure sections

SG · PSR 2019 (Binding)Binding Statute / Rule

Singapore Payment Services Regulations 2019 (binding subsidiary legislation) set statutory "shall" obligations for DPT service providers on safeguarding customer assets in statutory trust accounts (Regs. 18B–18C) and on security of DPT instruments, operational controls, and segregation of duties (Reg. 18G), distinct from the non-binding guidance in MAS PS-G03.

Source: Singapore Payment Services Regulations 2019 (as amended for DPT safeguarding), Regs. 18B–18C (safeguarding) & Reg. 18G (security & segregation of duties)

SG · MAS PS-G03Supervisory Guidance

MAS Guidelines PS-G03 (19 September 2024) set supervisory guidance for Digital Payment Token (DPT) service providers on customer-asset segregation in statutory trusts, private-key storage expectations (including cold-storage practices), daily reconciliations, and operational controls — issued as guidelines alongside the binding Payment Services Regulations.

Source: MAS Guidelines PS-G03 (19 September 2024), Safeguarding, private-key storage & reconciliation guidance

SG · MAS TRMSupervisory Guidance

MAS Technology Risk Management Guidelines set supervisory expectations for Singapore financial institutions on cryptographic key management lifecycle controls, dual control / split knowledge for sensitive key operations, access controls, logging, and resilience testing.

Source: MAS Technology Risk Management Guidelines (January 2021), Section 10 (Cryptography) & Section 9 (Access Control)

JP · Payment Services ActBinding Statute / Rule

Japan’s Payment Services Act (Act No. 59 of 2009, as amended) establishes registration, information security, and user-property management obligations for Cryptoasset Exchange Service Providers, requiring customer crypto-assets to be managed separately from proprietary assets using reliable methods specified by Cabinet Office Order.

Source: Japan Payment Services Act (Act No. 59 of 2009, English translation as amended 2020), Art. 63-11 (Management of User Property)

JP · Cabinet Office OrderBinding Statute / Rule

Japan’s Cabinet Office Order on Cryptoasset Exchange Service Providers (Order No. 7 of 2017, as amended) details cold-wallet segregation methods (offline management) for customer crypto-assets, requires matching proprietary crypto-assets held in cold storage for any customer assets kept in hot wallets to satisfy immediate transfer needs, and mandates external audit of segregated management.

Source: Japan Cabinet Office Order No. 7 of 2017 (English translation as amended 2021), Cold-wallet management, hot-wallet matching & audit provisions

CH · DEBA Art. 242aBinding Statute / Rule

Swiss Debt Enforcement and Bankruptcy Act (DEBA, SR 281.1) Article 242a provides for the segregation and surrender of crypto-based assets in bankruptcy where the custodian holds them in readiness for the beneficiary at all times (either individually attributed or in a community with identifiable shares).

Source: Swiss Federal Act on Debt Enforcement and Bankruptcy (DEBA, SR 281.1, status 1 Jan 2026), Art. 242a (Surrender of crypto-based assets)

CH · Banking ActBinding Statute / Rule

Swiss Federal Act on Banks and Savings Banks (Banking Act / BankG, SR 952.0) Article 16(1bis) and Article 37d establish custody-asset classification and bankruptcy segregation for crypto-based assets held by banks.

Source: Swiss Banking Act (BankG, SR 952.0, status 1 Oct 2026), Art. 16(1bis) & Art. 37d

CH · FINMA 08/2023 (Staking)Supervisory Guidance

FINMA Guidance 08/2023 addresses supervisory treatment of crypto-asset staking (insolvency segregation conditions for staked assets, validator operational risks, and risk disclosures) — it is scoped specifically to staking rather than general key-management custody rules.

Source: FINMA Guidance 08/2023: Staking (20 December 2023), Staking custody segregation & validator risk scope

International · IOSCOInternational Policy Recommendation

IOSCO Final Report FR11/2023 issues 18 policy recommendations for crypto and digital asset markets, including custody recommendations covering legal and operational segregation of client assets, safeguarding of private keys, reconciliation, and disclosure of custody and sub-custody arrangements.

Source: IOSCO Final Report FR11/2023 (November 2023), Chapter 5 — Custody & Client Asset Protection (Recommendations 12–15)

Industry · CCSS v9.0Industry Standard (Not Regulation)

The CryptoCurrency Security Standard (CCSS v9.0, published by C4) is a voluntary industry standard — not a government regulation — defining Level I–III controls across key generation, wallet architecture, key storage, key compromise policies, backups, and third-party security audits.

Source: CryptoCurrency Certification Consortium (C4) CCSS v9.0, CCSS v9.0 Control Matrix (Levels I–III)

Instrument-Type Gate: US Federal Accounting & Permissibility Context Band

SEC Staff Accounting Bulletins (SAB 121 / SAB 122) and OCC Interpretive Letters (1170 / 1184) are excluded from W11’s key-management control cells because they address financial-statement accounting or national-bank legal authority — not HSM, MPC, quorum, or key-lifecycle rules.

Context · Accounting BulletinAccounting Context (Not Key Control)

SEC Staff Accounting Bulletin No. 121 previously expressed staff views on recognizing a balance-sheet safeguarding liability for held crypto-assets, and was rescinded on 23 January 2025 by SAB 122; it was an accounting-reporting bulletin, not a cryptographic key-management rule.

Source: SEC Staff Accounting Bulletin No. 121 (rescinded 23 January 2025), Topic 5.FF (rescinded)

Context · Accounting BulletinAccounting Context (Not Key Control)

SEC Staff Accounting Bulletin No. 122 rescinds Topic 5.FF (SAB 121) and directs entities with crypto-asset safeguarding obligations to evaluate loss-contingency recognition under FASB ASC 450-20 or IAS 37 — an accounting framework rather than a custody key-management control specification.

Source: SEC Staff Accounting Bulletin No. 122 (23 January 2025), Rescission of Topic 5.FF & ASC 450-20 / IAS 37 reference

Context · Banking Permissibility LetterPermissibility Context (Not Key Control)

OCC Interpretive Letter 1170 concludes that national banks and federal savings associations have legal authority to provide cryptocurrency custody services, including holding cryptographic keys — a banking-permissibility determination rather than a key-management technical standard.

Source: OCC Interpretive Letter 1170 (22 July 2020), Legal authority conclusion for national bank crypto custody

Context · Banking Permissibility LetterPermissibility Context (Not Key Control)

OCC Interpretive Letter 1184 clarifies that national banks and federal savings associations may provide and outsource crypto-asset custody and execution services without prior supervisory non-objection, subject to safe-and-sound risk management — a permissibility text, not a technical key-control list.

Source: OCC Interpretive Letter 1184 (7 May 2025), Clarification on bank custody & sub-custodian outsourcing

NEGATIVE · as of 2026-11-21Algorithm-neutral vs architecture-neutral across held texts

Across the held custody regulations and standards (DA-18.1 through DA-18.13 and DA-18.17), texts are largely algorithm-neutral — they rarely mandate specific curves, MPC versus HSM, or post-quantum migration — but several are NOT architecture-neutral: explicit cold-storage shares (SFC §10.6, Japan Cabinet Office Order), wallet segregation / statutory trusts (MiCA Art. 75, NYDFS §200.9 & Sept 2025 guidance, Singapore PSR Regs. 18B–18C, Swiss DEBA Art. 242a), and SFC Circular 25EC44 cold-wallet isolation expectations constrain custody architecture.

Rule G1: Regulatory silence on an algorithm or architecture does not validate a design; check who holds signing, policy-update, and recovery authority under Rule G1.

Premises: DA-18.1, DA-18.2b, DA-18.3, DA-18.4a, DA-18.7, DA-18.7c, DA-18.7d, DA-18.10b, DA-18.11a, DA-18.17

Quantum-Specific Supervisory Roadmaps (Optional Further Reading — Module B §8c)

General custody rulebooks rarely specify post-quantum algorithms today. Quantum-specific supervisory roadmaps — NIST IR 8547, BIS Paper 158, the MAS Quantum Advisory, and the HKMA Fintech Promotion Blueprint — are taught in Module B §8c (optional further reading; nothing in Module C depends on Module B).

Optional · Module B §8cSupervisory Guidance

Quantum-specific transition timelines such as NIST IR 8547 (deprecating quantum-vulnerable signatures after 2030 and disallowing them after 2035) are taught in Module B §8c (optional further reading) rather than appearing in today’s general digital-asset custody rulebooks.

Source: NIST IR 8547 (Final, 27 October 2026), Transition timeline summary (cross-ref Module B §8c)

Optional · Module B §8cInternational Policy Recommendation

BIS Paper 158 (July 2025) provides a global financial-system quantum-readiness roadmap (cryptographic inventory and migration governance), covered as optional further reading in Module B §8c.

Source: BIS Paper 158 (July 2025), Quantum-readiness roadmap (cross-ref Module B §8c)

Optional · Module B §8cSupervisory Guidance

MAS Advisory on Addressing Cybersecurity Risks Associated with Quantum Computing (February 2024) addresses quantum risk governance for Singapore financial institutions, separate from MAS PS-G03 custody rules (see Module B §8c, optional further reading).

Source: MAS Quantum Advisory (20 February 2024), Quantum risk management expectations (cross-ref Module B §8c)

Optional · Module B §8cSupervisory Guidance

HKMA Fintech Promotion Blueprint (February 2026) introduces a Quantum Preparedness Index for Hong Kong banks, distinct from SFC VATP custody rules (see Module B §8c, optional further reading).

Source: HKMA Fintech Promotion Blueprint (3 February 2026), Quantum Preparedness Index (cross-ref Module B §8c)

6c. Insurance, Audit & Proof of Reserves: What They Do and Do Not Prove

Separating statutory insurance hooks from broker-reported market practice, comparing SOC 1/ISAE 3402, SOC 2, ISAE 3000 (Revised), and CCSS audits, and explaining why Proof-of-Reserves snapshots are not financial audits.

1. Custody Insurance: Statutory Hooks vs Broker-Reported Market Practice

Core teaching point: Insurance caps or transfers financial loss after a compromise — it does not reduce the cryptographic signing attack surface. No claim is made here about “typical” dollar cover limits (no primary source establishes a universal market limit).

EU · MiCA Arts. 75(8) & 67Binding Statute / Rule

MiCA Article 75(8) makes a CASP providing custody liable to clients for the loss of crypto-assets or of the means of access to them as a result of an incident attributable to the CASP, capped at the market value of the lost crypto-assets at the time the loss occurred; Article 67 sets prudential safeguard requirements met by own funds or an insurance policy meeting minimum capital or fixed-overhead floors.

Source: Regulation (EU) 2023/1114 (MiCA, OJ 9 June 2023), Art. 75(8) (custodian liability cap) & Art. 67 (prudential own funds / insurance)

HK · SFC §§10.22–10.23Supervisory Guidance

Hong Kong SFC Guidelines for VATP Operators state that licensed platform operators "should" maintain an SFC-approved compensation arrangement (insurance, bank guarantee, or funds/virtual assets held on trust) covering at least 50% of client virtual assets held in cold storage and 100% of client virtual assets held in hot and other storages.

Source: Hong Kong SFC Guidelines for VATP Operators (effective 1 June 2023), §10.22–10.23 (Compensation arrangement: 50% cold / 100% hot)

Dubai · VARA Company VI.DBinding Statute / Rule

Dubai VARA’s insurance requirements for Custody VASPs sit in the VARA Company Rulebook (Part VI.D — requiring professional indemnity, directors and officers, and commercial crime cover for virtual assets stored in hot wallets, as applicable under the rulebook), rather than inside the Custody Services Rulebook.

Source: VARA Company Rulebook (Version 2), Part VI.D (Insurance requirements)

Market Practice · Aon 2025Market Practice (Insurer / Broker)

Aon’s Financial Services Group brief (2025, market-practice broker commentary) notes that digital-asset crime and specie underwriters scrutinise wallet architecture, hot-vs-cold storage splits, multi-party signing controls, and transaction-verification practices after high-profile exchange breaches — reflecting broker-reported underwriting questions rather than regulatory mandates.

Source: Aon Financial Services Group Brief (2025, broker document), Crime & specie underwriting considerations

Market Practice · WTW 2023Market Practice (Insurer / Broker)

WTW’s industry commentary (2023, broker document) describes how financial-institution insurance markets distinguish cold-storage specie cover from hot-wallet crime and cyber cover, and highlights underwriting scrutiny of key generation, physical/logical segregation, quorum controls, insider-collusion exclusions, social-engineering/authorised-push boundaries, and hot-wallet sub-limits.

Source: WTW Industry Commentary (2023, broker document), Digital asset custody cover classes, underwriting & exclusions

2. Assurance Regimes, DORA TLPT Scoping & Proof of Reserves

Key-ceremony procedures and the evidence they generate are owned by Module A2 §5g; this section focuses strictly on what auditors and insurers request or conclude from that evidence. For long-term cryptographic evidence durability under quantum timelines, see Module B (optional further reading).

Assurance · AICPA SOC 1Assurance Standard

AICPA SOC 1 engagements report on internal controls at a service organization relevant to user entities’ internal control over financial reporting (ICFR); a Type II report covers operating effectiveness over a stated period, with system boundaries and control objectives scoped by the service organization.

Source: AICPA & CIMA SOC 1 Overview, SOC 1 ICFR scope & Type 1 / Type 2 distinction

Assurance · IAASB ISAE 3402Assurance Standard

IAASB ISAE 3402 is the international assurance standard parallel to SOC 1 for Type 1 and Type 2 reports on internal controls at a service organization relevant to user entities’ financial reporting — it does not inherently mandate cryptographic custody key-management tests unless included in the report scope.

Source: IAASB ISAE 3402 Staff Overview, Controls at a service organization (financial reporting scope)

Assurance · AICPA SOC 2Assurance Standard

AICPA SOC 2 examinations evaluate controls against the Trust Services Criteria (Security, Availability, Processing Integrity, Confidentiality, Privacy); the service organization chooses which criteria and system boundaries are in scope, so a clean SOC 2 report does not automatically verify custody signing-boundary controls.

Source: AICPA & CIMA SOC 2 Trust Services Criteria Hub, Trust Services Criteria & service-organization scoping

Assurance · ISAE 3000 (Rev.)Assurance Standard

IAASB ISAE 3000 (Revised) is an international standard for assurance engagements other than audits or reviews of historical financial information, supporting limited or reasonable assurance against any suitable criteria — it is a general assurance framework, not an "international SOC 2."

Source: IAASB ISAE 3000 (Revised), Scope & Limited vs Reasonable Assurance framework

EU · DORA TLPT RTS 2025/1190Binding Technical Standard (RTS)

Commission Delegated Regulation (EU) 2025/1190 (DORA TLPT RTS) sets the criteria under Article 2 for competent authorities to identify which financial entities must perform Threat-Led Penetration Testing (TLPT) based on impact, systemic character, and ICT-risk assessment, distinguishing CASPs from entity classes presumptively required to run TLPT under paragraph 2 (see also Recital 3).

Source: Commission Delegated Regulation (EU) 2025/1190 (OJ 8 July 2025), Art. 2 (Identification criteria) & Recital 3

PoR · PCAOB 2023 AdvisorySupervisory Guidance

The PCAOB Office of the Investor Advocate advisory (8 March 2023) warns that third-party Proof-of-Reserve (PoR) reports are not audits, lack uniform standards, and may omit complete liabilities, legal ownership rights, borrowed or encumbered assets, and whether the custodian retains control after the snapshot timestamp.

Source: PCAOB Investor Advisory (8 March 2023), Proof-of-Reserve limitations vs financial statement audits

PoR · Provisions (CCS 2015)Technical Research

Dagher et al. ("Provisions", ACM CCS 2015 / IACR ePrint 2015/1008) formalize one privacy-preserving proof-of-solvency construction combining cryptographic asset proofs and liability commitments (such as Merkle-tree or Pedersen-commitment schemes), while noting that cryptographic proofs alone cannot prevent off-ledger liabilities or collusion outside the protocol.

Source: Dagher et al., IACR ePrint 2015/1008 (ACM CCS 2015), §1 Introduction & Security Model

Regime / ArtifactWhat It CoversWhat It Does Not ProveScope Question to Ask
SOC 1 / ISAE 3402 (Type I & Type II)Internal controls at a service organization relevant to user entities’ internal control over financial reporting (ICFR). Type II covers operating effectiveness over a stated period.Does not inherently test cryptographic signing boundaries, frontend clear-signing integrity, or key-recovery quorums unless management placed them in scope.Which subservice organizations were carved out, and were signing-policy changes inside the tested ICFR boundary?
SOC 2 (AICPA Trust Services Criteria)Controls evaluated against selected AICPA Trust Services Criteria (Security, Availability, Processing Integrity, Confidentiality, Privacy) over a management-defined system boundary.A clean SOC 2 does not prove an HSM or MPC policy engine cannot be bypassed, nor does it audit client asset completeness or solvency.Did the system boundary include the transaction-builder UI, signing-service APIs, and contract-upgrade keys, or only corporate IT?
ISAE 3000 (Revised)IAASB’s general assurance standard for engagements other than historical financial audits — supports limited or reasonable assurance against any suitable criteria (not an "international SOC 2").Assurance strength depends entirely on whether the engagement was limited vs reasonable assurance and on the exact criteria selected.Was this limited or reasonable assurance, what exact criteria were tested, and who authored those criteria?
CCSS v9.0 Audit (Industry Standard)Voluntary cryptocurrency-specific security controls (Levels I–III) covering key generation, wallet architecture, key storage, backups, and compromise policies.Voluntary industry benchmark — not a regulatory licence or statutory compliance verdict, and point-in-time unless continuously maintained.Which CCSS level (I, II, or III) was assessed for each wallet tier (hot, warm, cold), and what exceptions were noted?
Proof of Reserves (e.g., Merkle Tree / Provisions)Cryptographic demonstration (one common construction: Merkle-tree liability proofs + signed asset addresses, or zero-knowledge Provisions) that someone could sign for claimed addresses at one timestamp.Per the PCAOB (8 March 2023), PoR reports are NOT audits: they may omit complete liabilities, beneficial ownership, borrowed or encumbered assets, and continuing control after the snapshot.Were off-ledger liabilities, pledged collateral, and post-snapshot key control verified by an independent financial audit?
ANALYSIS · as of 2026-11-21General limit: clean assurance reports do not prevent custody compromise

A clean SOC 1, SOC 2, ISAE 3402, ISAE 3000 (Revised), or proof-of-reserves report does not prevent custody compromise: assurance reports evaluate controls over a service-organization-chosen scope and historical period (or a single snapshot), and insurance transfers post-incident financial loss rather than shrinking the cryptographic signing attack surface.

Rule G1: Assurance scope depends on management’s system description; verify whether frontend transaction builders, signing-service APIs, upgrade keys, and recovery quorums were actually inside the tested boundary.

Premises: DA-19.4a, DA-19.4b, DA-19.5a, DA-19.5b, DA-19.5c, DA-18.16, DA-19.6

9C. Takeaways: Control × Regulatory Anchors × Market-Practice Assurance

Compact reference mapping each custody control across representative regulatory anchors (EU MiCA/DORA & HK SFC shown; compare all 8 profiles side by side in W11), insurer questions (market practice), auditor tests (market practice), and typical evidence artifacts.

Control (Module Link)EU (MiCA + DORA)HK (SFC)Insurer Asks (Market Practice)Auditor Tests (Market Practice)Example Evidence
Secure key generation & storage
Module A1 §4–§5b
DORA RTS (EU) 2024/1774 Arts. 6–7; MiCA Art. 75(3): Requires cryptographic control policies and key-lifecycle management covering generating and storing cryptographic keys, plus custody-policy rules minimizing risk of loss of means of access; names no specific HSM scheme or algorithm.SFC VATP Guidelines §10.8(a) & Circular 25EC44: Where practicable, seeds and private keys "should" be generated offline and kept in a secure environment such as an HSM with "appropriate certification" (no specific scheme named).WTW (2023, broker commentary): Asks how private keys are generated, whether cold-storage specie assets are physically/logically isolated, and what hardware/MPC boundary protects them.SOC 2 / CCSS v9.0 (scope-dependent): Tests key-generation and storage controls ONLY if included in the service organization’s system description and Trust Services Criteria scope.Witnessed key-ceremony log, HSM/MPC architecture boundary diagram, CMVP/module inventory.
Multi-party control (M-of-N / quorum)
Module A1 §5 & Module C §6 (Q1–Q4)
Not statedSFC Circular 25EC44 (15 Aug 2025): Sets expected minimum standards for transaction verification, multi-party signing controls, and senior-management accountability over custody operations.Aon (2025, broker brief): Scrutinises multi-party signing quorums, clear transaction verification, and collusion exclusions following high-profile exchange compromises.SOC 1 / ISAE 3402 & SOC 2 (Type II): Samples transaction approvals over the review period to verify configured quorum enforcement inside the declared scope.Signed policy-ruleset export, sampled quorum approval logs, negative-test rejection logs.
Segregation of client assets & keys
Module C §6b
MiCA (EU) 2023/1114 Art. 75(7) & Art. 70: CASPs providing custody shall segregate clients’ crypto-assets operationally and legally from their own holdings and maintain a register of positions.SFC VATP Guidelines §10.3–10.5: Client virtual assets should be held on trust through an associated entity, segregated from platform operator assets.WTW (2023, broker commentary): Reviews how insured client cold/hot assets are demarcated from proprietary balances and excluded exposures.SOC 1 / ISAE 3402 (ICFR): Evaluates reconciliation controls between client sub-ledgers and on-chain wallet balances relevant to financial reporting.Daily wallet-to-sub-ledger reconciliation reports, statutory trust / segregation legal memo.
Hot / warm / cold split & limits
Module A1 §5 & Module C §6b
Not statedSFC VATP Guidelines §10.6 & Circular 25EC44: 98% of client virtual assets "should" be stored in cold storage (except limited SFC-approved circumstances); Circular 25EC44 reinforces cold-wallet isolation.WTW (2023, broker commentary): Distinguishes cold-storage specie cover from hot-wallet crime/cyber sub-limits and asks for exact cold-vs-hot allocation caps.SOC 2 / ISAE 3000 (Revised): Checks adherence to declared hot-wallet sweep thresholds and cold-storage ratio controls when included in engagement criteria.Automated hot-wallet cap alerts, sweep execution logs, cold-ratio exception approvals.
Access control & MFA for key operations
Module A2 §5i
DORA (EU) 2022/2554 Art. 9 & RTS 2024/1774: Requires ICT access-control policies, least privilege, and strong authentication aligned with the ICT risk-management framework.SFC Circular 25EC44: Addresses strict access controls, privilege separation, and physical/logical restrictions on cold-wallet infrastructure.Aon (2025, broker brief): Reviews operator authentication, staff vetting, and social-engineering / authorised-push boundary conditions.SOC 2 (Security TSC): Tests quarterly user-access reviews, MFA enforcement, and privilege revocation tickets over the Type II period.Quarterly access-review sign-offs, IdP/HSM MFA configuration exports, joiner-mover-leaver logs.
Recovery of access
Module A2 §5f & Module C §6 (Q6)
MiCA Art. 75(3) & MiCA RTS (EU) 2025/305: Custody policy and authorisation disclosures must address safekeeping and recovery of means of access to client crypto-assets.SFC Circular 25EC44: Covers seed/key backup and recovery governance for licensed VATP cold-wallet infrastructure.WTW (2023, broker commentary): Examines how key-recovery shares are stored and protected against insider collusion or coercion.CCSS v9.0 / ISAE 3000 (Revised): Reviews documented recovery triggers, custodian share-custody logs, and tabletop or staging recovery drill records.Tamper-evident vault seal logs, staging recovery drill report, guardian roster.
Backup, disaster recovery & BCP
Module A2 §5j
DORA Art. 11–12 & DORA RTS (EU) 2024/1774 Art. 7: Requires ICT business continuity, backup/restoration policies, and key-lifecycle rules covering backing up, archiving, and retrieving cryptographic keys.SFC VATP Guidelines §10.8 & Circular 25EC44: Expects secure, geographically separated backups of seeds/keys and operational resilience procedures.Aon (2025) / WTW (2023): Not stated in this identified source (does not mean the market does not ask).SOC 2 (Availability TSC): Tests backup integrity checks and disaster-recovery test evidence when Availability is in scope.Annual DR failover report, encrypted backup checksum verification logs.
Key rotation & revocation
Module A2 §5e
DORA RTS (EU) 2024/1774 Art. 7: Explicitly covers renewing, retiring, and revoking cryptographic keys within the documented key-management lifecycle.Not statedAon (2025) / WTW (2023): Not stated in this identified source (does not mean the market does not ask).SOC 2 / CCSS v9.0: Tests timely de-enrolment of departed approvers and documented key-rotation tickets.Approver revocation timestamps, rotation ceremony tickets, updated quorum manifests.
Key destruction
Module A2 §5k
DORA RTS (EU) 2024/1774 Art. 7: Explicitly lists "destroying" cryptographic keys among the required key-lifecycle management controls.Not statedAon (2025) / WTW (2023): Not stated in this identified source (does not mean the market does not ask).CCSS v9.0 / ISAE 3000 (Revised): Verifies witnessed media-sanitization / HSM zeroisation certificates for retired keys.Dual-signed HSM zeroisation log, physical media destruction certificate.
Third-party / sub-custodian & ICT risk
Module A1 §5 (Vendor patterns)
DORA Arts. 28–30; MiCA Art. 75(9): Sets binding ICT third-party risk governance, contractual clauses, and register obligations; MiCA restricts sub-custody to authorised CASPs.SFC Circular 25EC44 (15 Aug 2025): Highlights third-party and supply-chain threat controls for wallet infrastructure and service providers.Aon (2025, broker brief): Evaluates supply-chain and third-party wallet-interface dependencies highlighted by recent exchange breaches.SOC 1 / ISAE 3402 (Carve-out / CUECs): Checks Complementary Subservice Organization Controls (CSOCs) and vendor due-diligence reviews.Sub-custodian SOC/ISAE bridge letters, annual vendor risk review, CSOC mapping.
Audit trail, logging, monitoring & ceremonies
Module A2 §5g & §5h
MiCA RTS (EU) 2025/305 & DORA Arts. 10–11: Requires anomaly detection, logging, and documented custody operational procedures in authorisation filings; specific key-ceremony scripts are not prescribed.SFC Circular 25EC44: Sets monitoring, alerting, and transaction-verification expectations (mapped to Module A2 §5h).WTW (2023, broker commentary): Asks for documented key ceremonies, chain-of-custody logs, and real-time anomaly monitoring.ISAE 3000 (Revised) / SOC 2: Inspects ceremony witness evidence (procedures taught in Module A2 §5g) and log immutability over the review period.Witnessed ceremony attestation pack, SIEM governance-alert runbooks, immutable log hashes.
Incident reporting & resilience testing
Module C §6b & §6c
DORA Arts. 17–19, 24–27 & TLPT RTS (EU) 2025/1190 Art. 2: Requires major ICT incident classification/reporting and periodic resilience testing; TLPT applies only where designated by a competent authority under RTS Art. 2 criteria.SFC VATP Guidelines §§10.22–10.23 & Circular 25EC44: Sets compensation-arrangement expectations (50% cold / 100% hot "should") alongside ongoing security reviews and incident reporting to the SFC.Aon (2025, broker brief): Reviews recent penetration tests, breach-response readiness, and loss-history disclosures during renewal underwriting.PCAOB (2023) & SOC 2 / Pen-test: Reviews remediation of pen-test findings; PCAOB warns Proof-of-Reserve snapshots are NOT audits and do not replace assurance engagements.Third-party pen-test remediation report, 72-hour incident playbook drill record.

Check your understanding

55 questions on Custody Governance & Assurance, each with its answer and the reason.

Take the quiz

Next step

Explore the Compliance Directory

Cross-check jurisdiction-scoped custody obligations alongside broader regulatory frameworks and deadlines.

Production Tool Capabilities & Verification Checklist

Capabilities to require in your production tools:

  • Structured custody-design evaluation across all six signing-boundary questions (Q1–Q6) with explicit Rule G1 authority assumptions for policy edits, approver enrolment, replay counters, and recovery.
  • Jurisdiction-scoped regulatory mapping that applies entity/licence applicability gates first, distinguishes binding statutory verbs ("shall") from guidance ("should"), and separates accounting/permissibility texts into a context band.
  • Independent scoping review of custody insurance policies (cold specie vs hot crime sub-limits and exclusions), SOC 1/ISAE 3402, SOC 2, ISAE 3000 (Revised), and proof-of-reserves boundaries.

How to evaluate in your environment

Review primary regulatory texts and assurance system descriptions against your actual signing boundary, confirming whether frontend transaction builders, policy updates, and recovery quorums were inside the tested scope.

Production evidence to collect

Jurisdiction applicability memo, SOC/ISAE system-description boundary review, policy-change quorum evidence, and insurance exclusion schedule review.

Completing this Hub module and its browser-based sample exercises teaches the technical and governance decision criteria for your role; it does not test, validate, or certify your deployed production systems.

Record evidence for your environment

Identify the tested build and configuration. Use reference IDs for observations. For a proposed exclusion, record the system boundary or rule and why it excludes this build.

Structured custody-design evaluation across all six signing-boundary questions (Q1–Q6) with explicit Rule G1 authority assumptions for policy edits, approver enrolment, replay counters, and recovery.
Jurisdiction-scoped regulatory mapping that applies entity/licence applicability gates first, distinguishes binding statutory verbs ("shall") from guidance ("should"), and separates accounting/permissibility texts into a context band.
Independent scoping review of custody insurance policies (cold specie vs hot crime sub-limits and exclusions), SOC 1/ISAE 3402, SOC 2, ISAE 3000 (Revised), and proof-of-reserves boundaries.

Evidence missing. 0 of 3 requirements have a reference or scope rationale.

Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.