eMudhra Exits Global TLS Certificates After CA Key Compromise

| 2 Min Read
eMudhra is replacing customer certificates with Sectigo’s as enterprises assess trust chains, Java systems and other services that may not follow browser updates.

eMudhra’s departure from the global SSL/TLS certificate market turns a certificate incident into a broader infrastructure task: customers need to identify every system that trusts the affected keys, then move services onto a dependable replacement path.

The Indian digital trust company’s board chose to “voluntarily withdraw from the global SSL/TLS certificate business” after private keys for eight intermediate certificate authorities were compromised. eMudhra also cited rising complexity and costs tied to data sovereignty and compliance. Chairman V Srinivasan said scrutiny amplified on social media had become disproportionate to TLS’s role in the company’s business.

Replacement certificates and a transition window

eMudhra is offering certificates issued by Sectigo to its customers and says it will replace affected certificates at no charge through its partners. CertiNext customers can request them in their accounts; other customers can contact eMudhra support. Sectigo had not responded to a request for comment.

The company says its G1 root certificates remain active and supported during the transition. It will continue providing revocation and certificate status services until every certificate it issued expires or is replaced.

That interim support may help prevent immediate service interruptions, but it doesn’t settle the longer-term trust question. Gartner principal analyst Niyati Daftary advised treating the G1 roots as a bridge, with a firm deadline and documented plan for moving critical services to an independent, fully trusted certificate authority where timelines permit. She also urged security teams to inventory the issuing authorities, certificate chains, cross-signing, revocation systems and browser trust status in their third-party risk reviews.

Security Brigade co-founder and CTO Yash Kadakia made a related point: switching to another root managed by the same company may leave concerns about trust and governance unresolved. “The last thing organisations need is to migrate twice,” he said.

Browser updates won’t reach every trust store

Replacing a website certificate may leave less visible systems exposed. IDC research director Sakshi Grover pointed to Java keystores, language runtimes, container images, mutual TLS setups, proxies, load balancers, VPNs, security appliances and embedded devices. These components can maintain separate trust stores and receive updates on different schedules from browsers and operating systems.

Google said it found no certificates chaining to the compromised intermediates in Certificate Transparency logs before blocking them. Grover said that offers reassurance for organizations that enforce Certificate Transparency, while cautioning that some applications and devices don’t. An attacker would also need a position that lets them intercept traffic, making the remaining risk limited and targeted, she said.

Java presents a specific patching concern. Azul said certificate revocation checks are disabled by default in Java, so an unpatched JDK may continue accepting a forged certificate signed with a compromised intermediate if that chain remains trusted. The vendor has updated Azul Zulu Builds of OpenJDK and Azul Prime to add the eight certificates to the JDK’s blocked-certificate list.

Grover’s recommended starting point is to map where trust decisions happen outside browsers and operating systems, giving priority to systems exposed to external connections and mutual TLS endpoints. Teams should then check whether each system can be updated to distrust the affected intermediate certificate or public key.

Chrome’s October 27 trust-store deadline

Mozilla removed emSign ECC Root CA – G3, which signed the eight compromised intermediates, from its trust store. Google said removal from the Chrome Root Store was expected to reach all devices on the morning of October 27, Pacific time. It urged website operators with certificates chaining to that root to acquire and install replacements immediately to avoid breakage.

Daftary said companies may know the reseller that supplied a certificate without knowing which certificate authority or root anchors its trust. That gap can create a “fourth-party risk” across many services. For security leaders, the practical takeaway is to map the full certificate chain and its dependencies now; a browser update alone won’t account for every application, device or service that makes its own trust decisions.

The article originally appeared on ComputerWorld.

Source: Richard Davis · www.csoonline.com

Comments

Please sign in to comment.