eMudhra says it is leaving the global SSL/TLS certificate business after a recent incident. What does that mean for existing certificate customers, and how should they plan for it?
eMudhra is exiting global SSL certificates. What should customers do?
Answers
Start with an inventory rather than assuming every certificate needs replacing today. Find certificates issued through eMudhra, including ones managed by hosting providers or automated deployment tools, and note their expiry dates and where they are installed.
Then check eMudhra's customer communications for the transition timeline and any renewal or revocation instructions. Pick an alternative issuer and test issuance and deployment before you need a renewal. An announcement about exiting the business does not, by itself, establish when every existing certificate stops working.
Reply to this answer
The incident is a separate concern from the business exit. Discussion focused on affected CA private keys reportedly having extremely small values, which would be a serious key generation failure. Revoking the affected CAs limits their continued use, but the response time doesn't answer how the weak keys got there or whether controls should have caught them earlier.
eMudhra said it revoked the affected CAs within 14 hours of discovery and that they had issued no end entity certificates. There was a challenge to that latter claim in the discussion, but not enough detail here to resolve it. I would check the incident disclosures and certificate records before drawing a conclusion about the scope.
Reply to this answer
Watch for changes from browser and operating system trust programs too. A certificate can still be within its validity period but stop working for some clients if a relevant CA loses trust. The exit announcement alone doesn't tell us whether or when that will happen.
Reply to this answer
This also raises a fair question about CA oversight. Audits and public incident reports are useful, but an audit result shouldn't be treated as proof that every key and process is sound. When choosing a replacement, look at the issuer's incident history, transparency, support and automation, not just the certificate price.
Reply to this answer
Add your answer
Answers are reviewed before publication.
r.439!sockettumbler:
Don't forget less visible endpoints such as mail gateways and appliances. Those can be easy to miss if the inventory only covers public websites.