TL;DR: Oak analysis finds service account sprawl becomes a governable risk only when teams measure owner coverage, dormancy, privilege and blast radius, because discovery alone can look like growth while orphaned, shared and standing-token accounts keep access alive. Baselines must freeze denominators, or the programme will misread inventory as risk drift.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on Oak's blog post: Service account sprawl is only manageable when ownership, dormancy, privilege and blast radius are measured against fixed baselines.
Why it matters: IAM and PAM teams need measurable service account governance because inventory growth, orphaned access and standing tokens can otherwise hide behind incomplete discovery.
By the numbers:
- Oak's analysis says 109 machine identities exist for every human in the 2026 Identity Security Landscape survey of 2,930 security decision-makers.
👉 Read Oak's analysis of service account sprawl risks and measurement
Context
Service account sprawl is not just a counting problem. It is a governance gap created when accounts outlive the people, systems and integrations that originally justified them, and when discovery tools do not fully reach on-prem, homegrown or out-of-band accounts. Non-Human Identities governance matters here because the risk is cumulative: orphaned access, dormant credentials and shared secrets all become harder to unwind once they are embedded in production workflows.
A service account can be active, dormant, privileged or effectively invisible to the people responsible for it. The article's central point is that teams need a measurement model that distinguishes new discovery from actual growth, so the programme can trend risk rather than merely record inventory.
Key questions
Q: What is the best way to measure service account sprawl?
A: Measure service account sprawl by inventorying every account, then tracking owner coverage, dormancy, privileged share, and where secrets or keys are embedded in code, CI pipelines, or cloud roles. A useful measure combines count, uniqueness of purpose, and whether each account has a named owner, rotation schedule, and expiry path.
Q: Why do orphaned service accounts create a governance problem, not just an inventory problem?
A: Because inventory tells you what exists, but governance requires someone who can approve rotation, revoke access, and explain business impact. When no owner exists, the account may remain active by default, and every downstream control loses its decision point.
Q: Why do dormant service accounts remain dangerous?
A: Dormant service accounts remain dangerous because their valid authentication material can still be reused if a token, key, or certificate is found, copied, or never revoked. They often keep standing privileges, so an old account can quietly regain access to systems, APIs, or cloud resources long after the original business need has passed.
Q: How does a nested impersonation chain expand access?
A: A nested impersonation chain expands access when one identity can act as another, and that second identity can in turn impersonate more accounts or roles. Each hop inherits the declared permissions on the first identity plus any downstream rights, so a small initial trust relationship can expose broader systems, data, or administrative functions.
Technical breakdown
Why service account ownership breaks down
A service account is a machine identity used by software, pipelines or integrations rather than a person. Ownership breaks down when accounts are created directly in cloud or SaaS consoles, bypassing normal joiner-mover-leaver workflows and leaving no named approver, reviewer or retiree. Once that happens, the account may still function, but it no longer has a governance path. That is why orphaning is not just an inventory issue. It is a control failure that removes accountability from the identity itself. See the Service Account Security Guide.
Practical implication: Map every service account to a named human or team before it enters routine access review cycles.
How dormant and privileged service accounts turn into blast radius
Dormancy means an account has valid credentials but no recent use. Privilege means the account can reach sensitive systems, often with write or admin rights that were granted for convenience and never reduced. Those two conditions interact: a dormant privileged account is low-visibility, high-impact access. Blast radius is the amount of damage an identity can reach once its permissions, inheritance and transitive access are resolved. The danger is not only what the account can do directly, but what it can reach through other identities or nested roles. Read Guide to NHI Rotation Challenges.
Practical implication: Separate dormant accounts from privileged ones so the riskiest identities are disabled or scoped first.
Why nested impersonation chains and standing tokens are harder to govern
An impersonation chain occurs when one service account can assume another, which can then assume a third. The declared permissions on the first account understate its effective reach. Standing tokens create a similar problem for third-party integrations because long-lived credentials keep working after the original business need fades. In both cases, the live access path is longer than the one recorded in inventory. That makes governance dependent on usage data, scope analysis and ownership, not just static account lists.
Practical implication: Trace transitive reach and token scope before you trust the visible permission set.
Threat narrative
Attacker objective: The attacker wants durable access to sensitive systems through identities that are hard to see, hard to own and easy to reuse.
- Entry occurs when service accounts are created out of band or inherited from old integrations, so no governing workflow captures them at birth.
- Credential access persists through shared secrets, standing tokens and dormant credentials that remain valid long after business need has changed.
- Escalation follows when nested impersonation chains extend what a single account can reach beyond its declared permissions.
- Impact comes from unowned or privileged access being available to an attacker without a clear reviewer, owner or revocation path.
Breaches seen in the wild
- Dropbox Sign breach 2024: A compromised back-end service account gave attackers Dropbox Sign customer data, including API keys, OAuth tokens and MFA information.
- Kubeflow cryptomining attacks 2020: Exposed Kubeflow dashboards and a notebook's mounted Kubernetes service account let attackers run cryptominers on tens of ML clusters.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Service account sprawl is a lifecycle problem before it is a privilege problem. Accounts proliferate because creation is easy and retirement is slow, so governance fails when onboarding is treated as the only meaningful event. The practical lesson is that service account programmes need a leaver model as much as a joiner model, otherwise unused access becomes permanent by default.
Owner coverage is the control that determines whether any other metric is actionable. If no one owns an account, no one can certify it, revoke it or explain why it still exists. That makes ownership the prerequisite for every downstream decision, not just a reporting field. Practitioners should treat unresolved ownership as a risk state, not an administrative defect.
Nested impersonation creates identity blast radius that static inventories miss. The account you see is not always the access path that matters, because transitive reach can be larger than declared permissions. That is why blast radius should be measured as a first-class governance variable, especially where service accounts can assume each other or inherit through roles.
Standing tokens create a third-party accountability gap that normal review cycles rarely close. A vendor integration can keep working long after the need for it has ended, and the account may never return to a person who can answer for its use. This is why third-party access must be governed as an identity lifecycle, not as a one-time integration choice.
Discovery without a fixed denominator produces false comfort. If the baseline moves every time a hidden account is found, the programme cannot tell whether risk is growing or simply becoming visible. That is why sprawl measurement has to separate discovery from drift, or board reporting will reward inventory work and hide the underlying exposure.
From our research library:
- NHIs outnumber human identities by 25x to 50x in modern enterprises, according to the Ultimate Guide to NHIs.
- Read next: Service Account Security Guide
What this signals
Identity programmes need a separate lifecycle for machine access, not a human review process with the labels changed. Service accounts are created, inherited and abandoned differently from human accounts, so recertification that depends on memory, ownership email threads or annual campaigns will miss the highest-risk identities. The practical shift is toward usage-aware review, fixed baselines and explicit retirement criteria for non-human accounts.
Blast radius will become the board-level shorthand for service account risk. As environments accumulate nested impersonation and third-party tokens, the question is less how many accounts exist than how far a single account can reach. Programs that can explain that reach in business terms will have a better chance of getting remediation funded and sustained.
For practitioners
- Freeze the baseline denominator before trending sprawl Complete inventory across on-prem, cloud and homegrown systems first, then hold the denominator fixed so newly found accounts are reported separately from true growth.
- Assign named owners to every service account Require a human or team owner for each account, including legacy integrations, so certification, revocation and retirement all have an accountable decision-maker.
- Measure dormant and privileged accounts separately Track no-use accounts and high-privilege accounts as distinct populations, because each requires a different remediation priority and timing.
- Break apart shared credentials and standing tokens Move each consumer to its own secret or token, then scope and expire third-party access so rotation is safe and unused access can be revoked.
- Map transitive reach before you rank blast radius Trace nested impersonation chains, inherited permissions and assumed roles so the accounts with the largest effective access are fixed before lower-risk findings.
Key takeaways
- Service account sprawl is risky because accounts outlive ownership, use and business need, not because they simply exist in large numbers.
- The strongest evidence in this post is the combination of owner coverage, dormancy, privilege and transitive reach as distinct governance signals.
- Teams that freeze baselines and separate discovery from drift can prioritise the accounts that matter most instead of mistaking inventory work for risk reduction.
Related NHI Mgmt Group resources: Ultimate Guide to NHIs · Guide to NHI Rotation Challenges · Service Account Security Guide
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 and MITRE ATT&CK address the attack and risk surface, while NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-01 — Improper Offboarding | Unowned service accounts persist because retirement never happens cleanly. |
| NHI-05 — Overprivileged NHI | The article centers on excessive privilege and blast radius in service accounts. | |
| NHI-07 — Long-Lived Secrets | Standing tokens and shared credentials are a core sprawl risk in the topic. | |
| Recommendation — Track and retire service accounts with the same offboarding discipline you apply to any other identity. Reduce standing access and scope service account permissions to the minimum needed for each task. Shorten secret lifetimes and revoke tokens that stay valid beyond their business need. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | The post is about governing who and what retains access over time. |
| Recommendation — Review entitlements regularly and remove access that no longer matches the account's role. | ||
| CIS Controls v8 | CIS-5 — Account Management | Service account ownership, dormancy and retirement are account-management problems. |
| Recommendation — Maintain a complete account inventory and disable accounts that no longer have a valid purpose. | ||
| MITRE ATT&CK | TA0006; TA0008 — Credential Access; Lateral Movement | Shared secrets and impersonation chains support credential abuse and reach expansion. |
| Recommendation — Detect credential theft and chain abuse that can expand a service account's reachable systems. | ||
Key terms
- Service Account: A special-purpose account used by applications, automated tools, or services rather than a human user to interact with systems, APIs, and infrastructure. Service accounts are a primary category of NHI and one of the most frequently exploited attack vectors.
- Impersonation Chain: An impersonation chain is a sequence of identities or roles that can act on behalf of one another. It occurs when one account is allowed to assume another identity, and that assumed identity can then reach additional permissions, creating a linked path of delegated access across systems.
- Orphaned Account: An orphaned account is an identity that remains active without a clear owner or business purpose. These accounts are dangerous because they often escape review, retain unnecessary access, and provide attackers with low-friction entry points into otherwise governed environments.
- Dormant account: A dormant account is an identity that has not been used within a defined period but still retains active access. The risk is not only wasted licensing. Dormant access often becomes stale standing privilege, which makes offboarding, certification, and incident response harder to execute cleanly.
What's in the full article
Oak's full blog post covers the operational detail this post intentionally leaves for the source:
- The five-metric measurement model with definitions for each denominator and review cadence
- The risk-order remediation sequence for orphaned, privileged, dormant and third-party accounts
- The board reporting approach for turning service account findings into a single identity risk score
- The examples of how nested impersonation and shared credentials change blast radius in practice
Deepen your knowledge
NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.
Published by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org