← Autoridad de Certificacion Firmaprofesional cases
Bugzilla #2054450 Ca Certificate Compliance Ccadb Disclosure Issue Incident Externally Reported Incident Policy Document Issue

Firmaprofesional CCADB hierarchy association incident closed after remediation and final call for comments

RESOLVED FIXED Autoridad de Certificacion Firmaprofesional
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 Firmaprofesional’s CCADB hierarchy metadata for seven subordinate CA certificate records that were initially associated only with a 2009 self-signed root record and not with the Chrome-included 2014 root record, even though the two roots share the same Subject and SPKI. The issue was first reported by the Chrome Root Program on 2026-07-10, and Firmaprofesional’s reconciliation expanded the scope from four records to seven. Firmaprofesional updated the `Parent CA Owner/Certificate` field for all seven records on 2026-07-10 and later published a full incident report on 2026-07-24. On 2026-08-14, Firmaprofesional said the remaining action item had been completed and that all action items in the full incident report were complete. On 2026-08-19, Firmaprofesional posted a closure summary stating that the procedure had been updated, the full corpus review found no additional affected records, and all action items had been completed. On 2026-08-25, CCADB incident-reporting posted a final call for comments or questions and said the report would be closed around 2026-09-01. The bug is marked RESOLVED/FIXED.

Model: gpt-5.4-mini Generated: 2026-07-16 19:55 UTC Revised: 2026-09-06 06:01 UTC Confidence: 0.98 8 comments
Chronology
  1. Chrome Root Program notified Firmaprofesional that four subordinate CA records were associated only with the 2009 root record instead of the Chrome-included 2014 root record.
  2. Firmaprofesional updated the parent association for the seven affected subordinate CA records to the 2014 root record.
  3. Firmaprofesional published the full incident report confirming the seven-record scope and the corrected parent association.
  4. Firmaprofesional said the remaining action item had been completed and that all action items were now complete.
  5. Firmaprofesional posted a closure summary requesting closure after completing remediation and procedure updates.
  6. CCADB incident-reporting posted a final call for comments and said the report would be closed around 2026-09-01.
Thread Activity
  1. Autoridad de Certificacion Firmaprofesional — Firmaprofesional posted a preliminary incident report describing the incorrect CCADB hierarchy associations and the seven affected records.
  2. Autoridad de Certificacion Firmaprofesional — Firmaprofesional said its investigation and full incident report preparation were still in progress and requested a next update date of 2026-07-27.
  3. Autoridad de Certificacion Firmaprofesional — Firmaprofesional posted the full incident report, confirmed the seven-record scope, and said the parent association had been changed to the 2014 root.
  4. Autoridad de Certificacion Firmaprofesional — Firmaprofesional said work on the remaining open action item was still in progress and requested next update be set to 2026-08-15.
  5. Autoridad de Certificacion Firmaprofesional — Firmaprofesional said the remaining action item had been completed and that all action items in the full incident report were now complete.
  6. Autoridad de Certificacion Firmaprofesional — Firmaprofesional posted a report closure summary describing the root cause, remediation, updated disclosure procedure, and request for closure.
  7. CCADB representative — CCADB incident-reporting posted a final call for comments or questions and said the incident report would be closed around 2026-09-01.
Participants
Autoridad de Certificacion Firmaprofesional CCADB representative Mozilla representative
Similar Local Cases
#2055444 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Audit Delay Opened 2026-07-16 · Closed 2026-09-10 · 100% similar
Firmaprofesional: Delayed publication of 2026 Audit Attestation Letters
#2055449 RESOLVED Ca Certificate Compliance Incident Ccadb Disclosure Issue Policy Document Issue Opened 2026-07-16 · Closed 2026-08-06 · 100% similar
Firmaprofesional: Delayed and inaccurate policy-document disclosures for SIGNE Autoridad de Certificacion - 2020
#2058363 RESOLVED Common Ca Database Ccadb Disclosure Issue Incident Externally Reported Incident Opened 2026-07-28 · Closed 2026-08-29 · 85% similar
DigiCert: Blank SubCA Owner field in CCADB for cross-certificate
#2055047 RESOLVED Common Ca Database Ccadb Disclosure Issue Incident Self Reported Incident Opened 2026-07-14 · Closed 2026-08-17 · 85% similar
DigiCert: Incomplete disclosure of CRL URLs in CCADB
#2055775 RESOLVED Common Ca Database Ccadb Disclosure Issue Incident Self Reported Incident Opened 2026-07-17 · Closed 2026-09-14 · 83% similar
Asseco DS / Certum: Incomplete CRL Disclosure in CCADB
#2050850 RESOLVED Ca Certificate Compliance Common Ca Database Incident Externally Reported Incident Opened 2026-06-26 · Closed 2026-08-04 · 83% similar
Asseco DS / Certum: HTTP 404 returned by CRL Distribution Point URLs for six pre-inclusion Root CAs
#2055250 ASSIGNED Common Ca Database Externally Reported Incident Ccadb Disclosure Issue Incident Opened 2026-07-15 Still Open · 82% similar
D-TRUST: Incomplete Disclosure of CRL URLs
#2049012 RESOLVED Ccadb Metadata Update Opened By Ca Ccadb Disclosure Issue Policy Document Issue Opened 2026-06-19 · Closed 2026-08-04 · 81% similar
FNMT: Inaccuracy in CRL URL in CCADB

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

⚠

Confirm action