← SSL.com cases
Bugzilla #2057919 Incident Problem Reporting Failure Revocation Issue Delayed Revocation Remediation Tracking

SSL.com: failure to respond to Certificate Problem Reports within 24 hours; final action item in progress

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 reported that its Certificate Problem Report intake path stopped forwarding form submissions to its internal mailbox after an Amazon SES IP-based forwarding change. As a result, SSL.com missed the BR §4.9.5 requirement to provide preliminary responses within 24 hours for five legitimate CPRs, and the incident report says six emails from five reporters were missed in total. The report also says the intake failure delayed one certificate revocation, but this bug is about the procedural failure to respond to CPRs on time, not the underlying certificate issues. SSL.com identified the non-compliance period as 2026-07-21 through 2026-07-26 and said the intake problem was resolved on 2026-07-26. In the latest update, SSL.com said work on final Action Item #3 is in progress: implementing a test email inbox that follows the same intake path, receives regular submissions, and alerts if a submission fails to land. SSL.com asked for the next update to be set for 2026-09-18 and said it will post sooner if the action item is completed earlier.

Model: gpt-5.4-mini Generated: 2026-08-04 07:25 UTC Revised: 2026-08-30 07:00 UTC Confidence: 0.98 5 comments
Chronology
  1. SSL.com’s CPR web form last successfully forwarded a report before the forwarding failure began.
  2. SSL.com missed the 24-hour preliminary response deadline for CPRs received through the broken intake path.
  3. SSL.com’s CPR intake forwarding issue was resolved.
  4. SSL.com’s final Action Item #3 is due to be completed.
Thread Activity
  1. SSL.com — SSL.com filed a preliminary incident report saying it had received a third-party follow-up about an unanswered CPR and was investigating the root cause.
  2. SSL.com — SSL.com filed a full incident report explaining that SES IP-based forwarding changes caused missed CPR emails, delayed five CPR responses, and delayed one revocation.
  3. SSL.com — SSL.com said it continues to monitor the bug and work on the action items from its incident report, with another update promised by 2026-08-21.
  4. SSL.com — SSL.com said it continues to monitor the bug and work on its final action item, with another update promised by 2026-08-28.
  5. SSL.com — SSL.com said final Action Item #3 is in progress, is on track for its 2026-10-15 due date, and asked for the next update to be set for 2026-09-18.
Participants
SSL.com
Related Bugzilla IDs Mentioned
Similar Local Cases
#2058920 ASSIGNED Problem Reporting Failure Incident Externally Reported Incident Opened By Ca Opened 2026-07-29 Still Open · 72% similar
CFCA: Delayed response to CPR related with bug 2058918
#2065157 ASSIGNED Ca Certificate Compliance Delayed Revocation Incident Self Reported Incident Opened 2026-08-20 Still Open · 71% similar
SwissSign: Delayed revocation in Bug 2057448
#2056934 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Policy Document Issue Opened 2026-07-22 Still Open · 71% similar
Actalis: failure to timely update CP/CPS for AgID SubCAs
#2053948 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Ccadb Disclosure Issue Opened 2026-07-09 Still Open · 71% similar
IdenTrust: Delayed disclosure of Intermediate CA in CCADB
#2055542 RESOLVED Incident Problem Reporting Failure Ccadb Disclosure Issue Opened 2026-07-16 · Closed 2026-08-17 · 71% similar
DigiCert: Delayed response to problem report related to Bug 2055539
#2066649 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-08-26 Still Open · 70% similar
Microsoft PKI Services: Missed Seven-Day Update for Bugzilla 2059818
#2063842 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-08-15 Still Open · 70% similar
NETLOCK: Failure to file a preliminary incident report within 72 hours (OCSP responder incident, Bug 2051459)
#2058261 ASSIGNED Ca Documents Incident Self Reported Incident Policy Document Issue Opened 2026-07-27 Still Open · 70% similar
Google Trust Services: CPS Missing root program attestation

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

Confirm action