DigiCert: Underscores - Discover

This case concerns a set of DigiCert certificates containing underscore characters that were reported as potentially not being revoked on the required date (Jan 15, 2019). The certificates were described as being used for business-to-business transactions, and the report referenced a customer change-freeze/blackout period (Nov 17, 2018 to Jan 5, 2019) and a company-wide change freeze with only pre-approved changes allowed during that time. DigiCert stated that it planned an extension to complete revocations by no later than February 14, 2019, and it provided a response describing steps to resolve the situation and prevent repetition, including improving communication flow and pace. DigiCert also stated that some certificates had been replaced and would be revoked, while other certificates required an extension to complete revocations. DigiCert confirmed that an incident had occurred and that the details were accurate to the best of its knowledge, and it committed to periodic updates. On 2019-02-14, DigiCert updated that all remaining underscore certificates for the customer had been revoked, and the reporter marked the matter as resolved. The bug is marked RESOLVED with resolution FIXED.

1. 2018-12-26 DigiCert opened an incident report regarding underscore-containing certificates potentially not being revoked on the required date.
2. 2019-01-15 DigiCert reported that some listed certificates had been replaced and would be revoked, while others required revocation completion by Feb 14, 2019.
3. 2019-02-14 DigiCert reported that all remaining underscore certificates for the customer had been revoked.

1. 2018-12-26 DigiCert — Opened the incident report describing underscore-containing certificates and stating they would potentially not be revoked on Jan 15, 2019, with multiple crt.sh links provided.
2. 2018-12-26 Community commenter — Questioned whether the report matched the incident-response template and asked for steps to resolve and prevent future issues.
3. 2019-01-04 Community commenter — Requested that the issue be flagged since it had been over a week and expressed concern about timing.
4. 2019-01-08 DigiCert — Stated that there is no exception/extension expected and that CAs are expected to revoke on the required date.
5. 2019-01-09 DigiCert — Said there was a miscommunication and that an update would be posted answering questions.
6. 2019-01-15 DigiCert — Reported that certain certificates had been replaced and would be revoked, and that remaining certificates required an extension to complete revocations by Feb 14, 2019, including a response to the requested incident-resolution steps.
7. 2019-01-17 Community commenter — Asked Jeremy to confirm whether an incident occurred and whether affected-certificate details were accurate.
8. 2019-01-18 DigiCert — Confirmed an incident occurred (to the best of DigiCert’s knowledge) and reiterated the planned extension to revoke remaining certificates by 14-Feb-2019 with periodic updates.
9. 2019-02-14 DigiCert — Updated that all remaining underscore certificates for the customer had been revoked as of 14-Feb-2019.
10. 2019-02-14 Community commenter — Marked the matter as Resolved.