← iTrusChina Co., Ltd. cases
Bugzilla #2025248 Self Reported Incident

iTrusChina: Failure to Provide Regular Incident Update

RESOLVED FIXED iTrusChina Co., Ltd.
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

iTrusChina reported an incident in which it failed to provide regular incident updates in Bugzilla. The CA said it was notified by a third party on March 22, 2026 that it did not provide timely updates of its Bug 2013805, which it considered a violation of the CCADB Incident Reporting Guidelines. In its report, iTrusChina stated that the planned update due around March 16 was missed due to human error, and that its governance process lacked a double-checking mechanism to ensure prompt updates. iTrusChina said it began root cause analysis and mitigation after realizing the issue on March 23, 2026. The CA committed to establishing a double-check mechanism (with at least two personnel) and to checking all its open incidents to ensure timely updates. In later comments, iTrusChina stated that the action items were finished and requested closure. The bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:14 UTC Revised: 2026-06-16 19:13 UTC Confidence: 0.90 8 comments
Chronology
  1. iTrusChina was notified by a third party that it had not provided timely incident updates for Bug 2013805.
  2. iTrusChina realized the issue and began root cause analysis and mitigation.
  3. iTrusChina requested closure after completing the disclosed action items.
  4. The incident report bug was resolved (FIXED).
Thread Activity
  1. iTrusChina Co., Ltd. — Opened a full incident report stating iTrusChina failed to provide regular updates for Bug 2013805, citing human error and lack of a double-checking mechanism, and listing remediation action items.
  2. iTrusChina Co., Ltd. — Reported that iTrusChina was monitoring for comments/questions and that all action items were finished.
  3. iTrusChina Co., Ltd. — Stated iTrusChina was monitoring the bug for comments/questions and would provide more information if needed.
  4. iTrusChina Co., Ltd. — Acknowledged monitoring for comments/questions and thanked participants.
  5. iTrusChina Co., Ltd. — Reiterated that iTrusChina was monitoring and that all action items had been finished.
  6. iTrusChina Co., Ltd. — Stated iTrusChina was monitoring and would provide more information if needed.
  7. iTrusChina Co., Ltd. — Provided a report closure summary, reiterated root causes and remediation, and requested closure after completing action items.
  8. CCADB representative — Issued a final call for comments/questions and said the incident report would be closed approximately 2026-05-01 if no further input was received.
Participants
iTrusChina Co., Ltd. CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2020899 RESOLVED Self Reported Incident Opened 2026-03-04 · Closed 2026-04-11 · 97% similar
iTrusChina: Failure to Respond to Feb 2026 Chrome Root Program Survey
#2025596 RESOLVED Self Reported Incident Incident Opened 2026-03-23 · Closed 2026-05-18 · 72% similar
IdenTrust: Delay in updating a Bugzilla ticket Bug 2014610 - Next update
#2025914 RESOLVED Self Reported Incident Audit Delay Opened 2026-03-24 · Closed 2026-05-18 · 71% similar
IdenTrust: Full Incident Report for bug 2014610 was not published within 14 days of discovering the issue
#1959733 RESOLVED Self Reported Incident Opened 2025-04-10 · Closed 2025-07-16 · 71% similar
CFCA: Failed to respond a Certificate Problem Report within 24 hours which violates Section 4.9.5 of the TLS BRs
#2026453 RESOLVED Self Reported Incident Audit Delay Opened 2026-03-26 · Closed 2026-04-22 · 70% similar
Microsoft PKI Services: Failure to report Bugzilla 2026452 within 72 hrs
#2025917 RESOLVED Self Reported Incident Audit Delay Opened 2026-03-24 · Closed 2026-05-18 · 70% similar
IdenTrust: Full Incident Report for bug 2016585 was not published within 14 days of discovering the issue
#2026351 RESOLVED Self Reported Incident Certificate Misissuance Opened 2026-03-25 · Closed 2026-05-18 · 70% similar
Identrust: Root CrossSign, of dedicated Roots, missing EKU
#2004845 RESOLVED Self Reported Incident Opened 2025-12-09 · Closed 2026-02-11 · 70% similar
GoDaddy: CA Certificates Published in PEM format

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

Confirm action