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

iTrusChina: Failure to Respond to Feb 2026 Chrome Root Program Survey

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 respond to a survey from the Chrome Root Program Team about Chrome Root Policy v1.8 before the Feb 26, 2026 deadline. The Chrome Root Program Team informed iTrusChina on Mar 3, 2026 that the survey response was not received, which iTrusChina stated was considered a violation of Chrome Root Policy. In its incident report, iTrusChina attributed the failure to its new Email Security Gateway wrongly quarantining the Chrome Team’s survey and reminder emails, and to inadequate management of quarantined email lists. iTrusChina said it responded to the survey after receiving the notification and took remediation steps, including adjusting the Email Security Gateway’s quarantine rules and adding whitelists, and establishing a mechanism to enhance management of quarantined email lists with daily quarantine notifications to email receivers. iTrusChina also stated that its investigation found additional contributing issues: an ISP block of some overseas IPs and Spamhaus.org blacklisting due to incorrect HELO/EHLO configuration, and that it contacted the ISP to whitelist overseas IPs and adjusted HELO/EHLO configuration and requested unlocking its IPs. The bug was resolved as FIXED, and iTrusChina requested closure after stating all action items were completed as described.

Model: gpt-5.4-nano Generated: 2026-06-13 21:13 UTC Revised: 2026-06-16 19:13 UTC Confidence: 0.86 8 comments
Chronology
  1. iTrusChina did not respond to the Chrome Root Policy v1.8 survey by the Feb 26 deadline.
  2. Chrome Root Program Team notified iTrusChina that it had failed to respond to the survey.
  3. iTrusChina submitted an incident report and remediation plan in the bug.
  4. iTrusChina provided a report closure summary and requested closure.
Thread Activity
  1. iTrusChina Co., Ltd. — Submitted a full incident report describing the missed Chrome Root Policy v1.8 survey response and root causes, and listed remediation actions.
  2. iTrusChina Co., Ltd. — Stated iTrusChina was monitoring the bug and that action items were finished, marking gateway quarantine-rule adjustments and quarantined-email-list management as Done.
  3. Community commenter — Questioned whether action items could be marked Done before investigating and disclosing the 'unknown reasons' for not receiving the first survey email.
  4. iTrusChina Co., Ltd. — Responded that IT was investigating the failure to receive the first email and would provide feedback ASAP.
  5. iTrusChina Co., Ltd. — Reported investigation results for the first-email failure, including ISP blocking of some overseas IPs and Spamhaus.org blacklisting due to HELO/EHLO misconfiguration, and described remediation steps.
  6. iTrusChina Co., Ltd. — Said iTrusChina was monitoring the bug 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 stating all action items were completed.
  8. CCADB representative — Issued a final call for comments and indicated the incident report would be closed around 2026-04-10 if no further comments were received.
Participants
iTrusChina Co., Ltd. Community commenter CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2025248 RESOLVED Self Reported Incident Opened 2026-03-23 · Closed 2026-05-01 · 97% similar
iTrusChina: Failure to Provide Regular Incident Update
#1959733 RESOLVED Self Reported Incident Opened 2025-04-10 · Closed 2025-07-16 · 70% similar
CFCA: Failed to respond a Certificate Problem Report within 24 hours which violates Section 4.9.5 of the TLS BRs
#2025318 RESOLVED Self Reported Incident Opened 2026-03-23 · Closed 2026-05-26 · 70% similar
certSIGN: delay in updating a Bugzilla ticket
#2012157 RESOLVED Self Reported Incident Revocation Issue Security Incident Opened 2026-01-23 · Closed 2026-03-08 · 70% similar
Actalis: Issuance of certificate using keys previously reported as compromised
#2009045 RESOLVED Self Reported Incident Audit Finding Opened 2026-01-07 · Closed 2026-02-19 · 68% similar
Chunghwa Telecom: Delayed disclosure to Bug 2008788 GTLSCA Audit Incident Report #2 - Domain validation records without the TLS BR version
#2031281 RESOLVED Ca Certificate Compliance Self Reported Incident Incident Certificate Misissuance Opened 2026-04-13 · Closed 2026-06-16 · 68% similar
CFCA: OCSP Responder Certificate Profile Deviations and OCSP Service Issues
#1886624 RESOLVED Self Reported Incident Opened 2024-03-20 · Closed 2025-06-04 · 68% similar
certSIGN: Certificates with incorrect Subject attribute order
#1973034 RESOLVED Self Reported Incident Opened 2025-06-19 · Closed 2025-07-02 · 68% similar
Certigna: Finding #3 ETSI Audit – Event log protection beyond seven years shall be improved

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

Confirm action