TL;DR: Public SSL/TLS certificate validity drops to 200 days on March 15, 2026, cutting the previous 398-day window in half and exposing manual certificate management to missed renewals, outages, and compliance failures as the industry moves toward 100-day and 47-day lifecycles, according to Sectigo.
Editorial analysis by NHI Mgmt Group, based on content published by Sectigo: “Understanding the Risk Scale: 6-month SSL/TLS Validity Starts March 15, 2026”.
By the numbers:
- Public SSL/TLS certificate validity falls from 398 days to 200 days on March 15, 2026.
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 shorter certificate lifespans increase outage risk?
A: Shorter lifespans compress the time available for discovery, approval, renewal, and validation.
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
- Build a complete certificate inventory Map every public certificate, owner, expiration date, and renewal dependency so the estate is visible before the 200-day threshold takes effect.
- Identify remaining manual renewal steps Document where issuance, renewal, approval, and revocation still depend on human intervention, then classify those paths by outage risk and volume.
- Prioritise automated issuance and renewal Evaluate ACME-based or equivalent automation for high-volume certificates so renewals can occur without ticket-driven delays.
Bottom line: Shorter SSL/TLS validity turns certificate management into an always-on governance problem rather than a once-a-year renewal task.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →