There are reports that IdenTrust plans to revoke TLS certificates issued over a long period, potentially leaving organizations with a lot of certificates to replace. How can we work out what's affected and prioritize the replacements?
How should we prepare for the reported IdenTrust certificate revocations?
Answers
Start with an inventory of certificates actually being served, not just the renewal spreadsheet. Check each known hostname with a TLS client using the right server name, then inspect the certificate issuer and expiry. Make sure the checks cover every relevant endpoint, including different load balancer addresses where applicable.
That will help find deployed IdenTrust certificates, but it won't prove which ones are subject to this revocation. Compare the results against the affected issuance window and certificate details in the issuer's notice. A scan also won't catch an endpoint you didn't know to check.
Reply to this answer
Get the actual notice from the issuer or certificate provider before scheduling the work. The reported deadlines differ, so confirm the affected certificates, date, time zone, and replacement process rather than relying on a forwarded summary.
If the certificates are held by a customer or another team, ask them to check for the notification too. Don't assume it reached the people who manage the endpoints.
Reply to this answer
I'd tackle public-facing services first, especially critical ones, then work through the rest of the affected inventory. For each replacement, make sure it gets installed on the right load balancers and test what clients actually receive afterward.
Reply to this answer
This is a good reason to automate certificate issuance and deployment where possible. Automation won't identify the scope of this particular notice for you, but having a tested replacement process makes a large, urgent rotation less painful.
Mivquelo.8s:
Shorter certificate lifetimes aren't established as the cause here. They can still encourage teams to build a regular renewal process.
Reply to this answer
Add your answer
Answers are reviewed before publication.
9r!gobletlatch_284:
Check the full chain after replacing certificates too. A correct leaf certificate can still be served with a missing or wrong intermediate.