TL;DR: Arcon's analysis of NHI access management finds service accounts, hardcoded credentials, secrets, APIs, bots, and cloud-native systems now sit under one governance problem, with centralised control treated as a core operating requirement. Practitioners need to manage machine credentials as governed identities, or exposure will persist across the lifecycle.
Editorial analysis by NHI Mgmt Group, based on content published by Arcon: “ARCON Digital Vault”.
Key questions
Q: Why do long-lived secrets keep creating risk even when teams centralise them?
A: Centralisation does not remove risk if ownership, access scope, and revocation rules are unclear.
Q: What breaks when corporate IT machine identities are not lifecycle-managed?
A: What breaks is the assumption that mature infrastructure controls automatically govern non-human access.
A: Treat hardcoded and poorly stored credentials as an immediate exposure problem, not a coding convenience.
Practitioner guidance
- Inventory embedded credentials across code and automation Search code repositories, scripts, CI pipelines, and deployment artefacts for hardcoded credentials, then assign each finding to an owner for remediation and revocation.
- Separate secret storage from secret governance Define who owns each secret, which systems may consume it, and what event triggers rotation or revocation, so the vault acts as a governed control plane rather than a passive store.
- Map every machine identity to a lifecycle trigger Tie service accounts, API keys, and tokens to provisioning, review, and offboarding events so access cannot survive workload retirement or ownership changes.
Bottom line: NHI risk is increasingly created by how secrets are governed across automation, APIs, bots, and cloud-native systems, not just by where they are stored.
Glossary terms: Non-Human Identity (NHI), Hardcoded Credential, Secrets Management, Digital Identity Workflow
What's in the full article
Arcon's full report covers the operational detail this post intentionally leaves for the source:
- Unified dashboard capabilities for managing digital assets and access permissions across machine and application identities
- How the report frames creation, mapping, and lifecycle management of digital identities in practice
- The report's vendor-specific description of data processing and access control workflows
- The full contextual framing behind the Executive View research that this analysis only summarises
👉 Read Arcon's report on NHI access governance and digital vault management →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Secrets governance is now an identity governance problem, not a storage problem. The article’s central point is that credentials, keys, and tokens now sit inside a broader NHI access model that includes automation, APIs, bots, and cloud-native systems. That means ownership, access policy, and revocation matter as much as where the secret is stored. Practitioners should treat secrets as governed identities with lifecycle obligations, not as inert configuration values.
A few things that frame the scale:
- 30.9% of organisations store long-term credentials directly in code, according to the Ultimate Guide to NHIs.
- Only 44% of organisations are currently using a dedicated secrets management system, according to the 2024 State of Secrets Management Survey.
A question worth separating out:
Q: What is the difference between dynamic secrets and static secrets for NHI governance?
A: Static secrets remain valid until someone rotates or revokes them, so exposure windows can be long. Dynamic secrets are issued for a shorter purpose and can shrink exposure, but only if the surrounding governance tracks issuance, use, and retirement properly. The difference is not just technical format; it is control over lifespan.
👉 Read our full editorial: NHI access governance needs central control as secrets sprawl grows