← DigiCert cases
Bugzilla #1937210 Ca Certificate Compliance

DigiCert: Late incident report for bug 1925106

RESOLVED FIXED DigiCert
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

DigiCert reported a failure to submit a full incident report within the required timeframe for bug 1925106. The delay was attributed to an incorrect calculation of deadlines during an internal tracker consolidation, which was exacerbated by staffing changes. DigiCert acknowledged the impact of this oversight on the community's expectations and outlined corrective actions, including updating their standard operating procedures (SOP) to better manage incident response timelines. The incident report was ultimately submitted late, but all action items to prevent future occurrences have been completed, and DigiCert has requested closure of the case.

Model: gpt-4o-mini Generated: 2026-06-13 11:46 UTC Revised: 2026-06-16 19:19 UTC Confidence: 0.85 23 comments
Chronology
  1. DigiCert files preliminary incident report for bug 1925106.
  2. DigiCert submits full incident report late.
  3. Bug closed after all action items completed.
Thread Activity
  1. DigiCert — DigiCert acknowledges the late submission of the full incident report.
  2. DigiCert — DigiCert requests closure of the bug after completing all actions.
  3. DigiCert — DigiCert provides a closure summary detailing the incident and remediation steps.
Participants
DigiCert Sectigo Mozilla representative
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#1927506 RESOLVED Ca Certificate Compliance Opened 2024-10-28 · Closed 2025-01-24 · 100% similar
DigiCert: Incorrect OrgID in S/MIME certificates for one customer
#1624527 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2020-03-24 · Closed 2023-02-22 · 87% similar
DigiCert: Issuance of Cert with Compromised Key
#1914911 RESOLVED Ca Certificate Compliance Opened 2024-08-26 · Closed 2025-01-08 · 87% similar
DigiCert: Unclear Disclosure of CAA Issuer Domain Names
#1714439 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-06-03 · Closed 2023-02-22 · 86% similar
DigiCert: Incorrect RegNumber-Org Type combination
#1865235 RESOLVED Ca Certificate Compliance Opened 2023-11-17 · Closed 2023-12-07 · 86% similar
DigiCert: Late background refreshment check
#1710444 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-05-10 · Closed 2023-02-22 · 85% similar
DigiCert: Invalid stateOrProvinceName
#1875205 RESOLVED Ca Certificate Compliance Opened 2024-01-18 · Closed 2024-01-26 · 85% similar
Digicert: SMIME certs missing State in Org ID
#1881364 RESOLVED Ca Certificate Compliance Opened 2024-02-21 · Closed 2024-03-29 · 85% similar
Digicert: SMIME certificate with unvalidated information

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

Confirm action