Seitenlogo
Seitenlogo
Seitenlogo

47-Day TLS Certificates and Industrial PKI: How OT Teams Should Prepare

47-Day TLS Certificates and Industrial PKI: How OT Teams Should Prepare

47-Day TLS Certificates and Industrial PKI: How OT Teams Should Prepare

47-Day TLS CertificateHow OT Teams Should Prepare
Shieldworkz logo

Team Shieldworkz

Publicly trusted TLS certificates will be capped at 47 days from March 15, 2029, and the step that hurts first arrives on March 15, 2027, when the cap falls to 100 days. Most of what runs inside a plant sits on private PKI that this rule never touches. The exposure is at the edges: the gateways, portals and vendor connections where your OT network meets public trust. 

The schedule, verified against the ballot 

A recent headline claimed TLS lifespans will shrink to 47 days by 2029. It's accurate, with one detail the headline skips: the drop happens in three steps, not one. The CA/Browser Forum, the body where certificate authorities and browser makers set the rules, passed Ballot SC-081v3 on April 11, 2025. Apple proposed it, Sectigo endorsed it, and no CA voted against it. 

Effective date

Max certificate validity

Max domain-validation reuse

Renewals per year, per certificate*

Before March 15, 2026

398 days

398 days

about 0.9

March 15, 2026 (in effect)

200 days

200 days

about 1.8

March 15, 2027

100 days

100 days

about 3.7

March 15, 2029

47 days

10 days

about 7.8

Our arithmetic: 365 divided by the maximum validity. In practice you renew earlier. Let's Encrypt advises renewing about two-thirds of the way through a certificate's life, which puts a 47-day certificate on a roughly 31-day cycle. 

Two details matter more than the headline number. First, the cap applies to certificates issued on or after each date, so what you already hold runs to its original expiry. Second, the domain-validation reuse window shrinks to 10 days by 2029. That means a CA can no longer lean on a domain check you passed months ago. Validation itself has to be automated, not only the renewal. 

One caution if you're reading older material: Google's 2023 suggestion of a flat 90-day maximum was never adopted. The schedule above is the binding one. 

What has changed since the ballot passed 

The 47-day number gets the attention, but three other moves are shaping how the transition lands in practice. 

March 15, 2027 is the date to plan around. It is the 100-day step, so renewals roughly double again. It is also the date Chrome's root program requires every newly issued public TLS certificate to carry the server-authentication usage only (more on that below). Two changes on one day is how outages get scheduled. 

Let's Encrypt is running ahead of the mandate. Its own announcement lays out the timeline. On May 13, 2026 its opt-in tlsserver profile began issuing 45-day certificates. On February 10, 2027 the default profile moves to 64-day certificates with a 10-day authorization reuse period. On February 16, 2028 it moves to 45 days with a 7-hour reuse period. If your ACME client renews on a hardcoded 60-day cron job, Let's Encrypt says that stops being enough. It recommends ACME Renewal Information (ARI), or renewing at roughly two-thirds of the certificate's lifetime. It is also pushing a new validation method, DNS-PERSIST-01, so the DNS record that proves domain control no longer has to change at every renewal. 

Client authentication is leaving public certificates. Chrome Root Program Policy v1.8 (updated February 5, 2026) removes the clientAuth extended key usage from publicly trusted TLS certificates in two stages. New subordinate CAs had to be server-auth-only from June 15, 2026. New leaf certificates must be server-auth-only from March 15, 2027. Earlier coverage gave June 2026 as the cutoff for leaf certificates, and that date has since been pushed back, so check your CA's own notice. DigiCert, for one, says it can include client authentication until March 1, 2027. Certificates issued before the cutoff stay valid until they expire. Let's Encrypt has already stopped issuing them. 

The practical read: if anything in your estate uses a public certificate for mutual TLS, that design has an end date, and it is earlier than 2029. 

What the rule covers, and what it doesn't 

This is where a lot of coverage goes wrong for OT audiences. Ballot SC-081v3 governs publicly trusted TLS certificates, meaning certificates that chain to a root in browser and platform trust stores. Private PKI, internal CAs and self-signed certificates are outside it. Several CAs and PKI vendors say so plainly, and the CA/Browser Forum has no authority over a CA that only your own systems trust. 

That is good news for the controller layer and a trap for everything around it, because plants quietly accumulate public certificates in places nobody listed. 

Certificate in your estate

Covered by the 47-day cap?

What to check

Public website, API or portal fronting OT data (historian dashboards, asset portals)

Yes

Who renews it, and is it automated?

Remote-access gateway or VPN portal using a public certificate

Yes

Renewal path, and whether the gateway supports ACME or API-driven install

Browser-facing HMI, gateway or appliance interface with a public certificate

Yes

Can the device take a new certificate without a maintenance window?

Public certificate used for client authentication or mutual TLS

Yes, and the client-auth usage is being removed

Move to a private CA before March 15, 2027

Vendor cloud or SaaS endpoints your OT systems call

Yes, but renewed by the vendor

Ask for their renewal automation evidence

Internal CA certificates for HMIs, historians, jump hosts

