← SECOM Trust Systems CO., LTD. cases
Bugzilla #2068053 Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Revocation Issue

SECOM self-reported issuance of five subordinate CA certificates without Apple prior approval

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 reported that it issued five subordinate CA certificates to Cybertrust Japan Co., Ltd. without obtaining Apple’s prior approval, which was required for an externally operated subordinate CA. SECOM said it discovered the non-compliance during an internal review triggered after Bugzilla 2066068 and reported the matter to the Apple Root Program the same day. Apple later told SECOM that all five subordinate CA certificates were mis-issued and that retrospective approval was not available. SECOM and Cybertrust Japan agreed that all five certificates had to be revoked, and SECOM later confirmed that revocation was completed. SECOM also updated the related CCADB records and submitted reissuance requests to the Chrome Root Program and Apple Root Program. The thread indicates that SECOM continues to investigate the full impact and will provide further updates as information becomes available.

Model: gpt-5.4-mini Generated: 2026-09-06 11:01 UTC Confidence: 0.97 4 comments
Chronology
  1. SECOM issued five subordinate CA certificates to Cybertrust Japan without Apple prior approval.
  2. SECOM identified the non-compliance during an internal review.
  3. SECOM reported the issue to the Apple Root Program and stopped EE issuance under the affected subordinate CAs.
  4. SECOM completed revocation of the five affected subordinate CA certificates.
Thread Activity
  1. Ml representative — SECOM filed a preliminary incident report describing the unauthorized issuance, the affected subordinate CAs, and the planned revocation.
  2. Ml representative — SECOM said it had suspended issuance under the affected subordinate CAs and temporarily extended issuance under two existing subordinate CAs during the transition.
  3. Ml representative — SECOM reported that it had completed revocation of all five subordinate CA certificates, updated CCADB records, and submitted reissuance requests.
Participants
Ml representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2066472 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Policy Document Issue Opened 2026-08-25 Still Open · 88% similar
SECOM: Inaccurate CP/CPS description regarding the basicConstraints extension of OCSP responder certificates by 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)
#1897346 RESOLVED Certificate Misissuance Revocation Issue Opened 2024-05-17 · Closed 2024-07-24 · 88% similar
SECOM: Difference in upper and lower case between CN field and SAN
#2017840 RESOLVED Incident Self Reported Incident Opened 2026-02-19 · Closed 2026-04-30 · 87% similar
SECOM: Repository service disruption affecting subordinate CAs (CTJ)
#1896596 RESOLVED Certificate Misissuance Revocation Issue Opened 2024-05-14 · Closed 2024-07-24 · 85% similar
SECOM: Certificates Issued with lower case value in subject:countryName
#1497703 RESOLVED Self Reported Incident Certificate Misissuance Closure Request Opened 2018-10-09 · Closed 2023-02-22 · 79% similar
SECOM: Undisclosed intermediate certificates
#1391064 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-08-16 · Closed 2023-02-22 · 78% similar
SECOM: Non-BR-Compliant Certificate Issuance
#1398259 RESOLVED Self Reported Incident Incident Closure Request Opened 2017-09-08 · Closed 2023-02-22 · 78% 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