← Autoridad de Certificacion Firmaprofesional cases
Bugzilla #2025538 Delayed Revocation

Firmaprofesional: Delayed weekly updates and responses on open incident reports

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

Firmaprofesional reported an incident reporting process non-conformity in which it did not provide timely required weekly updates or timely responses on several open CCADB incident reports. The issue applied specifically to open incident reports without a recorded Next update date, where no response or status update was posted within 7 days as required by the CCADB Incident Reporting Guidelines. The CA stated that the incident was identified through public follow-up comments noting the missed reporting cadence, and that it did not involve certificate issuance being stopped because it was an incident management process issue only. Firmaprofesional’s remediation included implementing mandatory tracking of Bugzilla response deadlines and required weekly update dates, assigning primary and backup owners with escalation triggers for overdue updates, and adding a control requiring Next update date review when an incident remains open after a remediation update. The bug thread records that the action items due on 2026-04-10 were completed and the action items table was updated accordingly. Firmaprofesional requested closure of the incident report, and CCADB issued a final call for comments with an expected closure date of approximately 2026-04-23. The bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:38 UTC Revised: 2026-06-16 18:15 UTC Confidence: 0.50 7 comments
Chronology
  1. Firmaprofesional’s 7-day update/response deadlines elapsed for several open incident reports without further updates or recorded Next update dates.
  2. A separate incident was opened to track delayed weekly updates and responses on open incident reports.
  3. Firmaprofesional completed the action items to address missed Bugzilla update deadlines and ownership/escalation controls.
  4. Firmaprofesional requested closure of the incident report after completing remediation actions.
  5. CCADB planned to close the incident report after a final comment window.
Thread Activity
  1. Logalty representative — Firmaprofesional submitted a preliminary incident report stating that required CCADB weekly updates and acknowledgements were not provided within the expected timeframe for several open incident reports.
  2. Logalty representative — Firmaprofesional posted the full incident report detailing that weekly updates/responses were not posted within 7 days when no Next update date was recorded, and described root causes and remediation timeline.
  3. Logalty representative — Firmaprofesional stated there was no material change and that the next update/action item due dates remained unchanged.
  4. Logalty representative — Firmaprofesional again reported no material change and reiterated the action item due dates.
  5. Logalty representative — Firmaprofesional confirmed the 2026-04-10 action items were completed and updated the action items table accordingly.
  6. Logalty representative — Firmaprofesional provided a report closure summary, stating remediation was completed and requesting closure of the incident report.
  7. CCADB representative — CCADB issued a final call for comments and indicated the incident report would be closed on approximately 2026-04-23.
Participants
Logalty representative CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2016066 RESOLVED Delayed Revocation Opened 2026-02-11 · Closed 2026-03-30 · 100% similar
Firmaprofesional: Delayed preliminary response under BR 4.9.5 (Bug #2009941)
#2011855 RESOLVED Delayed Revocation Opened 2026-01-22 · Closed 2026-05-11 · 96% similar
Firmaprofesional: Delayed revocation of TLS certificates affected by bug #2009941
#1891251 RESOLVED Delayed Revocation Opened 2024-04-12 · Closed 2024-06-01 · 88% similar
FIRMAPROFESIONAL: Delayed leaf revocation
#2016475 RESOLVED Delayed Revocation Opened 2026-02-12 · Closed 2026-05-15 · 88% similar
Firmaprofesional: Delayed revocation disclosure of TLS Subordinate CA certificate Secure Web 2024 in CCADB
#1771724 RESOLVED Ca Certificate Compliance Delayed Revocation Opened 2022-05-30 · Closed 2023-02-22 · 81% similar
Firmaprofesional: 2022 - CPS without correct explanation about difference between OCSP and CRL
#1651637 RESOLVED Delayed Revocation Opened 2020-07-09 · Closed 2023-02-22 · 78% similar
Firmaprofesional: Failure to revoke ICAs within 7 days: OCSP EKU
#1966006 RESOLVED Delayed Revocation Opened 2025-05-13 · Closed 2025-07-01 · 77% similar
KIR: Intermediate CA - SZAFIR Trusted CA3 - revocation status not changed in CCADB
#2004698 RESOLVED Delayed Revocation Opened 2025-12-08 · Closed 2026-01-15 · 72% similar
NAVER Cloud Trust Services: Failure to respond to CPR within 24 hours

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

Confirm action