Firmaprofesional: Delayed initial CCADB incident reporting (72-hour preliminary / 14-day full) for Bug 2016475
Firmaprofesional reported that, after becoming aware on 2026-02-04 of a delayed CCADB disclosure issue later tracked in Bugzilla #2016475, it did not publish the corresponding preliminary incident report within 72 hours and did not publish the full incident report within 14 days. The CA stated this was a non-conformity with the CCADB Incident Reporting Guidelines for initial incident disclosure timing. Firmaprofesional said the underlying CCADB disclosure issue was corrected on the same day it was identified, but the required initial incident reporting deadlines were not tracked as mandatory deliverables once awareness was established. The thread describes contributing factors including the lack of enforced tracking of the 72-hour and 14-day deadlines at incident awareness/classification. Firmaprofesional completed action items by standardizing and enforcing initial CCADB incident disclosure deadline tracking (72h/14d) and by adding formal owner assignment for preliminary and full incident report publication at incident opening. The bug is marked RESOLVED with resolution FIXED.
- Firmaprofesional became aware of a delayed CCADB disclosure issue later tracked in Bugzilla #2016475.
- Firmaprofesional published the preliminary incident report in Bugzilla #2016475.
- Firmaprofesional published the full incident report in Bugzilla #2016475.
- Firmaprofesional opened this bug to track delayed initial incident reporting.
- Firmaprofesional completed the action items for deadline tracking and ownership.
- Logalty representative — Opened the preliminary incident report stating Firmaprofesional did not publish the preliminary report within 72 hours or the full report within 14 days after awareness on 2026-02-04.
- Logalty representative — Posted the full incident report with a timeline, root cause analysis, and action items for enforcing 72-hour/14-day deadline tracking.
- Logalty representative — Confirmed the action items due on 2026-03-31 were completed and updated the action items table.
- Logalty representative — Posted a report closure summary describing remediation and requesting closure.
- CCADB representative — Issued a final call for comments and stated the report would close around 2026-04-14.
- Logalty representative — Corrected the report closure summary, reiterating the delayed initial CCADB incident reporting issue and the completed remediation actions.