← Government of The Netherlands, PKIoverheid (Logius) cases
Bugzilla #2008025 Incident Audit Finding

PKIoverheid: TSP CIBG Findings in 2025 ETSI Audit - Incident Report #4 – Incident Management

RESOLVED FIXED Government of The Netherlands, PKIoverheid (Logius)
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 is an incident report from PKIoverheid (CA Owner CCADB unique ID A000068) regarding Incident Management non-conformities identified in a 2025 ETSI audit. The incident disclosure source is stated as a finding by the CAB during the annual ETSI audit. The report states that incident management was not compliant with applicable requirements (ETSI 319 401, Clause 7.9), including that P2 and P3 incidents were not managed using SLA, RTO, and RPO, and that escalation from P1 to P0 lacked a clear path with linkage to BC in the process description. It also reports that for internal incidents no SLA was defined, TRO/RPO were checked manually, the supply chain contractor did not include RTO/RPO in reports, and the incident manager had no delegate. On the operational side, it was found that one ticket was closed before a lessons learned analysis was performed and that follow-up of one incident was not properly managed. The CA states that the Incident Management process was redesigned, role replacement agreements were formally recorded, supplier reporting was updated to include RTO/RPO for P2 and P3, and additional agreements were made for problem management update frequency; action items were completed and the report closure summary requested closure. The bug is resolved as FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:19 UTC Revised: 2026-06-16 19:25 UTC Confidence: 0.84 6 comments
Chronology
  1. An auditor identified an ETSI audit finding related to Incident Management non-conformities.
  2. A Corrective Action Plan was created in response to the finding.
  3. The Corrective Action Plan was approved by the auditor.
  4. The incident report’s action items were listed with due dates for remediation work.
  5. The CA reported that all action items had been closed and a report closure summary would follow.
  6. The CA posted the report closure summary describing remediation and requesting closure.
  7. The bug was marked RESOLVED with resolution FIXED.
Thread Activity
  1. Logius representative — Opened a preliminary incident report describing a minor non-conformity in Incident Management and citing ETSI 319 401 (Clause 7.9) with disclosure sourced to the annual ETSI audit.
  2. Logius representative — Stated the full incident report was in final review and would be posted shortly.
  3. Logius representative — Posted the full incident report detailing multiple Incident Management non-conformities, root causes, a timeline, and action items with due dates and statuses.
  4. Logius representative — Reported that all action items had been closed and that a report closure summary would be posted shortly.
  5. Logius representative — Posted the report closure summary, describing remediation (process redesign, recorded role replacement agreements, supplier reporting updates, and audit plan updates) and requested closure.
  6. CCADB representative — Issued a final call for comments and stated the incident report would be closed approximately 2026-02-06.
Participants
Logius representative CCADB representative
External References
Similar Local Cases
#1983263 RESOLVED Incident Closure Request Opened 2025-08-15 · Closed 2026-04-17 · 100% similar
PKIoverheid: TSP KPN Findings in 2025 ETSI Audit - Incident Report #3 – Internal Audit
#1983267 RESOLVED Incident Opened 2025-08-15 · Closed 2026-03-30 · 100% similar
PKIoverheid: TSP KPN Findings in 2025 ETSI Audit - Incident Report #7 – Change Management
#1983269 RESOLVED Incident Opened 2025-08-15 · Closed 2026-01-28 · 100% similar
PKIoverheid: TSP KPN Findings in 2025 ETSI Audit - Incident Report #9 – Lifecycle Management
#1983270 RESOLVED Incident Opened 2025-08-15 · Closed 2026-01-13 · 100% similar
PKIoverheid: TSP KPN Findings in 2025 ETSI Audit - Incident Report #10 – Firewall Rules and Review
#1983271 RESOLVED Incident Opened 2025-08-15 · Closed 2026-01-28 · 100% similar
PKIoverheid: TSP KPN Findings in 2025 ETSI Audit - Incident Report #11 – Anti-Malware Software
#1985816 RESOLVED Incident Opened 2025-08-28 · Closed 2026-05-26 · 100% similar
PKIoverheid: TSP Cleverbase Findings in 2025 ETSI Audit - Incident Report #1 – Incorrect issuer CA listed in CPS
#2008021 RESOLVED Incident Opened 2025-12-30 · Closed 2026-02-09 · 100% similar
PKIoverheid: TSP CIBG Findings in 2025 ETSI Audit - Incident Report #1 – Document Management
#2008023 RESOLVED Incident Opened 2025-12-30 · Closed 2026-02-19 · 100% similar
PKIoverheid: TSP CIBG Findings in 2025 ETSI Audit - Incident Report #2 – Supply Chain Management

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

Confirm action