← SSL.com cases
Bugzilla #2071491 Ca Certificate Compliance Incident Self Reported Incident Validation Issue Mass Revocation Readiness

SSL.com incident report: MPIC was not performed for some DCV paths, affecting 2,700 TLS certificates

ASSIGNED SSL.com
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

SSL.com opened this case to disclose an incident found during its annual WebTrust audit. The audit identified that MPIC corroboration evidence was missing for DCV performed on 4 sampled TLS certificates, and SSL.com later determined the issue affected 2,700 unexpired, unrevoked TLS certificates. SSL.com said an alternate DCV path in its RA platform had not been attached to the MPIC implementation, so MPIC checks were bypassed for that path. The company reported that it invoked its Mass Revocation Plan and revoked or expired all 2,700 affected certificates in less than 24 hours after discovering the incident. SSL.com also said it stopped new validation TLS issuance from the RA platform and has been working through remaining action items, with periodic updates requested and provided in the thread.

Model: gpt-5.4-mini Generated: 2026-10-20 17:46 UTC Confidence: 0.97 6 comments
Chronology
  1. TLS Baseline Requirements MPIC requirements became mandatory, making DCV completed through the secondary path non-conforming.
  2. SSL.com’s auditors followed up on MPIC evidence for certificate samples and the investigation began.
  3. SSL.com completed mass revocation for all unrevoked, unexpired affected certificates.
  4. SSL.com posted the full incident report and attached the incident annex.
Thread Activity
  1. SSL.com — SSL.com said the incident was discovered during its annual WebTrust audit, that 2,700 TLS certificates were affected, and that it would post a full incident report by 2026-09-25.
  2. SSL.com — SSL.com posted the full incident report and attached the MPIC incident annex.
  3. SSL.com — SSL.com said remaining action items were in progress and on track for their due dates.
  4. SSL.com — SSL.com said the action items were still on track and requested the next update be set for 2026-10-30.
  5. SSL.com — SSL.com said work on the remaining action items continued and again requested the next update be set for 2026-10-30.
Participants
SSL.com
Related Bugzilla IDs Mentioned
Similar Local Cases
#2077599 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Opened 2026-10-02 Still Open · 90% similar
SSL.com: Inconsistent published CRL for one ICA
#2076197 ASSIGNED Ca Certificate Compliance Self Reported Incident Ccadb Disclosure Issue Incident Opened 2026-09-28 Still Open · 89% similar
SSL.com: CRL URL typo in CRL URL disclosed to CCADB
#1750631 RESOLVED Incident Revocation Issue Opened 2022-01-17 · Closed 2024-06-30 · 89% similar
SSL.com: Issuance of TLS certificates with domain validation methods prohibited by SC-45
#1790693 RESOLVED Self Reported Incident Revocation Issue Opened 2022-09-13 · Closed 2023-03-24 · 88% similar
SSL.com: Issuance of 1 EV TLS certificate using a Registration/Incorporation Agency not included in our approved public list.
#1962809 RESOLVED Self Reported Incident Revocation Issue Opened 2025-04-25 · Closed 2025-07-28 · 88% similar
SSL.com: Expired certificate for a “Valid” Test Website
#2081961 ASSIGNED Ca Certificate Compliance Self Reported Incident Validation Issue Opened By Ca Opened 2026-10-14 Still Open · 87% similar
SSL.com: Test websites for EV enabled Roots with non-EV certificates
#1938236 RESOLVED Incident Revocation Issue Opened 2024-12-18 · Closed 2025-02-28 · 87% similar
SSL.com: Failure to process CAA records from one SubCA
#2029230 RESOLVED Self Reported Incident Revocation Issue Opened 2026-04-03 · Closed 2026-05-28 · 87% similar
SSL.com: Incorrect Open MPIC Lambda implementation by EJBCA ACME Service

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

⚠

Confirm action