Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Access Custody
Governance, Ownership & Risk

Access Custody

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Governance, Ownership & Risk

Access custody is the practical ownership of an access path, including who can grant it, use it, review it, and revoke it. For sovereign services, custody matters because a platform may appear local while key operational control still sits with external parties or cross-border support teams.

What Access Custody Means in Practice

Access custody is not just permission to use an access path, it is the practical ownership of that path across its full lifecycle. That includes authority to approve it, operate it, review it, and revoke it. The concept matters most when access is delegated, shared, or geographically distributed, because “who owns it” becomes a security control question, not just an administrative label.

For sovereign or regulated environments, custody also helps distinguish local presence from real control. A service may sit in-country while approval workflows, support operations, or recovery authority still sit elsewhere. In that case, the access path is present locally, but custody is not fully local.

Why Access Custody Matters for Control and Accountability

Custody determines who can change access conditions and who is accountable when access is too broad, stale, or misused. If custody is unclear, organisations often end up with overlapping approvers, delayed revocation, or no single owner responsible for periodic review.

This is especially important for privileged access, break-glass paths, service access, and third-party support channels. Those pathways can be operationally necessary, but they also create a clear question: who can legitimately grant them, who can use them, and who can take them away when the risk profile changes?

How Access Custody Shows Up in Real Environments

Access custody is often split across teams, contracts, and tooling. An internal platform team may run the system, a security team may define policy, and an external provider may still hold technical ability to restore, troubleshoot, or bypass controls. The result is a custody gap, where no one clearly owns the access path end to end.

That gap is easy to miss in hybrid and sovereign deployments because the interface looks local while the operational authority is not. The useful test is simple: if a control fails, who can investigate, who can repair, and who can revoke the path without waiting on another organisation?

Access Custody and the Access Lifecycle

Custody should follow the lifecycle of the access path, from request and approval through activation, review, suspension, and removal. When custody is explicit, access decisions are easier to audit and revocation is easier to execute. When it is implicit, access tends to persist after the business need has changed.

Good custody also makes review meaningful. A reviewer should be able to see not just that access exists, but who owns the authority behind it, which support or administrative dependencies exist, and whether the current custodian still matches the operational reality of the system.

Risk and Threat Considerations

Weak access custody creates exposure because control of the access path can drift away from the organisation that depends on it. That increases the chance of excessive privilege, delayed revocation, and unresolved support access that outlives its need.

Failure mechanism: Custody gaps let access remain active even when the business owner, support relationship, or operating environment has changed. In the worst case, an external party or cross-border support function can still influence a supposedly local access path after local administrators believe they own it.

Impact: The result can be unauthorised persistence, slower incident containment, weaker accountability, and difficulty proving that access control is actually under domestic or organisational control where that matters.

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 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-2 — Account ManagementAccess custody depends on clear ownership, approval, and removal of access relationships.
AC-6 — Least PrivilegeCustody determines who may grant only the minimum access needed for the path.
IA-5 — Authenticator ManagementCustody includes control over the credentials or authenticators that enable the path.
Recommendation — Assign a named owner to approve, review, and revoke each access path. Limit each custodian to the minimum authority needed to manage the access path. Track and rotate the authenticators that underpin each controlled access path.
ISO/IEC 27001:2022A.5.15 — Access controlAccess custody is an access-control ownership and governance concern.
A.5.18 — Access rightsCustody governs who grants, reviews, and removes access rights over time.
Recommendation — Define ownership and approval rules for each access route and support channel. Review and revoke access rights under a clearly assigned custodian.
NIST CSF 2.0GV.OC-03 — Legal, regulatory, and contractual requirements are understood and managedSovereign access custody depends on knowing who actually holds operational authority.
Recommendation — Map contractual and operational authority for each access path to the right owner.

Practitioner Guidance

Why practitioners should care: Treat custody as an explicit control attribute, not an implied side effect of system ownership. If no named owner can approve, review, and revoke a path, the access model is incomplete even if the technical configuration looks sound.

Governance implication: For shared, outsourced, or sovereign services, define custody separately from hosting, administration, and support. That avoids the common mistake of assuming local infrastructure automatically means local control.

Practitioner takeaway: A clean custody model should answer one question without ambiguity: who has the authority to say yes, to say no, and to remove access when conditions change.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org