← GlobalSign nv-sa cases
Bugzilla #1690807 Incident Self Reported Incident

GlobalSign: RSA-1024 leaf certificate issued after 2013-12-31

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 disclosed a compliance failure involving the issuance of a leaf certificate with an RSA-1024 key, which contravenes the Baseline Requirements established over seven years ago. The CA became aware of the issue through a Bugzilla report on February 4, 2021, and promptly revoked the certificate. An incident report was submitted detailing the timeline of events and actions taken, including enabling linting for their certificate issuance processes. Remedial actions have been completed, including the deployment of an additional linter to prevent future occurrences.

Model: gpt-4o-mini Generated: 2026-06-13 21:30 UTC Revised: 2026-06-16 18:55 UTC Confidence: 0.90 17 comments
Chronology
  1. GlobalSign issued a leaf certificate with an RSA-1024 key.
  2. GlobalSign revoked the non-compliant certificate.
  3. GlobalSign submitted a detailed incident report.
  4. GlobalSign completed all remedial actions.
Thread Activity
  1. Sectigo — Reported the issuance of a leaf certificate with an RSA-1024 key.
  2. GlobalSign nv-sa — Confirmed the revocation of the certificate and promised an incident report.
  3. GlobalSign nv-sa — Submitted a detailed incident report outlining the timeline and actions taken.
  4. GlobalSign nv-sa — Announced the completion of all remedial actions.
Participants
Sectigo GlobalSign nv-sa Community commenter Mozilla representative
External References
Similar Local Cases
#1694460 RESOLVED Self Reported Incident Opened 2021-02-23 · Closed 2022-11-14 · 100% similar
GlobalSign: Issuing CA certificate with wrong notBefore date
#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
#1393557 RESOLVED Self Reported Incident Incident Opened 2017-08-24 · Closed 2023-02-22 · 100% similar
GlobalSign: Non-BR-Compliant Certificate Issuance -- RSA key smaller than 2048 bits
#1630870 RESOLVED Self Reported Incident Opened 2020-04-17 · Closed 2023-02-22 · 100% similar
GlobalSign: Certificate issued with RSASSA-PSS public key
#1649937 RESOLVED Self Reported Incident Opened 2020-07-02 · Closed 2023-02-22 · 100% similar
GlobalSign: Incorrect OCSP Delegated Responder Certificate
#1664328 RESOLVED Incident Self Reported Incident Opened 2020-09-10 · Closed 2023-02-22 · 100% similar
GlobalSign: SHA-256 hash algorithm used with ECC P-384 key
#1393555 RESOLVED Self Reported Incident Incident Opened 2017-08-24 · Closed 2023-02-22 · 99% similar
GlobalSign: Non-BR-Compliant Certificate Issuance -- double-dots in dnsName

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

Confirm action