Starting in March 2026, TLS certificate lifecycles will shrink by half, to 200 days. And by 2029, you'll need to renew these certificates every 47 days. This means 8-12x the current renewal volume. Manual CLM (certificate lifecycle management) simply won't be possible. Teams must rethink how they manage risk and compliance.

In this session, PKI and encryption expert George Parsons sits down with Ryan Hurst, a cryptography pioneer and former Google and Microsoft security leader, to break down what’s changing, the operational risks of delayed action, and how organizations can use automation and policy alignment to adapt at scale.

Whether you're managing five or 10,000 certificates, understanding the 47-day shift and the potential for disruption to your critical systems is vital. You’ll leave the session with a clear understanding of how to:

• Modernize your TLS certificate lifecycle management strategy
• Communicate risk across technical and business teams, leadership, and the Board
• Build this change into your budget now (and quantify inaction to frame your business case)
• Ensure your infrastructure is ready for 47-day renewal cycles — mandatory for public PKI, and increasingly valuable for internal PKI as well.

Join us to get ahead of the transition and bring resilience to your TLS/SSL certificate lifecycle.

‍