Topic starter
10/07/2026 9:09 pm
TL;DR: Certificate lifetimes will shrink from 200 days in 2026 to 47 days in 2029, turning manual renewal, revocation, and inventory management into a near-continuous operational burden, according to GlobalSign. The real issue is not the date itself, but the fact that certificate governance now depends on automation, ownership, and auditability rather than periodic maintenance.
Editorial analysis by NHI Mgmt Group, based on content published by GlobalSign: “El riesgo oculto en tus certificados — y por qué la automatización no puede esperar”.
By the numbers:
- Certificate lifetimes will fall to 200 days in 2026 before reaching 47 days in 2029, according to GlobalSign.
Key questions
Q: What breaks when certificate lifetimes shrink faster than teams can renew manually?
A: Manual certificate management breaks at the coordination layer first.
Q: Why do shorter certificate lifetimes create more operational risk?
A: Shorter lifetimes compress the time teams have to discover, approve, renew, and validate trust without interruption.
Q: How do security teams know if certificate lifecycle management is working?
A: Certificate lifecycle management is working when every certificate has a clear owner, renewal is automated or tightly managed, and expiry cannot occur without escalation.
Practitioner guidance
- Automate certificate discovery and renewal Replace manual expiry tracking with continuous discovery, renewal workflows, and alerting across cloud, endpoint, and internal services.
- Assign explicit certificate ownership Attach each certificate to a named business or technical owner so that renewal, revocation, and exception handling do not depend on tribal knowledge.
- Build a system-wide certificate inventory Maintain a live inventory that includes location, expiry, issuing authority, and dependent services, with no reliance on isolated platform views.
Bottom line: Shorter TLS certificate lifetimes turn manual renewal into a brittle operating model that will not scale.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:33 pm
Certificate governance is now a machine-identity problem, not a paperwork problem: the article shows that shrinking TLS validity windows convert certificates into high-frequency credentials that need ownership, inventory, and lifecycle enforcement. Manual renewal models assume enough time exists for human review, but that assumption fails once expiries compress into weekly operations. Practitioners should treat certificate estates as part of the broader NHI governance surface.
A question worth separating out:
Q: How should organisations govern certificates alongside NHI controls?
A: They should treat certificates as part of the wider non-human identity estate and govern them with the same discipline used for service accounts and API credentials. That means assigning ownership, limiting scope, tracking lifecycle events, and proving revocation. Certificate governance should sit inside identity operations, not beside it.
👉 Read our full editorial: 47-day certificates will break manual TLS operations by 2029