← certSIGN cases
Bugzilla #2025318 Self Reported Incident

certSIGN: delay in updating a Bugzilla ticket (Incident Report Closure/Next update missing)

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

This case is an incident disclosure by certSIGN about a delay in updating a related Bugzilla incident ticket (Bug 2016672). certSIGN stated that Bug 2016672 was completed with all actions done, but it lacked a Closure Report and a “Next update” date, and the ticket was not updated for more than 7 days. certSIGN reported that the delay was specifically in adding the Closure report, and that internally the activity was marked as done before it was performed. certSIGN provided a root cause analysis identifying contributing factors including a procedural issue relying on single-person ownership and a notifications configuration issue that closed after a time-out rather than remaining active until received. After feedback from the Chrome Root Program requesting a deeper RCA and clearer action items, certSIGN updated the report and action items, including an updated RCA document referenced in the thread. The thread includes a Report Closure Summary with remediation steps and states that all action items disclosed in the report have been completed as described, with a request to close the incident report. The CCADB incident reporting contact issued a final call for comments, indicating the report would be closed on approximately 2026-05-26, and the bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:35 UTC Revised: 2026-06-16 18:25 UTC Confidence: 0.86 7 comments
Chronology
  1. Non-compliance period began for the related incident ticket (Bug 2016672) due to missing Closure Report/“Next update” date.
  2. Non-compliance period ended after the Report Closure Summary was added to the related ticket.
  3. certSIGN posted the Report Closure Summary and requested closure of the incident report.
  4. The incident report was closed (bug status RESOLVED/FIXED).
Thread Activity
  1. certSIGN — Opened a preliminary incident report stating Bug 2016672 was completed but missing a Closure Report and “Next update” date for more than 7 days, citing the 7-day update requirement.
  2. certSIGN — Submitted a full incident report with timeline, root cause analysis (procedural single-person reliance and notifications configuration), and action items.
  3. certSIGN — Reported that the action item “Update config” was completed and all actions were done.
  4. Google representative — Requested updates to the RCA and action items, noting the report lacked why the single point of failure existed and asking for a full 5-Whys breakdown.
  5. certSIGN — Stated the RCA and action items were updated and pointed to an attached updated RCA document.
  6. certSIGN — Posted the Report Closure Summary describing systemic root causes, remediation steps, and requesting closure, stating action items were completed.
  7. CCADB representative — Issued a final call for comments/questions and stated the incident report would be closed on approximately 2026-05-26.
Participants
certSIGN Google representative CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#1886624 RESOLVED Self Reported Incident Opened 2024-03-20 · Closed 2025-06-04 · 97% similar
certSIGN: Certificates with incorrect Subject attribute order
#2002402 RESOLVED Self Reported Incident Opened 2025-11-25 · Closed 2026-01-13 · 79% similar
GoDaddy: Missing R1 Intermediate Full CRL URLs in CCADB
#1959733 RESOLVED Self Reported Incident Opened 2025-04-10 · Closed 2025-07-16 · 78% similar
CFCA: Failed to respond a Certificate Problem Report within 24 hours which violates Section 4.9.5 of the TLS BRs
#1991558 RESOLVED Self Reported Incident Opened 2025-09-29 · Closed 2026-01-15 · 77% similar
IdenTrust: TLS self audit testing below 3%
#1950574 RESOLVED Self Reported Incident Opened 2025-02-26 · Closed 2025-09-15 · 77% similar
SECOM: S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)
#1390979 RESOLVED Self Reported Incident Opened 2017-08-16 · Closed 2023-02-22 · 77% similar
certSIGN: Non-BR-Compliant Certificate Issuance
#1955365 RESOLVED Self Reported Incident Opened 2025-03-20 · Closed 2025-05-19 · 77% similar
Apple: Public Key Reuse
#1991215 RESOLVED Self Reported Incident Opened 2025-09-26 · Closed 2025-11-21 · 75% similar
IdenTrust: ICA with invalid CDP

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

Confirm action