← Actalis cases
Bugzilla #2056934 Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Cp Cps Document

Actalis: late CP/CPS update for AgID subordinate CAs; bug resolved after closure request

RESOLVED FIXED Actalis
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 Actalis’s failure to publish updated CP/CPS documents for the AgID SSL Server CA and AgID CA1 subordinate CAs within the required annual timeframe. The issue was first reported by a third party, and Actalis said the updated documents and corresponding CCADB disclosures were published on 2026-07-22, 12 days after the applicable deadline. Actalis stated that no end-user certificates were affected and that issuance was not stopped because the problem was limited to document maintenance and disclosure. Since the previous summary, Actalis reported that all remaining action items were completed: the internal procedure was updated on 2026-09-03, the AgID training session was held on 2026-09-22, and the customer-relationships training session was held on 2026-09-25. Actalis then published a closure summary requesting closure, and CCADB issued a final call for comments saying the report would be closed around 2026-10-05 if there were no further questions. The bug is now RESOLVED with FIXED.

Model: gpt-5.4-mini Generated: 2026-07-26 06:21 UTC Revised: 2026-10-11 06:01 UTC Confidence: 0.99 13 comments
Chronology
  1. The annual publication deadline for the applicable CP/CPS documents was missed.
  2. Updated CP/CPS documents were published for the AgID SSL Server CA and AgID CA1 sub-CAs.
  3. Corresponding CCADB records were updated and the non-compliance ended.
  4. Actalis updated the internal procedure governing CP/CPS document changes for the AgID-branded subordinate CAs.
  5. A dedicated training and awareness session with AgID was held and documented.
  6. A training session for the department responsible for managing customer relationships was held and documented.
Thread Activity
  1. Staff representative — Opened a preliminary incident report saying the published CPS was older than 365 days, the updated documents and CCADB information were published, no end-user certificates were impacted, and a full report would follow.
  2. Staff representative — Said internal analysis was continuing and that the full incident report would be published within the expected timeline.
  3. Staff representative — Published the full incident report stating the bug was about failure to publish CP/CPS documents within the required annual timeframe and that the issue was limited to document maintenance and disclosure.
  4. Staff representative — Said Actalis was on track with the planned action items and was continuing to monitor the bug.
  5. Staff representative — Repeated that Actalis was on track with the planned action items and was continuing to monitor the bug.
  6. Staff representative — Repeated that Actalis was on track with the planned action items and was continuing to monitor the bug.
  7. Staff representative — Repeated that Actalis was on track with the planned action items and was continuing to monitor the bug.
  8. Staff representative — Said the internal procedure governing CP/CPS document changes was updated on 2026-09-03, so Action Item 2 is complete, and weekly updates will continue.
  9. Staff representative — Said Actalis was on track with the planned action items and was continuing to monitor the bug.
  10. Staff representative — Said the dedicated training and awareness session with AgID was held and documented on 2026-09-22, so Action Item 3 is closed, and Action Item 4 was scheduled for 2026-09-25.
  11. Staff representative — Said the training session for the department responsible for managing customer relationships was held and documented on 2026-09-25, so Action Item 4 is complete.
  12. Staff representative — Published the closure summary stating the annual CP/CPS update was late, the documents and CCADB disclosures were updated on 2026-07-22, all action items were completed, and closure was requested.
  13. CCADB representative — Issued a final call for comments or questions and said the incident report would be closed around 2026-10-05 if there were no further questions.
Participants
Staff representative CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2049960 ASSIGNED Ca Certificate Compliance Ccadb Disclosure Issue Problem Reporting Failure Information Request Opened 2026-06-24 Still Open · 92% similar
Actalis: Undisclosed Subordinate CA Certificate
#2060581 ASSIGNED Ca Certificate Compliance Certificate Misissuance Externally Reported Incident Revocation Issue Opened 2026-08-04 Still Open · 89% similar
Actalis: Issuance of Server TLS Certificates with id-kp-clientAuth against CPS
#2077464 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Delayed Revocation Opened 2026-10-02 Still Open · 88% similar
Actalis: Root CA CRL not published within 24 hours after recording revocations
#2059735 RESOLVED Ca Certificate Compliance Incident Problem Reporting Failure Remediation Tracking Opened 2026-07-31 · Closed 2026-09-14 · 85% similar
Asseco DS / Certum: Delayed publication of Full Incident Report for Bug 2055775
#2053948 RESOLVED Ca Certificate Compliance Self Reported Incident Ccadb Disclosure Issue Incident Opened 2026-07-09 · Closed 2026-10-02 · 84% similar
IdenTrust: Delayed disclosure of Intermediate CA in CCADB
#2050274 RESOLVED Incident Ccadb Disclosure Issue Problem Reporting Failure Remediation Tracking Opened 2026-06-24 · Closed 2026-08-04 · 84% similar
FNMT: Delay in incident disclosure reporting for Bug 2049012
#2058261 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Policy Document Issue Opened 2026-07-27 Still Open · 83% similar
Google Trust Services: CPS Missing root program attestation
#2065157 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Delayed Revocation Opened 2026-08-20 · Closed 2026-09-28 · 83% similar
SwissSign: Delayed revocation in Bug 2057448

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

⚠

Confirm action