← China Financial Certification Authority (CFCA) cases
Bugzilla #2009134 Self Reported Incident

CFCA: reporting delayed when handling incident bug #2005399

RESOLVED FIXED China Financial Certification Authority (CFCA)
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

The China Financial Certification Authority (CFCA) reported a delay in disclosing an incident related to Bug #2005399, which was not filed within the required 72-hour timeframe due to a misconception that remediation needed to be completed first. The CA acknowledged this delay and submitted a preliminary incident report, followed by a full report detailing the incident and its handling. CFCA has since updated its internal incident handling guidelines to align with community requirements and completed all action items related to this incident. The case is now resolved.

Model: gpt-4o-mini Generated: 2026-06-13 21:36 UTC Revised: 2026-06-16 18:10 UTC Confidence: 0.85 12 comments
Chronology
  1. Non-compliance identified due to delayed incident report submission.
  2. Full incident report submitted by CFCA.
  3. CFCA completed action items and requested closure of the incident.
Thread Activity
  1. Community commenter — CFCA acknowledged the delay in filing the incident report.
  2. Community commenter — CFCA submitted a preliminary incident report detailing the delay.
  3. Community commenter — Community member raised questions regarding CFCA's handling of the incident.
  4. Community commenter — CFCA finalized the incident handling standards and requested closure.
Participants
Community commenter
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#2005399 RESOLVED Incident Self Reported Incident Opened 2025-12-11 · Closed 2026-02-18 · 91% similar
CFCA: DV OCA caIssuers Returns PEM Encoded Certificate (RFC 5280 Section 4.2.2.1 Violation)
#1955799 RESOLVED Self Reported Incident Opened 2025-03-23 · Closed 2025-04-11 · 90% similar
CFCA: Failed to follow Report lifecycle rule to respond within 7 days
#1959733 RESOLVED Self Reported Incident Opened 2025-04-10 · Closed 2025-07-16 · 90% similar
CFCA: Failed to respond a Certificate Problem Report within 24 hours which violates Section 4.9.5 of the TLS BRs
#1949131 RESOLVED Self Reported Incident Opened 2025-02-19 · Closed 2025-05-08 · 87% similar
CFCA: BasicConstraints are not marked as critical certificates are missing and therefore not revoked
#2033412 RESOLVED Ca Certificate Compliance Externally Reported Incident Incident Certificate Misissuance Opened 2026-04-20 · Closed 2026-06-25 · 87% similar
CFCA: CRL signatureAlgorithm Missing NULL Parameter (RFC 4055 Section 5)
#2031281 RESOLVED Ca Certificate Compliance Self Reported Incident Incident Certificate Misissuance Opened 2026-04-13 · Closed 2026-06-16 · 86% similar
CFCA: OCSP Responder Certificate Profile Deviations and OCSP Service Issues
#1532559 RESOLVED Certificate Misissuance Self Reported Incident Opened 2019-03-05 · Closed 2023-02-22 · 82% similar
CFCA: Wrong SerialNumber encoding
#1565494 RESOLVED Audit Finding Self Reported Incident Repository Issue Opened 2019-07-12 · Closed 2024-06-30 · 81% similar
CFCA: Missed annual CPS update publication on website in 2018

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

Confirm action