Topic starter
24/06/2026 11:22 pm
TL;DR: As public TLS certificates move toward 47-day lifecycles by 2029, renewal volume can rise almost eightfold for large environments, exposing manual PKI processes that cannot keep pace, according to DigiCert. Certificate governance is shifting from periodic maintenance to alliance-driven automation, where reliability depends on coordinated lifecycle control across platforms, operators, and integrators.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “Why Strategic Alliances Are Now a Must-Have for PKI”.
Key questions
Q: What breaks when certificate lifetimes shrink to 47 days?
A: Manual certificate processes break first, followed by renewal consistency, deployment timing, and outage tolerance.
Q: Why do short-lived certificates increase governance risk?
A: Short-lived certificates increase governance risk because they compress the time available for manual review, approval, and replacement.
Q: How do teams know whether certificate automation is actually working?
A: Look for fewer human-mediated renewals, cleaner ownership records, lower expiry-driven outage rates, and reliable reporting across hybrid systems.
Practitioner guidance
- Inventory certificate-dependent systems across the delivery stack Map where public TLS certificates are issued, installed, renewed, and validated across load balancers, firewalls, cloud services, and legacy platforms.
- Automate renewal and installation as one workflow Do not stop at certificate issuance automation.
- Assign lifecycle ownership across partners and operators Document who owns policy, execution, escalation, and exception handling when certificates span internal teams, managed service providers, and integrators.
Bottom line: Short certificate lifecycles make PKI a continuous operations problem rather than a periodic maintenance function.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 8:11 am
47-day PKI turns certificate lifecycle governance into an operating discipline, not a renewal task. The old assumption was that certificates could be managed through periodic maintenance because lifetimes were long enough to fit human workflows. That assumption fails when renewal frequency rises to machine speed, because the control surface shifts from occasional administration to continuous orchestration. The implication is that certificate governance now belongs inside the identity operating model, not beside it.
A few things that frame the scale:
- 48% of organisations cite cloud-based services as a driver for PKI deployment, according to the 2023 State of Machine Identity Management report.
A question worth separating out:
A: Start with a defined scope, then map certificate inventory, approval workflows, renewal timing, and revocation ownership. A workable programme ties issuance, validation, and monitoring into one process, so expired or misused certificates do not linger unnoticed. Integrate the platform with existing IAM and enterprise systems, and train the teams that own certificates so the workflow is usable in practice.
👉 Read our full editorial: 47-day PKI certificate lifecycles demand alliance-driven governance