<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssl-Tls on CuraSec</title><link>https://curasec.metacog.co.kr/tags/ssl-tls/</link><description>Recent content in Ssl-Tls on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 24 Oct 2026 14:29:02 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/ssl-tls/index.xml" rel="self" type="application/rss+xml"/><item><title>eMudhra Exits SSL/TLS After 8 Intermediate CA Private Keys Recovered</title><link>https://curasec.metacog.co.kr/insights/2026-10-24-emudhra-to-exit-global-ssl-tls-business-after-8-intermediate/</link><pubDate>Sat, 24 Oct 2026 14:29:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-24-emudhra-to-exit-global-ssl-tls-business-after-8-intermediate/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Eight intermediate CA private keys were actually recovered — any certificate signed by those intermediates should be treated as potentially compromised. Audit your certificate inventory for eMudhra-issued certs and replace them now, before major browsers revoke trust and cause outages.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Compromised intermediate CA keys enable forged certificates for MITM attacks. Update TLS inspection rules to flag or alert on eMudhra-signed certificates in your environment, and confirm that CA distrust events are reflected in your trust stores and monitoring.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> A CA with recovered intermediate private keys will face browser distrust, which turns unexpired certificates into outages. Confirm this quarter whether your organization holds any eMudhra-issued certificates and initiate replacement before the distrust wave hits — and check if any vendors in your supply chain rely on them.&lt;/li>
&lt;/ul></description></item></channel></rss>