← SECOM Trust Systems CO., LTD. cases
Bugzilla #2066472 Ca Certificate Compliance Incident Self Reported Incident Policy Document Issue Cp Cps Document

SECOM/CTJ self-reported CP/CPS documentation inconsistency for OCSP responder certificate profiles

ASSIGNED SECOM Trust Systems CO., LTD.
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

SECOM Trust Systems reported a self-identified compliance issue involving Cybertrust Japan (CTJ), a subordinate CA operator in its hierarchy. The issue was that CTJ’s CP/CPS Appendix B incorrectly stated that certain OCSP responder certificate profiles included the basicConstraints extension, while CTJ’s internal profile and the issued certificates did not. SECOM said the 24 affected OCSP responder certificates were issued on 2026-08-07, and that no subscriber certificates were affected. CTJ revised the CP/CPS on 2026-08-26 and began reissuing and replacing the affected certificates, completing that work on 2026-08-28. The full incident report states the non-compliance began when the revised CP/CPS was published on 2026-08-10 and ended when the certificates were replaced on 2026-08-28. The bug remains assigned, and the thread indicates SECOM was continuing its investigation and remediation coordination with CTJ.

Model: gpt-5.4-mini Generated: 2026-09-06 11:00 UTC Confidence: 0.98 7 comments
Chronology
  1. CTJ issued 24 OCSP responder certificates for four subordinate CAs.
  2. CTJ published a revised CP/CPS that incorrectly described the OCSP responder certificate profile.
  3. CTJ revised the CP/CPS and began reissuing the affected OCSP responder certificates.
  4. The 24 affected OCSP responder certificates were replaced.
Thread Activity
  1. Ml representative — SECOM opened a preliminary incident report describing the CP/CPS/profile mismatch and said it was self-reported by CTJ.
  2. Ml representative — SECOM said CTJ had published the revised CP/CPS and started reissuing the affected certificates.
  3. Ml representative — SECOM reported that reissuance and replacement of the 24 affected certificates had been completed.
  4. Ml representative — SECOM filed the full incident report with the timeline, impact, and remediation details.
Participants
Ml representative CCADB representative
Similar Local Cases
#2017840 RESOLVED Incident Self Reported Incident Opened 2026-02-19 · Closed 2026-04-30 · 97% similar
SECOM: Repository service disruption affecting subordinate CAs (CTJ)
#2068053 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-09-01 Still Open · 88% similar
SECOM: Five Subordinate CA Certificates Issued Without Apple Prior Approval for Cybertrust Japan (CTJ)
#2021550 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2026-03-06 · Closed 2026-03-26 · 88% similar
SECOM: 2025 S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)
#1950574 RESOLVED Self Reported Incident Opened 2025-02-26 · Closed 2025-09-15 · 87% similar
SECOM: S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)
#1975624 RESOLVED Self Reported Incident Opened 2025-07-04 · Closed 2025-09-24 · 87% similar
SECOM: Cybertrust Japan's CRL lacks the critical flag in the issuingDistributionPoint extension
#1950574 RESOLVED Ca Certificate Compliance Incident Revocation Issue Opened 2025-02-26 · Closed 2025-09-15 · 86% similar
SECOM: S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)
#1981680 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Linting Quality Issue Opened 2025-08-07 · Closed 2025-09-26 · 80% similar
TunTrust: SSL OV mis-issuance against CP/CPS (Email attribute)
#1398259 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-09-08 · Closed 2023-02-22 · 79% similar
SECOM: Non-BR-Compliant OCSP Responders

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

Confirm action