← GlobalSign nv-sa cases
Bugzilla #1599775 Self Reported Incident Certificate Misissuance

GlobalSign: Wrong EV business category (Non-Commercial Entity vs Private Organization)

RESOLVED FIXED GlobalSign nv-sa
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

GlobalSign reported that it was notified by a third party that three EV SSL certificates identified the organization named in the certificate as a “Non-Commercial Entity.” GlobalSign stated that it reviewed certificates containing “Non-Commercial Entity” and determined that 3 of 65 certificates were non-compliant. GlobalSign decided to revoke the three certificates within five days per the Baseline Requirements and reported that it started and concluded its investigation within 24 hours. GlobalSign also said it reached out to certificate owners and communicated that the certificates needed to be replaced because revocation would follow the Baseline Requirements. In a later update, GlobalSign stated that the three certificates were revoked on 29 November 2019 and that additional training and testing had been rolled out. GlobalSign further described the cause as a breakdown in manual vetting for organizational details and said it added monitoring, monthly reviews, and updated training with testing of staff understanding.

Model: gpt-5.4-nano Generated: 2026-06-13 21:00 UTC Revised: 2026-06-16 18:48 UTC Confidence: 0.86 8 comments
Chronology
  1. GlobalSign was notified by a third party via the report abuse email address about three EV SSL certificates with an incorrect “Non-Commercial Entity” business category.
  2. GlobalSign revoked the three identified non-compliant EV SSL certificates.
Thread Activity
  1. GlobalSign nv-sa — GlobalSign described how it became aware of the issue, its internal response timeline, its review findings (3 non-compliant certificates), and planned revocation and remediation steps, including links to crt.sh IDs.
  2. GlobalSign nv-sa — GlobalSign added that a related issue had been missed in additional internal reviews and said it added compliance monitoring and scheduled monthly reviews.
  3. GlobalSign nv-sa — GlobalSign reported that the three certificates were revoked on 29 November 2019 and that additional training and testing had been rolled out.
  4. Community commenter — Ryan Sleevi asked for deeper systemic root-cause analysis and clarification on what other misunderstandings and process re-evaluations were planned.
  5. GlobalSign nv-sa — GlobalSign responded that training was updated and staff were tested, and it explained the misunderstanding and low request volume as factors, plus planned additional internal investigations.
  6. Community commenter — Ryan stated he had no further follow-up questions.
  7. Fastly representative — W. Thayer indicated it appeared all questions were answered and remediation was complete.
Participants
GlobalSign nv-sa Community commenter Fastly representative
Similar Local Cases
#1707073 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-22 · Closed 2023-02-22 · 100% similar
GlobalSign: Invalid countryName
#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 100% similar
GlobalSign: Invalid stateOrProvinceName and locality pair
#1552586 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-05-17 · Closed 2023-02-22 · 100% similar
GlobalSign: 4 Misissued certificates with invalid CN
#1575880 RESOLVED Self Reported Incident Revocation Issue Validation Issue Opened 2019-08-22 · Closed 2023-02-22 · 100% similar
GlobalSign: SSL Certificates with US country code and invalid State/Prov
#1866806 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-11-27 · Closed 2024-02-01 · 99% similar
GlobalSign: S/MIME Sponsor validated certificates with CommonName value equal to OrganizationName
#1524877 RESOLVED Certificate Misissuance Opened 2019-02-03 · Closed 2023-02-22 · 95% similar
GlobalSign: IP in dnsName
#1714968 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-06-07 · Closed 2023-02-22 · 94% similar
GlobalSign: Incorrect RegNumber-Org Type combination
#1579413 RESOLVED Self Reported Incident Opened 2019-09-06 · Closed 2022-11-14 · 94% similar
GlobalSign: OCSP Responder Returns invalid values for Some Precertificates

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

Confirm action