Crypto exchanges should treat custody as a core control, not an afterthought. In strict regimes, operators need clear segregation between customer assets and business funds, independent custody arrangements, and controls that make asset movement auditable. The practical goal is to reduce counterparty misuse, protect consumers, and preserve regulatory confidence when markets experience stress or platform failures.
Custody design should separate who owns the assets from who can move them
In strict regulatory environments, custody is not just a wallet operation, it is a control boundary. Exchanges need a structure that keeps customer assets legally and operationally distinct from house funds, with transaction approval, key usage, and settlement paths designed so that a single operator cannot blur that boundary.
A practical custody model usually combines segregated wallets or accounts, documented ownership records, and independent controls over signing and release. The important test is not whether the platform can move funds quickly, but whether every movement can be attributed, justified, and reconciled to the correct pool of assets.
For exchanges that want a deeper control baseline, Crypto Exchange Identity and Key Security Guide sets out the custody and signing patterns that matter most for exchange operations.
Segregation has to be operational, not just legal
Regulators usually care about more than account labels. They want to see that customer balances are not co-mingled with working capital, that reserve and withdrawal processes are separated from treasury functions, and that exception handling cannot quietly override segregation during stress.
This is why fund segregation must extend into the control environment. Access rights, approval workflows, and ledger treatment should all reflect the same separation. If the accounting view says customer funds are isolated but the operational stack allows routine commingling, the control is weak even if the paperwork looks correct.
CryptoCurrency Security Standard Guide is useful when you want to map custody practice to key handling, storage, and operational controls that support segregation.
Auditability is the difference between compliant custody and opaque custody
Strict regimes expect exchanges to prove what happened, not simply assert it. That means maintaining a clear trail from authorization to execution, including who approved a transfer, which keys or signers were involved, what amount moved, and which customer or treasury balance was affected.
Independent custody arrangements help here because they reduce the chance that internal operators can self-approve movements or bypass review. Good auditability also depends on tamper-evident logs, reconciliation between wallet state and books, and controls that make unusual movements visible before they become losses or reporting failures.
Crypto exchange breaches is a strong reference point for understanding how signing-path weaknesses and withdrawal-path failures turn into control failures.
Risk and Threat Considerations
Custody and segregation fail most often when an exchange treats them as accounting concepts rather than security controls. The exposure is amplified under market stress, because rushed operations, manual overrides, and concentrated signing authority can let a single compromise or process failure affect both customer and house funds.
Failure mechanism: Weak separation between custody, treasury, and withdrawal authority lets an insider, compromised operator, or failed workflow move assets across the wrong pool without immediate detection.
Impact: Customer asset loss, regulatory breach, loss of audit credibility, and a much harder recovery process if the platform must later prove which balances were genuinely segregated.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, OWASP ASVS and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Custody segregation depends on restricting who can move client and house assets. |
| AU-6 — Audit Review, Analysis, and Reporting | Auditable asset movement requires reviewable logs and reconciliation evidence. | |
| Recommendation — Apply least privilege so only tightly scoped roles can approve or execute asset transfers. Review transfer logs and reconcile movements to the correct asset pool. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Custody segregation requires defined access boundaries for operational and treasury functions. |
| Recommendation — Define and enforce access boundaries between custody, treasury, and operations. | ||
| OWASP ASVS | V8 — Authorization | Transfer approval and withdrawal authorization are central to preventing unauthorized movement. |
| Recommendation — Verify that every asset movement is explicitly authorized before execution. | ||
| CIS Controls v8 | CIS-5 — Account Management | Custody operations rely on tightly governed operator accounts and approvals. |
| Recommendation — Restrict and review operational accounts that can affect custody or withdrawal flows. | ||
Practitioner Guidance
What to verify: Test whether segregation is enforced in the wallet architecture, the ledger, and the approval process, not just in policy documents. If any one of those layers allows cross-pool movement without independent review, treat the control as incomplete.
Decision rule: If the exchange cannot demonstrate end-to-end traceability for every movement of customer assets, prioritise custody redesign and reconciliations before expanding product features or speeding withdrawal operations.
Practitioner takeaway: In a strict regime, the best custody design is the one that makes misuse hard, exception handling visible, and regulatory evidence easy to produce under pressure.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org