Chrome Root Program: The case for bringing certificate issuance in-house
Chrome's Root Program Policy v1.8 limits public trust to TLS server authentication, ending clientAuth in public TLS certificates from March 15, 2027 (Sectigo's cutoff: February 10, 2027). Teams using public certificates for mTLS, VPN, Wi-Fi or device identity should move those jobs to a private PKI for more control, automation and crypto agility.
For years, the publicly trusted TLS certificate was the Swiss Army knife of enterprise identity. It secured the website, but it also authenticated the VPN client, the Wi-Fi supplicant, the API partner and the microservice calling another microservice. One certificate, one vendor, one renewal. Convenient, until the browsers decided public trust should mean one thing only.
Chrome's Root Program has now made that decision formal. Version 1.8 of its policy states that the Chrome Root Store is relied upon solely for TLS server authentication, and it is phasing out every public PKI hierarchy that tries to do anything else. For organizations that have been leaning on public certificates for internal jobs, the direction is clear: public trust is for the public web. Everything else belongs in a PKI you control.
That isn't just a compliance chore. Done well, bringing certificate issuance in-house is one of the smartest moves a security team can make ahead of shorter certificate lifetimes and the shift to post-quantum cryptography.
What the Chrome Root Program now requires
Chrome Root Program Policy v1.8 (last updated February 5, 2026) turns a long-signalled direction into hard dates:
- Dedicated hierarchies: Subordinate CAs disclosed on or after June 15, 2026 may assert only the server authentication EKU (id-kp-serverAuth). Multi-purpose public hierarchies are being phased out.
- Server-only leaf certificates: Publicly trusted TLS certificates issued on or after March 15, 2027 must assert only serverAuth. The client authentication EKU (id-kp-clientAuth) is gone from public TLS.
- Automation as a baseline: From March 15, 2027, subordinate CAs in the Chrome Root Store must support automated issuance.
- Root term limits: Roots are removed 15 years after their key material was generated, so public trust anchors now rotate on a fixed clock.
Date | What changes |
June 15, 2026 | New public subordinate CAs must be serverAuth-only (now in effect) |
March 15, 2027 | New public TLS certificates must be serverAuth-only; automation support required |
March 15, 2027 | Maximum public TLS validity drops to 100 days (CA/B Forum Ballot SC-081) |
March 15, 2029 | Maximum public TLS validity drops to 47 days (SC-081) |
Certificates issued before these cutoffs stay valid until they expire. The impact shows up at renewal: a certificate renews cleanly, looks healthy in every dashboard, and then a mutual TLS handshake fails because the clientAuth EKU is no longer there. Sectigo, like other major public CAs, has already stopped including clientAuth in public TLS certificates by default, and its final cutoff is February 10, 2027. From that date, Sectigo will no longer issue public TLS certificates carrying the clientAuth EKU, so Sectigo customers should plan to complete their migration ahead of Chrome's March 2027 deadline.
Where public certificates are quietly doing private jobs
Most teams don't set out to use public certificates for internal authentication. It happens because the certificate was already there and it worked. Common examples include:
- Mutual TLS (mTLS) between microservices, API gateways and service meshes
- B2B and partner integrations that authenticate with client certificates
- Enterprise Wi-Fi and wired network access (802.1X, EAP-TLS, RADIUS)
- VPN client authentication
- Server-to-server connections such as mail and messaging connectors
- IoT and device identity
- CI/CD pipelines and developer environments
The test is simple. If a certificate's job is to prove a user, device or workload to your systems, rather than to prove your website to the world's browsers, it's a private PKI job.
Why in-house is the better answer, not just the required one
Chrome's policy closes a door, but the room on the other side is a better place to be.
Your policy, not the browser's: A private CA issues certificates to your rules: the EKUs each use case needs, validity periods that fit the device or workload, internal hostnames and IP addresses, and key types of your choosing. Public certificates have to satisfy the Baseline Requirements and every browser root program. Internal certificates only have to satisfy you.
Insulation from public-trust changes: When internal authentication depends on public certificates, every shift in public policy (EKU removals, shorter lifetimes, root rotations) becomes an internal change project. Bringing issuance in-house decouples your internal operations from a timetable you don't set.
Built for machine-identity scale: Machine identities already outnumber human ones, and the gap keeps growing. A private CA lets you issue high volumes of short-lived certificates to workloads and devices without routing internal identity through public validation processes.
Crypto agility on your terms: A private hierarchy is where you can pilot new algorithms, including post-quantum and hybrid certificates, against your own systems before the public ecosystem is ready. That makes private PKI a practical proving ground for your PQC roadmap.
A cleaner governance story: Separate public and private trust means separate, auditable policies, a clear owner for each, and no ambiguity about which certificates face the internet.
In-house doesn't mean do-it-yourself
For many security teams, "private PKI" still conjures an on-premises CA server that one person knows how to run, renewals tracked in a spreadsheet, and an outage every time something expires unnoticed. That model was never built for today's certificate volumes or lifetimes.
A modern private CA looks very different. It's cloud-delivered, can be stood up quickly, scales automatically, and enrolls certificates over standard protocols such as ACME, EST and SCEP. Bringing issuance in-house means owning the trust decisions, not the hardware.
A practical path to March 2027
- Find every certificate carrying clientAuth: Discover certificates across cloud, on-premises and hybrid environments, and flag every one used for client authentication, whichever CA issued it.
- Classify by audience: Public-facing services stay on publicly trusted certificates. Everything that authenticates users, devices or workloads internally moves to private trust.
- Design dedicated private hierarchies: Mirror Chrome's own logic: separate roots or issuing CAs by purpose (for example, network access, workloads and devices) so each can evolve independently.
- Automate enrollment and renewal: With public lifetimes falling to 100 days in 2027 and 47 days in 2029, manual renewal won't scale on either side of the house. Use ACME, EST or SCEP wherever your platforms support them.
- Manage public and private together: Two trust models shouldn't mean two consoles. A single certificate lifecycle management (CLM) platform gives you one inventory, one set of policies and one view of what's expiring.
Start with the certificates due to renew before February 10, 2027 (Sectigo's cutoff) or March 15, 2027 (Chrome's). Those are the ones most likely to come back without the clientAuth EKU they depend on.
How Sectigo helps
Sectigo's cloud-based Private CA issues and manages certificates for VPN and Wi-Fi authentication, device and workload identity, mTLS and API authentication, and developer and CI/CD environments, with the client authentication support those use cases need.
Sectigo Certificate Manager (SCM) then brings public and private certificates into one CLM platform: automated discovery across your environment, a complete inventory, policy enforcement, and automated issuance and renewal through ACME, EST, SCEP and APIs. It's simplicity at scale for every certificate you own, whichever hierarchy it comes from.
The bottom line
Chrome has drawn a clear line: public trust is for public websites. Organizations that treat that as a migration deadline will get through March 2027. Organizations that treat it as a design principle will come out with a faster, more controllable and more crypto-agile PKI.
Ready to bring certificate issuance in-house? Talk to Sectigo about assessing your clientAuth exposure and building a private PKI migration plan.