Schutz IT

Certificate Lifecycle Management for 47-Day TLS Certificates: An Automation Playbook

Schutz IT certificate and identity security

TLS certificates used to be something a team renewed once a year, usually after a calendar reminder and a short scramble. That rhythm is ending. Under the CA/Browser Forum's ballot SC-081, the maximum lifetime of a publicly trusted TLS certificate has already dropped to 200 days, falls to 100 days in March 2027 and reaches 47 days in March 2029. For most organisations that means renewals will run roughly eight times more often than they do today, which is why teams working with Schutz IT now treat certificate lifecycle management as an operational discipline rather than an occasional admin task.

This article sets out a practical playbook: what changes, where certificate programmes usually break, and how to build automation that keeps pace without adding headcount.

Why Shorter Certificate Lifetimes Change the Operating Model

A one-year certificate gives a team plenty of slack. If a renewal is missed, someone usually notices in the final weeks and fixes it by hand. With a 47-day certificate there is no slack. A renewal that depends on a person remembering, raising a ticket and copying files to a server will eventually be missed, and a missed renewal means an expired certificate, a browser warning and, in the worst case, a production outage.

The same ballot also shortens how long domain validation can be reused, eventually to just ten days. In practice this removes the option of validating a domain once and issuing against it for months. Validation has to be automated as well.

The real shift is therefore from "managing certificates" to "managing the system that manages certificates". The certificate itself becomes disposable; the inventory, the policy and the automation pipeline are what need care.

Step 1: Build a Complete Certificate Inventory

Every certificate programme that struggles has the same root cause: nobody knows how many certificates exist or where they are installed. Public web certificates are only part of the picture. There are internal TLS certificates on load balancers and APIs, device certificates issued through Intune or JAMF, code-signing certificates, S/MIME certificates and machine identities inside containers and service meshes.

A useful inventory records, for each certificate:

  • the issuing CA and certificate profile
  • the host, service or device it protects
  • the expiry date and renewal method
  • the business owner who is contacted when something fails

Discovery tools that scan networks, query CA logs and read cloud key vaults can build the first version. After that, the inventory must be kept current automatically; a spreadsheet updated by hand is out of date within weeks.

Step 2: Automate Enrolment and Renewal with Standard Protocols

Once you know what you have, the next job is to take people out of the renewal loop. Three protocols cover most environments:

  • ACME (Automated Certificate Management Environment) for web servers, ingress controllers and cloud load balancers
  • EST (Enrollment over Secure Transport) and SCEP for network equipment and managed devices
  • MDM integrations such as Microsoft Intune and JAMF for laptops and mobile devices

The aim is simple: a certificate should be requested, validated, installed and renewed without a human touching it. People should only be involved when something fails, and that failure should raise an alert well before expiry. If you are still deciding whether to run your own CA or hand the infrastructure to a provider, our earlier comparison of managed PKI versus an in-house CA walks through the trade-offs.

Step 3: Separate Public Trust from Private Trust

Not every certificate needs to come from a public CA. The new lifetime limits apply to publicly trusted TLS certificates. Internal services, devices and workloads that never face the open internet can be issued from a private CA, where your own policy sets the lifetimes, profiles and revocation rules.

Moving internal workloads to a private or cloud-hosted CA reduces the volume of public certificates you have to manage under the new rules, and gives you more control over the rest. The decision between hosting that CA on-premises or consuming it as a service is covered in detail in this guide to cloud PKI versus an on-premises CA.

Step 4: Connect Certificates to Your Identity Strategy

Certificates are identities. A device certificate proves which laptop is connecting; a client certificate proves which service is calling an API. That makes certificate programmes part of the wider identity and access conversation, not a separate silo.

This is most visible in authentication. Certificate-based authentication and FIDO2 passkeys both rely on public key cryptography, and both are among the passwordless authentication methods organisations are now rolling out to staff and customers alike. Teams that design PKI and customer identity together avoid building two separate trust models that later have to be reconciled. If customer-facing sign-in is on your roadmap, plan the key management, device trust and recovery processes alongside the CIAM platform choice rather than after it.

Step 5: Monitor, Report and Rehearse Failure

Automation reduces risk but does not remove it. ACME clients break after operating system upgrades, firewall changes block validation, and a CA can have an incident that forces mass replacement. A mature programme plans for these events:

  • Expiry monitoring that is independent of the renewal tooling, so a broken pipeline is noticed
  • Dashboards showing certificates by owner, CA, algorithm and days to expiry
  • Crypto-agility tests that prove you can replace every certificate from one CA within a set number of hours
  • Runbooks for revocation and emergency re-issuance

Crypto-agility matters for another reason too. Post-quantum algorithms are being standardised now, and the organisations that can rotate certificates quickly today will be the ones able to change algorithms smoothly later. Our enterprise PKI planning guide explains how to fold that requirement into a multi-year roadmap.

A Realistic Timeline

For a mid-sized organisation, a workable plan looks like this:

  1. Months 1–2: discovery and inventory, owner assignment, policy draft
  2. Months 3–5: ACME and EST automation for the highest-volume certificate types; move internal workloads to a private CA
  3. Months 6–9: device and MDM integration, monitoring and dashboards, first crypto-agility test
  4. Ongoing: quarterly reviews, preparation for the 100-day limit in 2027 and the 47-day limit in 2029

Starting now leaves time to fix problems while lifetimes are still at 200 days, rather than discovering them when renewals are happening every few weeks.

Final Thoughts

Shorter certificate lifetimes are not a reason for alarm, but they do end manual renewal as a viable approach. The organisations that cope best will be the ones that inventory everything, automate enrolment through standard protocols, keep private trust separate from public trust and connect certificates to their broader identity strategy.

If you would like a review of your current certificate estate or a roadmap for automation, please contact the Schutz IT team.