← Entrust cases
Bugzilla #1890123
Incident
Entrust: Failed to provide a preliminary incident report according to TLS BR 4.9.5
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 failure to provide a preliminary incident report as required by TLS Baseline Requirements section 4.9.5. The CA confirmed a mis-issuance incident and acknowledged that they did not meet the 24-hour reporting requirement. They committed to providing a full incident report by April 19, 2024, and outlined the timeline of events leading to the oversight. Entrust has since completed all action items related to improving their incident management procedures and requested the closure of this bug. The resolution was marked as FIXED.
Chronology
- Entrust acknowledged failure to provide a preliminary incident report.
- Entrust completed all action items and requested closure of the bug.
Thread Activity
- Entrust representative — Entrust did not provide a preliminary incident report as required.
- Entrust representative — All action items have been completed, requesting closure of the bug.
- Entrust representative — Requesting closure of the incident if there are no further questions.
Participants
Entrust representative
Mozilla representative
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
Entrust: Test Website Certificates Expired
Entrust: CRLs and OCSP responses not issued as specified in the CPS
Entrust: CRL non-conformance with the TLS BRs
Entrust: S/MIME mailbox address not in subjectAltName
Entrust: Delay in Updating CPS
Entrust: Not updating CPR Problem Reporting Mechanism fields in CCADB
GlobalSign: RSA-1024 leaf certificate issued after 2013-12-31
Entrust: CPS typographical (text placement) error