Topic starter
06/11/2026 6:55 pm
TL;DR: Machine identities outnumber human users 45:1 and are growing 44% year over year, according to AppViewX’s analysis of certificate governance. Teams now need discovery and automation to prevent outages, because manual renewal processes cannot keep pace with machine-scale credentials.
Editorial analysis by NHI Mgmt Group, based on content published by AppViewX: “What is Non-Human Identity?”.
By the numbers:
- Machine identities outnumber human users 45:1 in modern enterprises.
- Machine identities are growing 44% year over year as cloud, AI, and containerization accelerate.
Key questions
Q: Why do expired certificates cause wider outages than expired API tokens?
A: Expired certificates often cause wider outages because they are embedded in many services, clusters and deployment pipelines, so one missed renewal can break many connections at once.
Q: How should teams discover hidden service accounts and certificates?
A: Teams should discover hidden service accounts and certificates by combining automated scanning of cloud accounts, directories, repositories, container images and certificate stores with inventory reconciliation.
Q: How do certificates support machine-to-machine authentication?
A: Certificates support machine-to-machine authentication by proving a workload or service owns a private key linked to a trusted public certificate.
Practitioner guidance
- Map every machine credential to an owner and dependency chain Create an authoritative inventory of certificates, keys, and API tokens across cloud, containers, and on-premises systems, then record which service each credential supports and who is accountable for renewal.
- Automate renewal before certificate validity windows shrink Replace spreadsheet-driven renewals with policy-based workflows that request, issue, deploy, and validate certificates before expiration across all production environments.
- Separate discovery from remediation Run agentless scans to find hidden credentials first, then prioritise the highest-risk certificates for rotation, revocation, or replacement based on service criticality.
Bottom line: Machine identities are now a scale problem, not a niche infrastructure detail, because the volume of machine credentials has outgrown manual governance.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:56 pm
Certificate lifecycle is now operational resilience infrastructure: The article is right to treat machine identity as a business continuity issue, not a narrow security task. When certificates touch customer transactions, APIs, and deployment pipelines, expiry becomes an outage mechanism as much as a trust failure. The practitioner takeaway is to govern certificate lifecycle with the same seriousness as production uptime.
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.
- 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: When should machine identity governance move from manual to automated?
A: Machine identity governance should move from manual to automated when the number of service accounts, API keys, tokens and certificates exceeds what teams can track reliably by hand, or when rotation, expiry and ownership checks must happen continuously. Automation then enforces lifecycle events, policy checks and revocation at scale, reducing missed renewals and orphaned credentials.
👉 Read our full editorial: Machine identity failures now threaten uptime and revenue