Entrust: Non-BR-Compliant Certificate Issuance

RESOLVED FIXED Entrust

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

Entrust disclosed a compliance issue regarding the issuance of TLS/SSL certificates that contained non-compliant metadata, specifically a hyphen in the organizational unit (OU) field. The CA first became aware of the issue through a forum discussion on August 9, 2017, and confirmed that it had ceased issuing such certificates. Entrust identified five certificates with the problematic metadata, two of which had already expired, while the remaining three were set to expire soon. The CA decided not to revoke the unexpired certificates, citing no security risks. Entrust has since implemented enhanced education and software checks to prevent future occurrences. The issue was marked as resolved after the necessary changes were completed.

Model: gpt-4o-mini Generated: 2026-06-13 17:04 UTC Revised: 2026-06-16 18:34 UTC Confidence: 0.90 13 comments

Chronology

2017-08-09 Entrust became aware of compliance issues through a forum discussion.
2017-11-27 Entrust completed deployment of software fail-safe checks to prevent issuance of non-compliant certificates.

Thread Activity

2017-08-16 Mozilla representative — Reported compliance issues with certificates issued by Entrust.
2017-08-18 Entrustdatacard representative — Confirmed that Entrust has stopped issuing non-compliant certificates.
2017-08-21 Entrustdatacard representative — Stated that no security issues were found with the previously issued certificates.
2017-11-30 Entrustdatacard representative — Announced completion of software fail-safe checks for OU values.

Participants

Mozilla representative Entrustdatacard representative Community commenter Titanous representative

External References

Original Bugzilla Case

Similar Local Cases

#1448986 RESOLVED Self Reported Incident Opened 2018-03-26 · Closed 2023-02-22 · 91% similar

Entrust: IP Address in dNSName form

AI Summary CA Owner

#1599484 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-11-26 · Closed 2023-02-22 · 90% similar

Entrust: EV Certificates Issued with Business Category "Non-Commercial" when it should have been set to "Private Organization"

AI Summary CA Owner

#1391056 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2017-08-16 · Closed 2023-02-22 · 89% similar

NetLock: Non-BR-Compliant Certificate Issuance

AI Summary CA Owner

#1658792 RESOLVED Self Reported Incident Opened 2020-08-12 · Closed 2023-02-22 · 89% similar

Entrust: Invalid data in State/Province Field

AI Summary CA Owner

#1390974 RESOLVED Certificate Misissuance Self Reported Incident Opened 2017-08-16 · Closed 2023-02-22 · 88% similar

Actalis: Non-BR-Compliant Certificate Issuance

AI Summary CA Owner

#1391087 RESOLVED Self Reported Incident Opened 2017-08-16 · Closed 2023-02-22 · 87% similar

Visa: Non-BR-Compliant Certificate Issuance

AI Summary CA Owner

#1390998 RESOLVED Self Reported Incident Certificate Misissuance Opened 2017-08-16 · Closed 2023-02-22 · 87% similar

Kamu SM: Non-BR-Compliant Certificate Issuance

AI Summary CA Owner

#1512018 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2018-12-04 · Closed 2023-02-22 · 83% similar

Entrust: Certificate issued with '-' in ST field

AI Summary CA Owner