← GlobalSign nv-sa cases
Bugzilla #1714968 Ca Certificate Compliance Self Reported Incident

GlobalSign: Incorrect RegNumber-Org Type combination

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 discovered a compliance issue involving four certificates that had an incorrect combination of registration number and organization type. The issue was identified through a problem report on June 3, 2021. Following the discovery, GlobalSign initiated an investigation and confirmed the need for revocation of the affected certificates. They communicated their remediation plan, which included revoking the certificates by June 8, 2021, and implementing changes to their systems to prevent similar issues in the future. The CA has since completed the necessary changes and confirmed that the identified remedial activities were concluded by July 27, 2021.

Model: gpt-4o-mini Generated: 2026-06-13 21:32 UTC Revised: 2026-06-16 18:56 UTC Confidence: 0.85 16 comments
Chronology
  1. GlobalSign received a problem report regarding incorrect certificate registrations.
  2. All affected certificates were revoked.
  3. Changes to the GCC UI were deployed in production.
Thread Activity
  1. GlobalSign nv-sa — GlobalSign was notified through a problem report about incorrect registration numbers.
  2. GlobalSign nv-sa — GlobalSign provided a timeline of their actions in response to the incident.
  3. GlobalSign nv-sa — GlobalSign detailed the changes implemented to prevent future mis-issuance.
  4. GlobalSign nv-sa — GlobalSign confirmed that changes to the GCC UI have been deployed.
Participants
GlobalSign nv-sa Community commenter Mozilla representative
External References
Similar Local Cases
#1668007 RESOLVED Ca Certificate Compliance Opened 2020-09-29 · Closed 2023-02-22 · 100% similar
GlobalSign: Invalid stateOrProvinceName value
#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
#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
#1623356 RESOLVED Ca Certificate Compliance Opened 2020-03-18 · Closed 2023-02-22 · 100% similar
GlobalSign: Misissuance of QWAC Certificates
#1649937 RESOLVED Self Reported Incident Opened 2020-07-02 · Closed 2023-02-22 · 100% similar
GlobalSign: Incorrect OCSP Delegated Responder Certificate
#1630870 RESOLVED Self Reported Incident Opened 2020-04-17 · Closed 2023-02-22 · 98% similar
GlobalSign: Certificate issued with RSASSA-PSS public key
#1664328 RESOLVED Incident Self Reported Incident Opened 2020-09-10 · Closed 2023-02-22 · 98% similar
GlobalSign: SHA-256 hash algorithm used with ECC P-384 key

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

Confirm action