CFCA: Failed to follow Report lifecycle rule to respond within 7 days
This case is a self-reported compliance issue by China Financial Certification Authority (CFCA) regarding incident reporting lifecycle management. CFCA stated that, while handling community incidents in related Bugzilla incidents, it failed multiple times to respond within 7 days as required by the “Report lifecycle management” section of the Incident Reporting Guidelines. CFCA said it inspected the incidents for response time gaps, identified a serious incident handling problem, and previously listed improvement approaches in one of the related bugs. In this bug, CFCA described remediation steps including establishing a certificate incident handling plan, investing more human resources, assigning tasks to check Bugzilla at least twice a week, and developing an automated workflow to send daily notifications via its tools. CFCA provided a “Report Closure Summary” stating that the action items disclosed in the report were completed and requested closure. Mozilla’s Ben Wilson indicated he would close the bug on or about 11-Apr-2025 unless additional questions or issues arose, and the bug is marked RESOLVED with resolution FIXED.
- CFCA began a period of non-compliance where it failed to respond within 7 days for incident reports referenced by the case.
- CFCA identified the report lifecycle non-compliance for the incident handling period described in the bug.
- CFCA opened this self-disclosure bug describing the 7-day response failures and proposed remediation.
- The bug was resolved (FIXED) after Mozilla indicated closure would occur around 11-Apr-2025.
- Community commenter — Michael (CFCA) reported that CFCA failed multiple times to respond within 7 days during handling several incidents, and requested a separate bug for self-improvement.
- Community commenter — Michael provided a full incident report summary, including a timeline of multiple missed 7-day responses and described contributing factors and remediation.
- Community commenter — Jeremy recommended more automated controls and suggested pulling questions into JIRA and tracking them there.
- Community commenter — Michael responded that CFCA is testing automation (n8n/airtable/IM clients) and described a daily check process to notify until the bug is resolved.
- Community commenter — Michael stated CFCA implemented a n8n+airtable+slack automation workflow to monitor CFCA-related bugs and send daily updates for unresolved items.
- Community commenter — Michael said CFCA would submit a closure summary and request closure if there were no further comments.
- Community commenter — Jeremy thanked Michael and appreciated the automation reminders.
- Community commenter — Michael updated with a “Report Closure Summary,” listing incident root causes and remediation, stating action items were completed and requesting closure.
- Mozilla representative — Ben Wilson said he would close the bug on or about Friday, 11-Apr-2025 unless additional questions or issues remained.
- Community commenter — Michael said CFCA would continue monitoring until RESOLVED and reported no further updates.