← Disig, a.s. cases
Bugzilla #2075878 Ca Certificate Compliance Incident Self Reported Incident Repository Issue

Disig self-reported CRL non-compliance in CA Disig Root R2

ASSIGNED Disig, a.s.
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

Disig reported a non-compliant CRL for its legacy CA Disig Root R2. The issue was that the CRL contained prohibited authorityCertIssuer and authorityCertSerialNumber fields in the authorityKeyIdentifier extension, which Disig said violated TLS BR section 7.2.2. Disig stated that the problem was identified after a third-party report, then investigated internally, paused automated CRL generation for the affected profile, and updated the production CRL profile. The company later said a compliant CRL was issued, a zlint issue was opened and fixed, and all action items were completed. Disig requested closure of the incident in its final report.

Model: gpt-5.4-mini Generated: 2026-10-20 17:37 UTC Confidence: 0.97 6 comments
Chronology
  1. CA Disig Root R2 was deployed with default RFC 5280 CRL profile settings.
  2. The TLS BR v2.0.1 mandatory CRL requirements took effect.
  3. Disig was notified about a non-compliant CRL for CA Disig Root R2.
  4. The CRL profile was updated and a compliant CRL was generated and published.
Thread Activity
  1. Disig, a.s. — Disig filed a preliminary incident report saying a third party had reported a non-compliant CRL and that further investigation was ongoing.
  2. Disig, a.s. — Disig said the internal investigation was ongoing and that its other CAs were okay.
  3. Disig, a.s. — Disig posted a full incident report describing the CRL non-compliance, impact, timeline, and remediation.
  4. Disig, a.s. — Disig said it had opened a zlint issue to address the detection gap.
  5. Disig, a.s. — Disig said the patch fixed the issue and the action item was completed.
  6. Disig, a.s. — Disig posted a closure summary stating remediation was complete and requesting closure.
Participants
Disig, a.s.
Related Bugzilla IDs Mentioned
Similar Local Cases
#2073074 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Validation Issue Opened 2026-09-17 · Closed 2026-09-30 · 87% similar
Disig: Multi-purpose Subordinate CA with missing EKU
#1390991 RESOLVED Ca Certificate Compliance Incident Certificate Misissuance Opened 2017-08-16 · Closed 2023-02-22 · 79% similar
Disig: Non-BR-Compliant Certificate Issuance
#2008972 RESOLVED Self Reported Incident Opened 2026-01-07 · Closed 2026-01-28 · 78% similar
Disig: Delayed Full Incident Report
#2007132 RESOLVED Certificate Misissuance Self Reported Incident Opened 2025-12-19 · Closed 2026-02-11 · 77% similar
Disig: Certificates with invalid embedded SCT signature
#2082361 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-10-15 Still Open · 75% similar
certSIGN: Missing the countryName attribute in the Subject DN of a test DV TLS certificate
#2076795 RESOLVED Ca Certificate Compliance Self Reported Incident Incident Repository Issue Opened 2026-09-30 · Closed 2026-10-15 · 74% similar
Certigna: CRL HTTP Media Type
#2081189 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-10-13 Still Open · 74% similar
ANF: Potential TLS BR 7.1.2.8 violations in OCSP responder certificate
#1999850 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Opened 2025-11-13 · Closed 2026-07-01 · 74% similar
Microsoft PKI Services: OCSP Non-Compliance

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

⚠

Confirm action