Sectigo: "Default City" in Subject:localityName

This case involves Sectigo's disclosure of a compliance issue where multiple certificates contained 'Default City' in the localityName field, indicating a failure to validate this information. The issue was reported to Sectigo on May 2, 2019, leading to an immediate investigation and the revocation of affected certificates. Sectigo has since implemented improvements to their validation processes, including automated checks to prevent similar issues in the future. The case has been resolved with all necessary actions completed and ongoing developments planned to enhance compliance.

1. 2019-05-02 Initial report received regarding certificates with 'Default City' in localityName.
2. 2019-05-03 Revocation of identified certificates commenced.
3. 2019-10-12 Geofencing check to avoid issuing certificates to embargoed areas went live.

1. 2019-05-02 Fastly representative — Reported the issue of 'Default City' in localityName and requested an incident report.
2. 2019-07-12 Sectigo — Apologized for the delayed response and promised to provide the incident response.
3. 2019-11-18 Sectigo — Indicated that the issue was resolved and requested to close the bug.
4. 2019-12-09 Fastly representative — Confirmed that all questions have been answered and remediation is complete.