Cryptocurrency custody is the control, storage, and safeguarding of digital assets and the keys that unlock them. It includes technical controls, access governance, recovery processes, and operational responsibility. Poor custody design can turn a single compromise into irreversible asset loss.
Expanded Definition
Cryptocurrency custody is the governed control of digital assets and the private keys, recovery secrets, or signing authority that make those assets movable. In NHI and agentic security contexts, custody is not just storage. It is the full operational model for who can create, approve, rotate, recover, and revoke access to assets held on behalf of an organisation or client.
Definitions vary across vendors, especially around whether custody includes transaction policy enforcement, multisignature quorum design, and external key management. The clearest practical boundary is that custody must answer who is trusted to sign, under what conditions, and how loss, compromise, or insider misuse is contained. That makes it closely related to control governance in the NIST Cybersecurity Framework 2.0, even when the underlying asset is blockchain-native rather than a conventional secret.
Ultimate Guide to NHIs treats custody as part of the broader problem of safeguarding machine-held authority, because a key that can move value behaves like any other high-risk NHI credential. The most common misapplication is treating custody as a simple wallet-hosting choice, which occurs when teams focus on where keys live instead of how signing authority is governed.
Examples and Use Cases
Implementing cryptocurrency custody rigorously often introduces operational friction, requiring organisations to weigh faster settlement and self-sovereign control against approval latency, recovery complexity, and insider-risk reduction.
- Institutional treasury custody where a finance team uses separated approval roles, threshold signing, and documented recovery procedures to prevent one compromised administrator from moving funds.
- Exchange or brokerage custody where customer assets are isolated from operating funds, with strict key escrow, withdrawal policy checks, and tamper-evident audit logs.
- Protocol or DAO treasury custody where governance tokens or reserves are held under a multisignature policy that requires multiple independent approvers before execution.
- Managed service custody where a third party holds signing keys, but the client retains policy oversight, periodic attestations, and offboarding requirements for emergency transfer.
- Incident recovery custody where lost access is restored through predefined quorum rules instead of ad hoc key sharing, reducing the chance of unauthorized emergency action.
These patterns align with the broader identity-governance concerns described in Ultimate Guide to NHIs and with the access-control logic expected in NIST Cybersecurity Framework 2.0. In practice, custody decisions are often shaped by regulation, auditability, and whether the organisation can survive a single signer compromise without catastrophic loss.
Why It Matters in NHI Security
Cryptocurrency custody matters because the private key is a non-human credential with irreversible blast radius. If the control plane is weak, a stolen token, leaked signing secret, or overprivileged automation path can move assets instantly, leaving almost no recovery window. That is why custody belongs in the same governance conversation as secrets management, privileged access management, and Zero Trust Architecture.
NHI Management Group notes that 79% of organisations have experienced secrets leaks, and 77% of those incidents caused tangible damage, which shows how quickly weak credential governance turns into business loss. The same lesson applies to custody: once signing authority is exposed, the issue is no longer theoretical, and the response must include rotation, revocation, and forensic review. The Ultimate Guide to NHIs also reports that only 5.7% of organisations have full visibility into their service accounts, a reminder that hidden machine-held authority is usually discovered too late.
Practitioners should map custody controls to the governance and recovery expectations in the NIST Cybersecurity Framework 2.0, especially where key authority is split across humans, software agents, and external providers. Organisations typically encounter the severity of custody failures only after a theft, signing abuse, or failed recovery event, at which point the term becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207), NIST SP 800-63 and NIST AI RMF set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 | Custody depends on secure secret handling and key protection, which maps to NHI secret-management risk. |
| NIST CSF 2.0 | PR.AA | Identity and access governance supports controlled authority over asset signing and recovery. |
| NIST Zero Trust (SP 800-207) | PA | Zero Trust requires strong policy decisions before any signing authority is exercised. |
| NIST SP 800-63 | AAL2 | Strong authentication assurance is needed for humans who approve or recover custody operations. |
| NIST AI RMF | AI governance principles apply when agents can initiate or approve custody-related actions. |
Require equivalent or stronger assurance for recovery and approval roles than for ordinary access.