No

Lifetime is your policy decision

OPC UA application instance certificates (self-signed or CA-issued)

No

Trust lists, expiry alarms, renewal procedure

Self-signed device certificates

No

Expiry dates nobody recorded

A fair summary: you won't be forced to move a PLC to 47-day certificates. You will be forced to find every public certificate your plant depends on, and to prove that something other than a person renews it. 

Where OT teams will actually feel it 

IT can restart a web server at 2 a.m. and move on. OT usually can't. That difference is why shorter lifetimes are a different kind of problem on the plant side, even when the technical change is identical. 

Remote access and vendor connectivity. Support portals, jump hosts and VPN gateways are the most common place a public certificate meets a plant. They are also the systems you least want failing during an incident, when the vendor engineer needs in and the certificate lapsed last night. Industry commentary on shrinking lifespans has pointed to industrial control systems among the places a lapsed certificate can take offline, because trust between connected machines simply breaks. 

The DMZ. Reverse proxies, historian replicas and data-diode-adjacent services that publish plant data to the business network often hold public certificates. These are your best candidates for proper ACME automation, because the DMZ is the one zone that usually has the outbound reach a CA validation needs. 

Devices that can't renew themselves. Many embedded HTTPS interfaces accept a certificate through a manual upload and a service restart. At one renewal a year, that was tolerable. At eight, it becomes a standing maintenance job. A certificate that takes a change request and a window to replace is, in practice, a certificate that will expire. 

Segmented networks. ACME clients need to reach the CA and prove domain control through DNS or HTTP. In a properly segmented plant, the system that holds the public certificate often cannot do either. With domain-validation reuse falling to 10 days, you can no longer paper over that gap with a validation done months earlier. 

Time. Certificates are only as reliable as the clocks checking them. Devices that boot without a trustworthy time source, or drift between zones, reject perfectly valid certificates. Short lifetimes shrink the margin for that kind of error. 

Mutual TLS built on public CAs. This one is the quiet risk. If a partner connection or a data pipeline authenticates clients with a public certificate, new issuance loses the client-auth usage from March 15, 2027. The connection doesn't fail on that date. It fails at the next renewal, which is easy to lose track of. 

A design principle worth adopting now: terminate public trust at the edge, in the DMZ, on infrastructure you can automate, and keep everything behind it on a private CA you control. The fewer public certificates inside a zone, the smaller the problem. 

Industrial PKI and OPC UA: the part the mandate doesn't write for you 

Inside the plant, trust is mostly your own. Every OPC UA application instance carries an X.509 certificate, and each application keeps a trust list of the peers it accepts. The OPC Foundation's security guidance notes that a certificate has a lifetime and will eventually need replacing, and that administering trust lists by hand becomes too burdensome as servers and clients multiply. It also advises against using a commercial CA for this in most cases, since the company, not a third party, should decide which applications are trusted. 

So the 47-day cap doesn't reach OPC UA. But the OPC Foundation has already moved in the same direction on its own terms. Its GDS guidance describes a Global Discovery Server that can manage certificate deployment, trust lists, CAs and revocation lists, and notes that certificate lifetimes configured in a GDS are typically short, around one to three months, to keep revocation lists small. The specification also defines a certificate expiration alarm type, so an expiring certificate can raise an alarm on the server before it breaks a connection. 

That gives OT teams a useful frame. The public rule is not forcing you to shorten private lifetimes. It is showing you what a certificate estate looks like when renewal is a routine, automated event. If your OPC UA estate still depends on someone remembering a trust-list update, the same weakness will show up whether or not a CA/Browser Forum ballot exists. 

A workable way to set lifetimes inside the plant is to tier them by what the certificate protects and what can renew it: 

  • Services that can renew automatically over ACME or a GDS: short lifetimes, measured in weeks or a few months. 

  • Controllers and field devices that need a manual or on-site step: longer lifetimes, but with a recorded owner, an expiry alarm and a rehearsed replacement procedure. 

  • Assets that cannot reach any CA, including mobile or disconnected equipment: a documented offline renewal process, agreed with the vendor before the old certificate expires. 

One PKI vendor suggests roughly this split, with 47-day certificates for private TLS using ACME, three to six months for TPM-protected device certificates, and one to three years for certificates bound to an offline physical device. Treat those as starting points, not rules. The right number is whatever your renewal process can reliably meet. 


A preparation plan for OT teams 

