Two tools, two questions
Certificate lifecycle management (CLM) keeps certificates valid. It asks: which certificates do we have, who owns them, when do they expire, and how are they renewed or revoked? A cryptographic bill of materials (CBOM) keeps an inventory of cryptography. It asks: which algorithms, keys, protocols and certificates are in use, where, and which of them are vulnerable to a quantum computer?
The two overlap on certificates and are often confused for that reason. They are complements, not substitutes.
What certificate lifecycle management does
A CLM programme, sometimes called PKI management, covers the life of each certificate: discovering certificates already deployed, requesting and issuing new ones, renewing before expiry, revoking compromised or retired ones, alerting owners, and enforcing issuance policy such as permitted CAs and key sizes.
Much of this is now automated. The ACME protocol (RFC 8555, March 2019) is "a protocol that a CA and an applicant can use to automate the process of verification and certificate issuance", with facilities for other functions "such as certificate revocation".[1] The ACME Renewal Information extension (RFC 9773, 2025) lets an ACME server suggest when clients should renew.[2]
CERT-In's guidelines place CLM inside cryptographic asset control. Best practice 8.4.2.2 says "certificate lifecycle management should include automated issuance, rotation, and revocation tracking".[3] In CERT-In's model, CLM is one practice that feeds the CBOM, not a replacement for it.
What a CBOM covers that CLM does not
A CBOM records cryptographic assets wherever they live. CERT-In's Table 9 sets per-asset elements for four types: algorithms, keys, protocols and certificates.[3] Certificates are one of the four. The other three are where CLM is usually blind:
- Protocol configuration. The TLS version and cipher suites a server negotiates decide its key exchange. A renewed certificate does not change them.
- Keys without certificates. Symmetric data-encryption keys, signing keys used directly by applications, SSH keys and keys exported from HSMs. CycloneDX models these as
related-crypto-material, with types such asprivate-key,secret-keyandtoken.[4] - Algorithms in code. An RSA call or ECDSA token signature hard-coded in an application.
- Certificates outside CLM's reach. Certificates embedded in firmware, appliances or supplier packages, or issued by a private CA that the CLM platform does not connect to.
A CBOM also records relationships. CycloneDX separates a library that provides an algorithm from an application that depends on it,[4] so you can trace an RSA key from the certificate to the service that uses it.
Shorter certificate lifetimes: CA/Browser Forum Ballot SC-081
The CA/Browser Forum passed Ballot SC-081v3 on 11 April 2025, with 25 certificate issuers and 4 certificate consumers voting yes and none against.[5] It cuts the maximum validity of publicly-trusted TLS server certificates from 398 days to 47 days in steps, and shortens how long a CA may reuse earlier validation data. The schedule is now in Baseline Requirements §6.3.2 and §4.2.1.[6]
| Certificate issued on or after | Maximum validity | Domain/IP validation data reuse | Subject identity data reuse |
|---|---|---|---|
| (before 15 Mar 2026) | 398 days | 398 days | 825 days |
| 15 March 2026 | 200 days | 200 days | 398 days |
| 15 March 2027 | 100 days | 100 days | 398 days |
| 15 March 2029 | 47 days | 10 days | 398 days |
Two limits are worth noting. First, the Baseline Requirements "only address Certificates intended to be used for authenticating servers accessible through the Internet".[6] Internal PKI, private mTLS, code signing and S/MIME are outside this schedule. Second, the ballot governs certificate lifetime, not the algorithms behind the rest of the connection.
Why shorter lifetimes help PQC, and where they stop
At 47 days, a public certificate is replaced around eight times a year. That forces fully automated renewal, and automated renewal is exactly what an algorithm change needs. When a post-quantum certificate profile becomes available and accepted for a given use, an automated fleet can move at its next renewal instead of waiting out a year-long certificate. The same machinery has already handled an algorithm retirement: the Baseline Requirements sunset all remaining SHA-1 use in certificates and CRLs from 15 September 2026.[6]
Fast rotation does not tell you what else is in use. The most urgent quantum risk for TLS, recorded traffic decrypted later, sits in the key exchange, which is set by protocol configuration rather than by the certificate (see hybrid X25519MLKEM768 in TLS). Nor does rotation reach the keys, code paths and private-PKI certificates listed above. A perfectly run CLM programme can renew every certificate on time while the estate still depends on RSA and elliptic-curve cryptography elsewhere.
CLM makes it cheap to change certificates. A CBOM tells you which of the things you need to change are certificates, and which are not.
How they work together
CLM data is a strong input to a CBOM. CERT-In's certificate elements (subject and issuer names, validity dates, signature algorithm reference and subject public key reference) are fields a CLM inventory already holds.[3] CycloneDX 1.7 goes further, with a certificateState array (pre-activation, active, suspended, deactivated, revoked, destroyed) and dates such as revocationDate, so lifecycle status can be carried into the CBOM.[4][7]
In the other direction, the CBOM tells the CLM team what to change. It shows which certificates carry RSA-2048 or ECDSA keys, which services depend on them, and which CAs and clients would need to accept a new algorithm. That turns a renewal calendar into a migration plan.
A practical split: run CLM to keep certificates valid and automated; feed its inventory into the CBOM each cycle; use the CBOM to find the non-certificate assets and to rank what moves first.
| Certificate lifecycle management | CBOM | |
|---|---|---|
| Primary question | Is every certificate valid, owned and renewed on time? | Which cryptography is in use, where, and how exposed is it? |
| Unit of record | A certificate (and usually its private key) | An algorithm, key, protocol or certificate, linked to the components that use it |
| Core actions | Discover, issue, renew, revoke, alert, enforce issuance policy | Inventory, classify, link dependencies, prioritise, evidence progress |
| Typical sources | CA records, certificate stores, endpoint scans, automation clients | Code and binaries, configuration, network handshakes, key stores and HSM exports, supplier CBOMs, CLM data |
| Update cadence | Continuous; driven by expiry dates | At every change to software, configuration or keys; CERT-In asks for at least quarterly review[3] |
| Usually misses | Key exchange settings, symmetric keys, keys not bound to a certificate, cryptography in code | Operational control: it records state but does not issue or renew anything |
| Standards | ACME (RFC 8555), ARI (RFC 9773), CA/B Forum Baseline Requirements | CERT-In Table 9; CycloneDX 1.6/1.7 cryptoProperties |
How KavachQ helps
KavachQ does not replace your certificate lifecycle tooling. It covers what sits around it:
- Discover finds certificates from live TLS probes, keystores, code and configuration, including ones no CLM tool was told about.
- Seal's monitoring re-scans on a schedule and alerts on expiring certificates and on drift.
- Migrate includes ACME among its change packs for TLS terminators, with a named approver and a tested rollback.