Topic starter
30/09/2026 5:00 pm
TL;DR: Akeyless says as TLS certificate lifetimes move toward 47 days, machine identity programmes are being forced to manage larger certificate volumes, more frequent renewals, and greater governance complexity. Manual ownership and fragmented lifecycle processes no longer scale cleanly across cloud, hybrid, and DevOps environments.
Editorial analysis by NHI Mgmt Group, based on content published by Akeyless: “The 47-Day Certificate Era: Are Your Machine Identities Ready?”.
By the numbers:
- As public TLS certificate lifetimes move toward 47 days, organizations face increasing pressure to manage larger certificate volumes.
Key questions
Q: What breaks when certificate lifetimes shorten but ownership stays fragmented?
A: Renewal becomes a coordination problem instead of a control.
A: Shorter certificate lifespans increase the number of renewals, which multiplies the chance of missed expiration and service outage.
Practitioner guidance
- Map certificate ownership to every machine identity Create a live inventory that ties each certificate to an application, service, pipeline, or automated workload, with an accountable owner and renewal path.
- Automate renewal before expiry becomes urgent Replace manual renewals with policy-driven lifecycle automation so certificate issuance, renewal, and revocation happen without relying on last-minute human action.
- Reduce fragmented certificate stewardship Consolidate governance for certificates, secrets, and keys so teams can see where machine credentials live and who is responsible for their lifecycle.
Bottom line: Shorter certificate lifetimes turn machine identity management into a continuous governance task rather than a periodic renewal exercise.
What to expect at the briefing
Akeyless's full webinar covers the operational detail this post intentionally leaves for the source:
- Live discussion on automating certificate issuance, renewal, and lifecycle processes across modern environments
- Specific guidance on reducing outage risk from expired or unmanaged certificates
- Speaker perspectives on certificate governance across cloud, hybrid, DevOps, and automated systems
- A practical look at preparing for shorter certificate lifecycles at machine scale
👉 Watch Akeyless's live webinar on the 47-day certificate era and machine identity governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
30/09/2026 5:00 pm
47-day certificates turn machine identity into a lifecycle governance test. The issue is no longer whether certificates can be renewed, but whether the organisation can govern every certificate through inventory, ownership, and offboarding at machine scale. Shorter lifetimes expose whether machine identity programmes are operationally disciplined or still dependent on human memory. Practitioners should treat certificate lifecycle control as a core identity governance capability, not a back-office PKI function.
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.
- The 2025 Gartner Machine Identity Management in a Hybrid, Automated AI World Survey showed that 32% of organizations use mostly automated methods to manage credentials and only 1% use fully automated methods.
A question worth separating out:
Q: How should teams govern certificate lifecycle management in multi-cloud environments?
A: Teams should govern CLM as part of the broader machine identity stack, not as a standalone certificate tool. That means tying issuance, renewal, revocation, and discovery to secrets management, key protection, and audit evidence so identity state remains consistent across cloud platforms and workloads.
👉 Read our full editorial: The 47-day certificate era raises machine identity governance risk