TL;DR: Certificate operations could be reshaped as lifetimes shrink and post-quantum signatures grow, according to Sectigo, pushing teams toward automation, visibility and crypto-agility rather than manual renewal workflows. The operational challenge is no longer whether a new certificate format wins, but whether governance can keep pace with faster replacement and multiple certificate forms.
Editorial analysis by NHI Mgmt Group, based on content published by Sectigo: “What Merkle Tree Certificates (MTCs) mean for your certificate operations”.
By the numbers:
- TLS certificates are under mandates to shorten through a phased approach, resulting in a 47-day lifespan by 2029.
Key questions
Q: How should security teams respond to shorter certificate lifespans?
A: They should treat shorter lifespans as an automation mandate, not as a reason to add more manual review.
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: What breaks when certificate lifecycle management is still manual?
A: Manual certificate management breaks at the point where expiry, ownership, and renewal do not line up.
Practitioner guidance
- Build a complete certificate inventory Track every certificate, associated relying party, and renewal dependency so format changes and short validity periods do not create blind spots.
- Automate issuance and replacement workflows Remove spreadsheet-based renewal steps and use repeatable automation for issuance, deployment, renewal, revocation, and monitoring.
- Map support for multiple certificate forms Identify which applications, devices, and infrastructure can accept older and newer certificate forms before mixed-state operations begin.
Bottom line: Shorter certificate lifetimes make certificate lifecycle governance a reliability issue, not just a renewal task.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →