Disig: Non-BR-Compliant Certificate Issuance

Disig, a.s. disclosed a non-compliance issue regarding the issuance of a TLS/SSL certificate that contained invalid dnsNames. The CA became aware of the issue through a Bugzilla notification and confirmed that only one certificate was affected. Disig has since ceased issuing non-compliant certificates and revoked the problematic certificate. They have implemented a blacklist to prevent future occurrences and are enhancing their internal controls to ensure compliance with the Baseline Requirements. The case has been resolved with all actions completed.

1. 2017-08-16 Disig informed of non-compliance issue via Bugzilla notification.
2. 2017-08-17 Disig revoked the non-compliant certificate.
3. 2017-09-01 Disig deployed a blacklist to prevent issuance of non-compliant certificates.
4. 2017-10-01 Disig implemented post-issuance controls.

1. 2017-08-16 Mozilla representative — Disig must respond to compliance issues found in their certificates.
2. 2017-08-17 Disig, a.s. — Disig confirmed they stopped issuing non-compliant certificates.
3. 2017-09-20 Disig, a.s. — Disig reported on the implementation of a blacklist for TLDs.
4. 2017-11-28 Disig, a.s. — Disig provided an update on progress regarding compliance measures.
5. 2018-02-09 Fastly representative — The case was marked as resolved after all actions were completed.