PKI ecosystem changes in 2026: what your team needs to know

Executive summary: 2026 is shaping up to be the busiest year the PKI ecosystem has ever seen. Certificate lifetimes are dropping to 200 days (and heading to 47 days by 2029), private PKI remains a blind spot for most organizations, and post-quantum cryptography (PQC) migration timelines are tightening. Red Sift's Billy McDermid, VP of Customer Engineering, and Bhushan Lokhandi , Principal Software Engineer, broke it all down in a recent webinar.

Key takeaways:

• Apple is enforcing 200-day certificate lifetimes from the end of March 2026, with Amazon already issuing 198-day certificates. By 2029, lifetimes drop to 47 days.
• 81% of certificate-related outages are still caused by expired or misconfigured certificates. Shorter lifetimes multiply that risk.
• 60% of enterprises run their own internal certificate authorities (CAs), and the average large enterprise has more than 140,000 internal certificates in use. Most have minimal central oversight.
• The "Harvest Now, Decrypt Later" threat from quantum computing means organizations should deploy hybrid TLS (combining classical ECDHE with ML-KEM) now.
• Organizations need a real-time, multi-source certificate inventory across public and private infrastructure to keep pace with these changes.

The changes are already here. Apple is enforcing 200-day maximum certificate lifetimes from the end of March 2026. Amazon has started issuing 198-day certificates too. If you have certificates in your estate from these providers, you're going to see the number of certificates in your environment at least double this year.

And that's just the start. By 2027, lifetimes drop to 100 days. By 2029, they hit 47 days.

Here's the math that matters: a 47-day lifetime means roughly eight times as many certificate renewals per year compared to today. If you're an organization with 1,000 public certificates right now, you're looking at managing 8,000 renewal events annually by 2029.

That volume makes manual certificate renewal impossible. But as Billy McDermid pointed out during the webinar, automation alone isn't enough either.

"We talk to customers about this every single day," McDermid said. "They come to us and say they thought they had everything automated. Then the automation failed in one part of their estate, or a third-party certificate that one of their services depended on expired."

The replacement window is shrinking too. The old best practice was to start rotating certificates 30 days before expiry. With shorter lifetimes, you might be looking at a seven-day window. That cuts the time you have to catch and fix a failed automation dramatically.

And the stakes are real: 81% of certificate-related outages are still caused by expired or misconfigured certificates. That's already one of the biggest causes of downtime. Shorter lifetimes, without the right tooling, will make it worse.

Public PKI (the certificates securing your website, public APIs, and external domains) gets most of the attention. There's a well-established ecosystem of CAs, browser enforcement, certificate transparency (CT) logs, and compliance requirements that keep public PKI relatively well managed.

Private PKI is a different story.

Internal certificates securing your servers, VPNs, DevOps pipelines, IoT devices, and internal APIs are often issued by internal private CAs like Microsoft Active Directory Certificate Services (ADCS) with minimal central oversight. Lifetimes are frequently set to years, sometimes even decades. There's typically no external monitoring. And when something goes wrong (an unexpected expiry, a compromised root, a misconfigured intermediate), the impact can be severe and hard to diagnose.

The numbers tell the story. 60% of enterprises run their own internal CAs. A large enterprise on average has more than 140,000 internal certificates in use. And 57% of organizations are now incorporating zero trust into their encryption strategy, which means private PKI is becoming even more central to how they operate.

Zero trust follows a simple principle: never trust, always verify. Every service gets a unique certificate. Every connection uses mutual TLS (mTLS), meaning both sides must present a valid certificate signed by a trusted CA. Access is policy-driven, not location-based.

Private PKI is what makes all of this possible at scale. It gives every service, device, and user a strong cryptographic identity. But because zero trust favors short-lived, auto-rotated certificates, the volume and velocity of certificate operations is only going up.

And the consequences of private PKI failure go beyond your website going down. When private certificates expire or break, it can take out manufacturing lines, operational technology (OT) systems, and internal services that your business runs on. As McDermid put it, "we're no longer just talking about your website being down or your API not responding. We're talking about manufacturing of product no longer taking place."

Post-quantum cryptography (PQC) readiness feels like a future problem. The regulatory deadlines for full migration sit around 2030 to 2033. But the preparation required is substantial, and one threat demands action right now.

When a cryptographically relevant quantum computer (CRQC) is built, it will break today's widely deployed public key cryptography, including RSA and elliptic curve cryptography (ECC), essentially overnight.

The immediate concern is called "Harvest Now, Decrypt Later." Adversaries can already capture encrypted data today (your TLS traffic, VPN tunnels) and store it. Once a CRQC becomes available, they can decrypt everything they've collected. For organizations handling long-lived sensitive data, that makes this a present-day risk, not a future one.

Red Sift's Bhushan Lokhandi outlined three steps for building PQC readiness.

• Step one: know your posture. You can't protect what you can't see. Build a comprehensive, always up-to-date inventory of your cryptographic assets across both public-facing and internal private infrastructure. Every domain, subdomain, certificate, and network endpoint.
• Step two: identify your weak links. Which systems are running algorithms that quantum computers will break? That means finding all RSA and ECC deployments. You're also looking for systems that lack crypto-agility (ones that can't be updated to support new algorithms without significant re-engineering).
• Step three: plan the migration. Not everything needs to move at once. Prioritize long-lived data and high-risk systems, as they carry the greatest "Harvest Now, Decrypt Later" exposure.

The migration has two distinct parts. On the key exchange side, the most urgent action is deploying hybrid TLS, combining classical ECDHE with ML-KEM (formerly known as Kyber). This directly addresses the "Harvest Now, Decrypt Later" risk while maintaining backward compatibility. Cloudflare, Google, and major browser vendors are already deploying hybrid key exchange at scale. On the digital signature side, organizations should phase in NIST-standardized post-quantum algorithms like ML-DSA and SLH-DSA as the ecosystem matures.

PQC readiness isn't a single event. It's a migration process, and you should start immediately.

All three of these shifts point to the same underlying requirement. You need a comprehensive, continuously updated inventory of every certificate in your estate, public and private, the moment it's issued.

Spreadsheets won't cut it anymore. Daily scans won't cut it either. You need real-time ingestion of certificates from multiple discovery sources: hostname-based discovery, network scanning, certificate transparency logs, cloud provider integrations, and private infrastructure agents.

Most organizations also underestimate their certificate authority sprawl. McDermid shared a telling observation from the webinar: most prospects Red Sift onboards discover certificates from 10 or 11 different certificate authorities, plus self-signed certificates, and that's just the public footprint before looking inside the network.

You also need visibility into your cryptographic posture: which endpoints support PQ-safe key exchange, which certificates use quantum-vulnerable algorithms, and where your estate stands against the coming lifecycle changes.

A CLM (Certificate Lifecycle Management) tool handles issuance and renewal. But in 2026, you need an insurance policy that sits alongside your CLM: something that deploys in minutes, provides continuous real-time detection, correlates certificate data with CT logs and DNS, and covers both sides of the network.

Red Sift Certificates provides public and private infrastructure monitoring in a single view, with dedicated dashboards for PQC readiness and certificate lifecycle compliance. The platform's private PKI agent discovers certificates across internal infrastructure and brings them into the same inventory as your public certificates.

New capabilities launching in 2026 include an ADCS integration (coming Q2), HashiCorp Vault integration later in the year, and MCP (Model Context Protocol) access so teams can query their certificate estate using AI.

Want to see how your estate stacks up? Check your domain's security posture with Red Sift Radar Lite for a free assessment, or request a demo of Red Sift Certificates to get full visibility into your public and private certificate infrastructure.