Disig: Delayed Full Incident Report
This case concerns Disig, a.s. (CA Owner CCADB unique ID A000008) disclosing that it delayed posting its Full Incident Report. The preliminary incident report was referenced as being disclosed in bug 2007132, and the Full Incident Report submission was delayed. The thread states that the non-compliance period ran from 2026-01-02 to 2026-01-07, with the Full Incident Report submitted on 2026-01-07. The reported impact was that no certificate issuance, revocation, or overall CA operations were affected, and that no certificate misissuance or ecosystem risk occurred; the delay affected only the timing of the Full Incident Report submission. The stated contributing factors were staffing issues due to pre-planned vacations during the holiday season and a high number of bank holidays. The CA reported remediation including implementing a holiday coverage plan to ensure compliance and technical coverage during holiday or non-standard working periods, and requested closure after completing the action items.
- Disig’s incident reporting non-compliance period began (Full Incident Report not yet submitted).
- Disig identified the incident reporting non-compliance.
- Disig submitted the Full Incident Report and the non-compliance period ended.
- Disig posted the report closure summary and requested bug closure.
- Disig, a.s. — Posted a preliminary incident report noting delayed posting of the Full Incident Report and referenced CCADB Incident Reporting Guidelines v3.1 and bug 2007132 as the source of disclosure.
- Disig, a.s. — Posted the Full Incident Report, stating the delay window (2026-01-02 to 2026-01-07), the contributing factors (vacations and holiday/bank holidays), and that no certificate/operations impact occurred.
- Disig, a.s. — Posted a report closure summary stating the Full Incident Report was posted on 2026-01-07, described remediation via a holiday coverage plan, and requested closure after completing action items.
- CCADB representative — Issued a final call for comments and indicated the bug would be closed approximately 2026-01-27 if no further input was received.