Topic starter
25/06/2026 1:22 am
TL;DR: Manual service account management is creating unnecessary sprawl, governance gaps, and operational risk as CI/CD, Kubernetes, and automation workloads scale, according to SSH Communications Security. The meaningful change is not just faster provisioning, but a move away from standing machine identities toward ephemeral, scoped access that better fits modern infrastructure.
Editorial analysis by NHI Mgmt Group, based on content published by SSH Communications Security: “Smarter Access for Machine Identities: PrivX PAM release”.
Key questions
Q: What breaks when service accounts keep long-lived standing access?
A: Long-lived standing access turns one intercepted credential into a reusable credential for lateral movement and persistence.
Q: Why do ephemeral nodes and just-in-time access reduce risk for CI/CD and engineering workflows?
A: Ephemeral nodes and just-in-time access reduce standing exposure by making access temporary, task scoped, and automatically withdrawn when the job ends.
Q: How do teams know if machine identity governance is actually working?
A: Look for evidence that each service account has a current owner, a narrow purpose, a short credential lifetime, and a clear retirement path.
Practitioner guidance
- Replace persistent service accounts with task-scoped access Map CI/CD runners, automation scripts, and Kubernetes workloads that still rely on manually created accounts, then migrate them to temporary identities issued only for the job duration.
- Bind privileged access to external identity assertions Use JWT or OIDC-backed assertions as the trust input for short-lived machine access so the local account no longer becomes the primary control object.
- Separate role administration from role scope Allow teams to manage roles only inside clearly bounded groups, and review those boundaries separately from the entitlements granted within them.
Bottom line: The core risk is not automation itself but persistent machine identities that outlive the workflows they support.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 10:44 am
Ephemeral machine access is becoming the default governance model for scaled automation: Persistent service accounts no longer match the runtime shape of CI/CD, Kubernetes, and API-driven operations. When identities exist only for a task window, governance has to follow issuance and teardown instead of assuming long-lived account stewardship. The programme implication is that machine access should be governed as a lifecycle event, not a static record.
A few things that frame the scale:
- NHIs outnumber human identities by 25x to 50x in modern enterprises, according to the Ultimate Guide to NHIs.
- 59% of compromised machines in a major 2025 supply chain attack were CI/CD runners rather than personal workstations, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: When should organisations prefer federated access over local machine accounts?
A: Organisations should prefer federated access when the workload or operator already trusts an external identity provider and the local account would only duplicate that trust. In those cases, federation reduces account sprawl, preserves approval workflows, and keeps governance attached to the upstream identity system.
👉 Read our full editorial: Machine identity management is shifting toward ephemeral access models