The spreadsheet everyone starts with
Most teams track certificates in a spreadsheet at first: one row per certificate, with the name, the expiry date, where it is installed and who looks after it. It is a sensible start. It is free, everyone can read it, and it is far better than nothing.
The trouble is that a spreadsheet records what someone knew on the day they typed it. Certificates change on their own schedule, and the sheet does not notice.
Five reasons it stops matching reality
It only knows what someone typed
A new certificate appears whenever someone sets up a service, a vendor installs an appliance or a cloud service creates one. None of these add a row. The sheet lists the certificates you already knew about, which are rarely the ones that cause outages.
The expiry date is not the deadline
The sheet shows the day the certificate expires. The real deadline is earlier: the last day you can renew, install and check it with time to fix a problem. For a certificate on an appliance that needs a change window, that can be weeks before expiry.
It does not know what is actually served
A row can say a certificate was renewed while the server still presents the old one. Unless someone connects to the endpoint and checks, the sheet and the service quietly disagree. We describe this failure in how to stop certificate expiry outages.
People move on
The owner column holds names. Names change teams, go on leave and leave the company, and reminders based on the sheet go with them.
Renewals multiply
A spreadsheet can keep up with one renewal a year per certificate. Public certificates now last at most 200 days, falling to 100 in March 2027 and 47 in March 2029. At 47 days, a certificate renewed two thirds of the way through its life is renewed about twelve times a year, so 300 certificates mean about 3,600 updates to the sheet. The arithmetic is in certificate lifetimes are falling to 200, 100 and 47 days.
The audit problem
If you are asked to show your certificates, a spreadsheet proves only that someone wrote them down. For EU financial entities, Commission Delegated Regulation (EU) 2024/1774, Article 7(4), asks for a register of certificates kept up to date. A register that is built from discovery and updated by each renewal is much easier to defend than one updated by hand. We look at the regulations in more detail in what certificate lifecycle management is.
What to keep when you move on
The spreadsheet holds knowledge that no scanner can find, and it is worth keeping:
- Ownership. Which team owns each service, and who to call at night.
- Context. Why a certificate exists, which customer or system depends on it, and any special installation steps.
- Constraints. Change windows, appliances that need a manual step, and partners that pin a certificate.
Move these into whatever replaces the sheet, attached to the discovered certificates. Then let the data that changes by itself (expiry, issuer, where it is served) come from automation instead of typing.
A practical way to move on
- Run discovery across your public names and internal networks, and compare the result with the sheet. Expect certificates the sheet does not have.
- Assign a team owner to every certificate found, using the sheet as a starting point.
- Automate renewal and installation for the certificates where that is easy, which is usually most of them.
- Monitor the certificate each endpoint serves, and alert on that instead of on the sheet.
- Keep the sheet read-only for a few months as a cross-check, then retire it.
Where clm.mt fits
We make clm.mt, so we have an interest here. clm.mt keeps the inventory for you: each certificate with its owner, issuer, expiry and where it is deployed, with expiry views and a filtered CSV export when someone still wants a spreadsheet. Renewals and deployments update it as they happen, and network and Certificate Transparency discovery, which can add certificates you did not list, is in preview.
The integrations page shows what is supported and what is in preview, the docs explain setup and pricing lists the plans.
Sources
- Commission Delegated Regulation (EU) 2024/1774, Article 7(4).
- CA/Browser Forum, Ballot SC-081v3, April 2025.