← China Financial Certification Authority (CFCA) cases
Bugzilla #2058920 Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Closure Request

CFCA delayed response to a Certificate Problem Report within 24 hours

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

This case concerns CFCA’s failure to provide a preliminary response to a Certificate Problem Report within the 24-hour requirement in BR Section 4.9.5. CFCA’s report says the CPR was submitted on 2026-07-27 at 20:50 UTC+8 and the preliminary response was provided at 2026-07-28 21:51 UTC+8, about one hour late. CFCA stated that no subscriber certificates were affected. The report identified process gaps in CPR handling, including lack of leave coverage and an A/B backup mechanism, and a misread of the CPR submission time. CFCA later said all action items were completed and posted a closure report requesting closure. The bug is now resolved with resolution FIXED, and CCADB had issued a final call for comments before the expected closure date.

Model: gpt-5.4-mini Generated: 2026-08-04 07:21 UTC Revised: 2026-09-27 07:00 UTC Confidence: 0.99 11 comments
Chronology
  1. A Certificate Problem Report was submitted to CFCA.
  2. The 24-hour preliminary response deadline was missed and the CPR was acknowledged later that day.
  3. CFCA opened the Bugzilla incident report for the delayed CPR response.
  4. CFCA said all action items were complete.
  5. CFCA posted a closure report and requested closure.
  6. The bug was resolved with resolution FIXED.
Thread Activity
  1. China Financial Certification Authority (CFCA) — CFCA filed a preliminary incident report saying the CPR acknowledgment exceeded the 24-hour requirement in BR Section 4.9.5.
  2. China Financial Certification Authority (CFCA) — CFCA said it was preparing the full report and had no other updates yet.
  3. China Financial Certification Authority (CFCA) — CFCA filed the full incident report with the timeline, impact, and root-cause analysis.
  4. China Financial Certification Authority (CFCA) — CFCA said there were no further updates.
  5. China Financial Certification Authority (CFCA) — CFCA said it was monitoring the incident and had no further updates yet.
  6. China Financial Certification Authority (CFCA) — CFCA again said it was monitoring the incident and had no further updates yet.
  7. China Financial Certification Authority (CFCA) — CFCA said there were still no further updates and that it would keep monitoring the incident.
  8. China Financial Certification Authority (CFCA) — CFCA said it was monitoring the incident and had no further updates yet.
  9. China Financial Certification Authority (CFCA) — CFCA said all action items were complete and listed completed preventive changes to CPR handling.
  10. China Financial Certification Authority (CFCA) — CFCA posted a closure report stating the incident report was complete and requesting closure.
  11. CCADB representative — CCADB issued a final call for comments and said the report would be closed on or about 2026-09-24.
  12. China Financial Certification Authority (CFCA) — Bug status changed to RESOLVED with resolution FIXED.
Participants
China Financial Certification Authority (CFCA) CCADB representative
Similar Local Cases
#2049179 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-06-21 · Closed 2026-08-04 · 97% similar
CFCA: OCSP Service return unauthorized responses
#2054464 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-07-13 · Closed 2026-08-17 · 96% similar
CFCA: Delayed response to CPR-related email related with bug 2049179
#2072647 RESOLVED Ca Certificate Compliance Externally Reported Incident Problem Reporting Failure Ct Logging Issue Opened 2026-09-16 · Closed 2026-10-28 · 84% similar
Sectigo: Violation of TLS BR 7.1.3.2.2 in OCSP responses
#2055539 RESOLVED Problem Reporting Failure Incident Externally Reported Incident Revocation Issue Opened 2026-07-16 · Closed 2026-08-11 · 84% similar
DigiCert: Delayed availability of OCSP responses
#2065157 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Delayed Revocation Opened 2026-08-20 · Closed 2026-09-28 · 83% similar
SwissSign: Delayed revocation in Bug 2057448
#2047952 RESOLVED Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Opened 2026-06-16 · Closed 2026-08-04 · 83% similar
KIR: OCSP responder does not return status for precertificate
#2073548 RESOLVED Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Opened 2026-09-18 · Closed 2026-10-21 · 82% similar
Sectigo: Submitted CPR not replied to within 24 hours
#2057919 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Opened 2026-07-26 Still Open · 82% similar
SSL.com: Failure to respond to Certificate Problem Report within 24 hours

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

⚠

Confirm action