← SwissSign AG cases
Bugzilla #2034359 Ca Certificate Compliance Self Reported Incident Delayed Revocation Revocation Issue Remediation Tracking

SwissSign delayed revocation incident closed after remediation and final mass revocation testing

RESOLVED FIXED SwissSign AG
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

SwissSign self-reported a delayed revocation incident involving 454,436 S/MIME MV certificates that had to be revoked within 120 hours after Bugzilla 2033000. The company said the revocation missed the BR timeframe because of LDAP workflow issues, a batch-revocation software bug, and a database buffer that was too small. SwissSign reported that all affected certificates were revoked on 2026-04-22 17:32 UTC and later posted a full incident report and closure summary. It then completed remediation work, including runbook updates, software/configuration fixes, and a redesigned mass revocation test procedure covering different certificate states, volume, and load. In the final update, SwissSign said the technical problems were remediated, all action items were completed, and it requested closure; CCADB issued a final call for comments and said the bug would be closed around 2026-10-12.

Model: gpt-5.4-mini Generated: 2026-06-13 20:46 UTC Revised: 2026-10-18 06:01 UTC Confidence: 0.98 10 comments
Chronology
  1. SwissSign completed revocation of the affected S/MIME MV certificates after missing the intended revocation timeframe.
  2. SwissSign posted the full incident report describing the delayed revocation and its contributing factors.
  3. SwissSign reported that updated runbooks had been reviewed by auditors and were now used in production.
  4. SwissSign completed final mass revocation tests for S/MIME and TLS certificate populations.
  5. SwissSign submitted a closure summary and requested that the incident report be closed.
Thread Activity
  1. SwissSign AG — Posted a preliminary self-reported incident report saying performance issues prevented timely revocation and that all affected certificates had been revoked.
  2. SwissSign AG — Corrected the revocation completion time and said the next update would be the full incident report.
  3. SwissSign AG — Posted the full incident report with the revocation count, timeline, contributing factors, and remediation action items.
  4. Community commenter — Asked whether SwissSign had validated production-scale mass revocation capability and requested clarification on readiness and future exercises.
  5. SwissSign AG — Said the action items were still open, explained the testing gaps, and updated the remediation plan with additional action items.
  6. SwissSign AG — Reported that the updated runbooks were reviewed by auditors and are now used in production, with action items #1 and #2 marked done.
  7. SwissSign AG — Described the final mass revocation test setup, results, and said the numbers gave good confidence for revoking the full certificate population within the required time.
  8. SwissSign AG — Marked all remediation action items done and said SwissSign would continue observing the bug for feedback and prepare the closure report.
  9. SwissSign AG — Posted the closure summary, said the technical problems were remediated, and requested closure.
  10. CCADB representative — Issued a final call for comments and said the bug would be closed around 2026-10-12.
Participants
SwissSign AG Community commenter CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2033000 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Policy Document Issue Opened 2026-04-17 · Closed 2026-07-09 · 100% similar
SwissSign: Certificate Profile error for S/MIME MV
#2074466 ASSIGNED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Delayed Revocation Opened 2026-09-22 Still Open · 96% similar
SwissSign: Backdating of 48+h
#1849364 RESOLVED Revocation Issue Self Reported Incident Opened 2023-08-18 · Closed 2023-09-22 · 95% similar
SwissSign: Missed revocation and opening Bugzilla
#2065061 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Policy Document Issue Opened 2026-08-20 · Closed 2026-09-01 · 94% similar
SwissSign: Potential error in stateOrProvinceName
#2057448 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Delayed Revocation Opened 2026-07-24 · Closed 2026-10-02 · 93% similar
SwissSign: Invalid Entry in State field
#2079638 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Ccadb Disclosure Issue Opened 2026-10-08 Still Open · 88% similar
SwissSign: Root CRLs Missing Reason Code
#1731586 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Opened 2021-09-20 · Closed 2023-02-22 · 87% similar
SwissSign: Certificate with key length 16258
#1815466 RESOLVED Revocation Issue Self Reported Incident Opened 2023-02-07 · Closed 2023-04-19 · 87% similar
SwissSign: CRL/OCSP revocation time mismatch

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

⚠

Confirm action