IdenTrust: Improper encoding of wildcard certificate

This case involves IdenTrust Services, LLC, which disclosed an improper encoding issue with wildcard certificates. The CA identified the problem during an audit on August 14, 2017, and confirmed that no new certificates with the issue were issued after that date. IdenTrust provided a formal incident report detailing the issue, the certificates affected, and the steps taken to resolve it, including revocation of the impacted certificates. As of March 23, 2018, all six certificates identified with the encoding issue were revoked. IdenTrust has since implemented pre-issuance certificate linting to prevent future occurrences.

1. 2017-08-14 IdenTrust identified a configuration problem during an audit.
2. 2018-03-23 All six certificates with the encoding issue were revoked.
3. 2018-08-11 IdenTrust implemented pre-issuance certificate linting.

1. 2018-03-15 Fastly representative — Requested an incident report regarding the improper encoding issue.
2. 2018-03-15 IdenTrust Services, LLC — Acknowledged receipt of the bug and committed to providing a formal incident report.
3. 2018-03-16 IdenTrust Services, LLC — Provided a formal report detailing the issue and remediation steps.
4. 2018-03-23 IdenTrust Services, LLC — Confirmed that all six certificates have been revoked.
5. 2018-08-11 IdenTrust Services, LLC — Announced successful implementation of pre-issuance certificate linting.