11/18/2026 | Press release | Distributed by Public on 11/18/2026 05:27
In Brief (TL;DR)
Shorter certificate lifespans are making manual certificate management increasingly difficult, creating new risks for network security and operational resilience. With validity periods set to fall to just 47 days by 2029, organisations need better visibility, automation and control over their certificate estates. Getting this right will not only help prevent outages and reduce operational overhead, but also build the crypto agility needed to prepare for the transition to post-quantum cryptography.
As certificate lifetimes shrink and machine identities multiply, organisations need to rethink how they manage digital trust. What was once an administrative PKI task is quickly becoming a wider network security challenge, with implications for automation, resilience and post-quantum readiness.
For years, digital certificates have quietly kept enterprise networks running. They authenticate systems, secure connections, and establish trust among applications, devices, services, and users.
But the way organisations manage those certificates is about to come under increasing pressure.
Public TLS certificate lifetimes are getting shorter. The maximum validity period has already been reduced to 200 days, with further reductions planned to 100 days in March 2027 and just 47 days by March 2029.
On the surface, this might sound like an administrative change. In reality, it has much wider implications for network security and operational resilience.
The certificate challenge is growing
Most organisations have more certificates than they realise.
They sit across firewalls, web servers, load balancers, cloud workloads, containers, APIs and internal systems. Some are managed centrally, others are issued by different certificate authorities, and many have accumulated over time without anyone having a complete picture of where they are or what depends on them.
This creates a visibility problem.
A certificate expiring unexpectedly can interrupt services, break application connections or leave critical systems unable to communicate. As certificate lifetimes get shorter, tracking everything manually becomes increasingly unsustainable.
Consider an organisation with 500 public TLS certificates. Once the maximum validity period reaches 47 days, renewing those certificates every 30-40 days could mean managing around 4,000 to 6,000 renewals each year.
That's a significant increase in operational activity, particularly for organisations still relying on manual processes.
Spreadsheets and calendar reminders simply aren't going to cope.
The challenge is particularly relevant to organisations operating Secure Access Service Edge (SASE) and Security Service Edge (SSE) environments. Customer-facing certificates, cloud proxies, browser-based Zero Trust Network Access (ZTNA) and private service edges all rely on certificates working correctly. These dependencies can easily be overlooked until something expires and users start experiencing problems.
Certificate management is no longer just a PKI concern. It's becoming an operational requirement for the teams responsible for keeping networks and security services running.
Why visibility and automation matter
The first step is understanding what you actually have.
Organisations need a complete view of their certificate estate, including certificates issued by different public and private certificate authorities, those spread across multiple environments and the ones that may have been forgotten altogether.
This means moving away from fragmented processes towards centralised certificate lifecycle management.
There are three important capabilities to consider:
We're also seeing certificate lifecycle management become more closely integrated with network security platforms. Palo Alto Networks, for example, has brought lifecycle management and PKI capabilities into its Next-Generation Trust Security (NGTS) offering, integrated with Strata Cloud Manager. There is another consideration that is often overlooked: Domain Validation. By March 2029, the maximum period for reusing domain validation data will fall to just 10 days. This means organisations will need to automate not only certificate insurance and renewal, but also the process used to demonstrate control of their domains.
Without this, even organisations that have automated certificate renewals could find themselves facing additional manual work.
However, organisations don't need to commit to a single network vendor to address the challenge. Certificate management needs to work across the wider technology estate, including multi-vendor environments and existing infrastructure.
The link to post-quantum readiness
There is another reason why getting certificate management right matters: quantum computing.
Post-quantum cryptography (PQC) is often discussed in terms of replacing vulnerable encryption algorithms. But the practical challenge is much broader.
Organisations will need to understand where cryptography is being used, which systems and services depend on it, and how to update certificates, keys and cryptographic configurations when the time comes.
This is where crypto agility becomes essential.
If an organisation cannot identify all its certificates today, how will it manage a large-scale cryptographic transition tomorrow?
As post-quantum algorithms such as ML-KEM become increasingly integrated into modern TLS implementations , organisations will need the ability to adapt their cryptographic infrastructure without lengthy, disruptive projects.
Certificate lifecycle management provides an important part of that foundation. Those investing in visibility and automation now will be in a much stronger position to manage future changes.
In the UK, the NCSC expects organisations to complete discovery and planning by 2028, carry out migration planning by 2031and complete their transition by 2035.
The US is also setting clear deadlines. NIST's October 2026 guidance confirms that quantum-vulnerable public key algorithms will be l deprecated after 2030 and disallowed under NIST standards and guidelines after 2035. Federal high-value assets and high-impact systems face earlier requirements, with post-quantum key establishment required by the end of 2030 and digital signatures by the end of 2031."
Getting ahead of the change
Shorter certificate lifetimes are not going away, and the operational pressure will only increase as organisations move towards more automated, cloud-based and interconnected environments.
For CISOs, CTOs and infrastructure leaders, now is a good time to ask some straightforward questions:
The organisations that address these questions now will be better placed to avoid unexpected outages, reduce operational overhead and prepare for the cryptographic changes ahead.
The upside. Shorter lifetimes also shrink exposure from compromised keys and reduce reliance on broken revocation, therefore enhancing your security posture.
At Xalient, we help organisations bring together network, security and identity to address challenges like these. Taking a vendor-agnostic approach, we can help you understand your certificate estate, identify potential risks and explore how certificate lifecycle management can be automated across your environment.
If you don't know where all your certificates are today, it's going to be much harder to manage them when their lifetimes get even shorter.
Ready to make AI Accountable?
About the author
Technical Director at Xalient
Neil Johnson is an experienced technology leader with a strong technical background in networking, cybersecurity and enterprise infrastructure. As Technical Director at Xalient, Neil works with organisations to navigate evolving security challenges, helping them design and implement solutions that strengthen their networks, protect digital environments and support business transformation.