TL;DR: The industry move to 199-day TLS certificates in March 2026, then 99-day and 46-day lifecycles, will multiply renewal volumes and expose gaps in discovery, ownership, and automation, according to Sectigo. Manual certificate operations assume renewal can be handled as a periodic task; that assumption fails once replacement becomes continuous infrastructure work.
Editorial analysis by NHI Mgmt Group, based on content published by Sectigo: “Keeping an eye on the TLS clock: Key certificate lifecycle dates you need to know”.
Key questions
Q: What breaks when public TLS certificate lifespans shrink but renewal stays manual?
A: Manual renewal breaks first because the lifecycle becomes too compressed for ticket-based workflows to handle reliably.
Q: Why do DNS retirements create governance risk for IAM and platform teams?
A: DNS retirements expose the gap between operational ownership and access governance.
A: Security teams should maintain a complete certificate inventory, tie each certificate to an owner or endpoint, and automate renewal, revocation, and replacement before expiry.
Practitioner guidance
- Automate certificate discovery across every environment Build continuous inventory coverage for public TLS, internal certificates, and any certificate embedded in application or platform workflows.
- Assign certificate ownership to named operational teams Map every certificate to a responsible team or system owner so renewal, validation, and replacement cannot stall in an ambiguity gap.
- Eliminate manual DCV where possible Replace human-driven domain control validation steps with automated checks and repeatable issuance workflows so renewal cadence can move from quarterly to monthly without bottlenecks.
Bottom line: Shrinking TLS lifetimes turn certificate renewal into a continuous governance and operations problem, not a periodic administrative task.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →