← Izenpe S.A. cases
Bugzilla #1996857 Self Reported Incident Certificate Misissuance

IZENPE: not allowed Key Usage in ocsp responder certificate

RESOLVED FIXED Izenpe S.A.
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

Izenpe S.A. self-reported a compliance issue regarding their OCSP responder certificates, which included the 'nonRepudiation' key usage extension, contrary to the Baseline Requirements that only permit 'digitalSignature'. This non-compliance was identified on October 28, 2025, during a review prompted by a previous bug. The CA issued new OCSP responder certificates that comply with the updated requirements, and they began signing OCSP responses on November 24, 2025. Izenpe has committed to continuous monitoring of their compliance with the Baseline Requirements to prevent future issues.

Model: gpt-4o-mini Generated: 2026-06-13 21:16 UTC Revised: 2026-06-16 19:18 UTC Confidence: 0.90 11 comments
Chronology
  1. BR 2.0.0 changes regarding OCSP responder key usage came into effect.
  2. Non-compliance with OCSP responder certificates was identified.
  3. New compliant OCSP responder certificates were issued.
  4. New OCSP responder certificates began signing OCSP responses.
Thread Activity
  1. Izenpe S.A. — Izenpe discovered that their OCSP responder certificates did not comply with the BRs.
  2. Izenpe S.A. — New OCSP responder certificates have been issued and will start signing OCSP requests.
  3. Izenpe S.A. — The new OCSP responder certificates have started signing OCSP responses.
  4. CCADB representative — Final call for comments on the incident report before closure.
Participants
Izenpe S.A. Snowflake representative CCADB representative
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#1876565 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-01-25 · Closed 2024-04-06 · 91% similar
Izenpe: Not allowed Qualifier ID OID on Certificate Policies extension
#1921254 RESOLVED Certificate Misissuance Self Reported Incident Opened 2024-09-26 · Closed 2025-02-19 · 91% similar
Izenpe: Duplicate attribute in Subject
#1976256 RESOLVED Self Reported Incident Opened 2025-07-08 · Closed 2025-11-20 · 91% similar
IZENPE: IssuingDistributionPoint extension in CRLs not marked as Critical
#1945867 RESOLVED Self Reported Incident Certificate Misissuance Opened 2025-02-04 · Closed 2025-04-18 · 90% similar
Izenpe: Incorrect Unicode characters in Subject
#1948600 RESOLVED Self Reported Incident Policy Document Issue Opened 2025-02-17 · Closed 2025-07-01 · 88% similar
IZENPE: Outdated CPS for Izenpe Root
#1959721 RESOLVED Self Reported Incident Certificate Misissuance Opened 2025-04-10 · Closed 2025-06-12 · 81% similar
Lawtrust: The S/MIME CA’s policy identifiers did not align with the CA/Browser Forum Requirements.
#1391054 RESOLVED Ca Certificate Compliance Incident Certificate Misissuance Opened 2017-08-16 · Closed 2023-02-22 · 80% similar
Izenpe: Non-BR-Compliant Certificate Issuance
#1653284 RESOLVED Self Reported Incident Opened 2020-07-16 · Closed 2023-02-22 · 80% similar
Izenpe: incorrect value in stateOrProvinceName

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

Confirm action