With March 15, 2027 as the first hard date, a sensible plan runs in this order. The early steps cost little and make every later step cheaper. 

  1. Build a certificate inventory that includes OT. List every certificate by issuer, expiry date, extended key usage, host, owner and renewal method. Include the DMZ, remote-access platforms, historians, gateways and anything a vendor installed. For public certificates, search Certificate Transparency logs for your domains. They record every publicly trusted certificate issued for them, including ones nobody told you about. 

  2. Sort public from private. Mark each certificate by trust model. Anything that doesn't need to be trusted by an outside browser or partner is a candidate for your own CA. 

  3. Find every client-authentication dependency. Look for the clientAuth usage on public certificates and confirm real use from handshake logs or partner configuration. Plan the move to a private CA before March 15, 2027, and before each affected certificate's next renewal. 

  4. Move internal-only services to private PKI. This shrinks the number of certificates the public schedule governs, and it puts the lifetime back under your control. 

  5. Automate what must stay public. Put ACME-based issuance in the DMZ. Enable ARI or renew at about two-thirds of lifetime. Test against a 45-day certificate now, not just a 100-day one. Decide how domain validation will work from a segmented network, and watch DNS-PERSIST-01 as it becomes available. 

  6. Give manual-only devices a front. Where an appliance can't automate, place a DMZ reverse proxy in front of it so public trust ends on something you can renew, or schedule its replacement with the vendor. 

  7. Add expiry alerting that doesn't depend on the failing system. Alert at several thresholds from a separate monitoring path. Use OPC UA expiry alarms where servers support them. 

  8. Rehearse an expiry. Let a non-critical certificate lapse in a test cell and time the recovery. Include time synchronization and a rollback in the runbook. 

  9. Put it in procurement. For new equipment and remote-access services, ask whether the product supports ACME or API-driven certificate installation, whether it can import a CA-signed certificate, and what its default certificate lifetime is. Our view is that this belongs next to patching and logging in the security requirements for any new purchase. 

  10. Assign a named owner to every certificate. Tie renewals to change management so the replacement is a planned event with an approver, not a ticket someone finds the night before. 

One more option for resilience: configure a second CA. Under a 47-day ceiling, a CA outage leaves no time for a manual fallback, so a tested alternative issuer is cheap insurance. 

How Shieldworkz can help 

In most plants, certificate risk is an asset-visibility and architecture problem long before it is a PKI problem. You can't automate renewal for a certificate you don't know exists, and you can't move a dependency off public trust if no one has drawn where it sits. 

Shieldworkz is an end-to-end industrial OT cybersecurity company, covering products, services and solutions across SCADA, OT and IoT environments. For this topic, that typically means helping teams with three things: 

  • Mapping the OT assets, remote-access paths and DMZ services that depend on certificates, so the inventory in step one reflects the plant, not just the IT estate. 

  • Reviewing network segmentation, remote-access design and trust relationships, so public certificates end at the edge and private PKI governs the inside. 

  • Building certificate renewal and expiry response into OT incident readiness and change management, so a lapsed certificate is a rehearsed event. 

If you'd like a second pair of eyes on how your plant will handle the 100-day step in March 2027, talk to the Shieldworkz team. 

Frequently asked questions 

When do TLS certificates become 47 days? On March 15, 2029. The maximum validity falls to 200 days on March 15, 2026 (already in effect), to 100 days on March 15, 2027, and to 47 days on March 15, 2029. 

Does the 47-day rule apply to OT and ICS equipment? Only where that equipment uses publicly trusted TLS certificates. Private PKI, internal CAs and self-signed certificates are outside the rule, which covers most controller-level and OPC UA certificates. Public certificates on remote-access gateways, DMZ services and browser-facing interfaces are covered. 

Do OPC UA certificates have to be renewed every 47 days? No. OPC UA application instance certificates are typically self-signed or issued by a private CA, so the public cap doesn't apply. Their lifetime is your decision, and the OPC Foundation's own GDS guidance suggests short lifetimes where renewal is automated. 

Will my existing certificates stop working when the limits change? No. Each limit applies to certificates issued on or after its effective date. Certificates you already hold remain valid until they expire. 

What happens to mutual TLS that relies on public certificates? New public certificates lose the client-authentication usage from March 15, 2027 under Chrome Root Program Policy v1.8, and some CAs cut over earlier. Move client-authentication certificates to a private CA before the next renewal. 

Why is domain-validation reuse changing? Because stale validation weakens the guarantee a certificate gives. The reuse window falls from 398 days to 10 days by 2029, which means domain control has to be proven almost every renewal cycle. 

Additional resources:

Comprehensive Guide to Network Detection and Response NDR in 2026 here
NERC CIP-015 Internal Network Security Monitoring Readiness Checklist for Electric Utilities here
OT SOC Foundational Guide here
Managed SOC Service here

Wöchentlich erhalten

Ressourcen & Nachrichten

Erfahren Sie, wie unsere branchenführenden OT-Security-Lösungen kritische Sicherheitsherausforderungen gemäß KRITIS-Anforderungen bewältigen

Dies könnte Ihnen auch gefallen.

BG image

Jetzt anfangen

Skalieren Sie Ihre CPS-Sicherheitslage

Nehmen Sie Kontakt mit unseren CPS-Sicherheitsexperten für eine kostenlose Beratung auf.

BG image

Jetzt anfangen

Skalieren Sie Ihre CPS-Sicherheitslage

Nehmen Sie Kontakt mit unseren CPS-Sicherheitsexperten für eine kostenlose Beratung auf.

BG image

Jetzt anfangen

Skalieren Sie Ihre CPS-Sicherheitslage

Nehmen Sie Kontakt mit unseren CPS-Sicherheitsexperten für eine kostenlose Beratung auf.