Topic starter
09/07/2026 1:41 pm
TL;DR: Automation is now a practical requirement for machine identity programmes as enterprises manage tens of thousands of TLS certificates, shorter renewal windows, and certificate-related outages driven by human error, according to Keyfactor. The operational issue is no longer efficiency alone: manual trust operations cannot sustain reliable governance at machine scale.
Editorial analysis by NHI Mgmt Group, based on content published by Keyfactor: “Stage Four – Automate & Orchestrate: Trust at Machine Speed”.
By the numbers:
- A Fortune 500 enterprise might easily have 50,000+ TLS certificates and countless keys and secrets.
- Public TLS certificates are moving to 90-day or shorter lifetimes.
- 81% of organisations have experienced a certificate-related outage in the last two years.
Key questions
Q: What breaks when machine identity lifecycle management is still partly manual?
A: Manual lifecycle management breaks first at scale.
Q: Why does automation reduce outage risk in machine identity programmes?
A: Automation reduces outage risk because it removes routine trust tasks from human handling and ties issuance to deployment and verification.
Q: How do you know if machine identity automation is actually working?
A: Automation is working when it reduces manual intervention, shortens renewal and revocation latency, and produces continuous evidence of control.
Practitioner guidance
- Automate renewal, deployment, and verification together Connect certificate renewal to endpoint deployment and active-state verification so a renewed certificate is not considered complete until it is live on the target service.
- Replace spreadsheet-driven lifecycle tracking Move certificate and key tracking into an orchestration workflow that can schedule renewals, trigger deployment, and surface exceptions without manual chasing.
- Embed trust issuance into CI/CD pipelines Issue machine identities at deploy time so new services, containers, and workloads receive compliant certificates and secrets as part of the release process.
Bottom line: Machine identity outages are increasingly a governance failure, not just a technical nuisance, because renewal and deployment now happen too fast for manual oversight to be reliable.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 1:45 pm
Machine identity automation is now a reliability control, not a convenience layer. The article shows that certificate operations have crossed the threshold where manual handling is no longer operationally credible. When 50,000+ TLS certificates and shorter rotation windows collide, the real risk is service interruption through missed lifecycle events, not just administrative inefficiency. Practitioners should treat automated trust orchestration as part of service resilience, not a back-office optimization.
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.
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: When should organisations prioritise automation over manual certificate handling?
A: Automation should be the default once an organisation manages more than a small number of certificates, because scale makes manual renewal unreliable. The turning point is not a specific count, but the moment certificates span teams, tools, and infrastructure layers that no single person can track safely.
👉 Read our full editorial: Automating machine identity trust reduces outage risk at scale