A plain definition
Certificate lifecycle management (CLM) is the work of looking after every certificate an organisation depends on, from the moment it is needed to the moment it is replaced or no longer used. It covers TLS certificates on websites and APIs, but also those on mail servers, VPNs, load balancers, databases and internal services.
NIST’s practice guide SP 1800-16, TLS Server Certificate Management describes this work for large organisations and how to prevent, detect and recover from certificate incidents. You do not need to be large for the same ideas to apply.
The stages
- Discover. Find the certificates that exist, including the ones nobody wrote down.
- Inventory and own. Record each one with its names, issuer, expiry, location and a team that owns it.
- Issue. Request certificates from the right CA, public or internal, with the right names and key type.
- Deploy. Install the certificate and key where they are used, and reload the service.
- Verify. Check that each endpoint serves the new certificate and a correct chain.
- Renew. Repeat issue, deploy and verify well before expiry.
- Replace or revoke. Replace certificates early when a key may be exposed or a CA must be changed, and revoke them when needed.
A missed step anywhere ends the same way: a service presents an expired or wrong certificate and clients refuse to connect. We cover the common causes in how to stop certificate expiry outages.
Why it is getting harder
Public TLS certificates now last at most 200 days. That drops to 100 days in March 2027 and 47 days in March 2029, under the CA/Browser Forum schedule we explain in certificate lifetimes are falling to 200, 100 and 47 days. Every stage above now happens several times a year for each certificate, not once.
What regulation says
Two EU laws are worth knowing, and it helps to be exact about what they say.
- NIS2. Directive (EU) 2022/2555, Article 21(2)(h), asks essential and important entities for “policies and procedures regarding the use of cryptography and, where appropriate, encryption”. It does not mention certificates by name, but certificates are how most of that cryptography is used in practice.
- DORA. For financial entities, Commission Delegated Regulation (EU) 2024/1774, Article 7, is specific. Paragraph 4 requires a register of all certificates and certificate-storing devices, at least for ICT assets supporting critical or important functions, kept up to date. Paragraph 5 requires the prompt renewal of certificates in advance of their expiration.
Whether these apply to you is a legal question for your own advisers. If they do, an up-to-date inventory and a renewal process you can show are the evidence you will be asked for.
When you need a CLM tool, and when you do not
You may not need one. If you run a few websites on servers you control and an ACME client such as certbot already renews them, keep that. Add monitoring of what each site serves and you have covered most of the risk.
The signs that scripts and a calendar are no longer enough:
- You cannot say with confidence how many certificates you have.
- Certificates sit on appliances, cloud load balancers or Windows servers, where a simple ACME client does not run.
- Several teams or customers each manage their own, in different ways.
- You use more than one CA, for example a public CA and an internal one.
- Someone asks you to prove your inventory and renewals, such as an auditor, a customer or a regulator.
- You have had an outage from an expired certificate in the last year.
If several of these are true, a single place that discovers, tracks, renews, deploys and checks will save you time and outages.
Where clm.mt fits
We build clm.mt, so this section is about our own product. It covers the stages above: inventory with owners, renewal through ACME and other CAs, deployment to servers and services, and a check of what each endpoint serves. Discovery of certificates by network scan and Certificate Transparency is in preview. Agents run on Linux or Windows inside your network, and you can use the hosted service, which is in pilot, or run the licensed server yourself.
See the integrations page for which CAs and targets are supported and which are in preview, the docs for setup and pricing for the plans.
Sources
- NIST, SP 1800-16, Securing Web Transactions: TLS Server Certificate Management, June 2020.
- Directive (EU) 2022/2555 (NIS2), Article 21(2)(h).
- Commission Delegated Regulation (EU) 2024/1774, Article 7(4) and 7(5).
- CA/Browser Forum, Ballot SC-081v3, April 2025.