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

SECOM self-reported issuance of five subordinate CA certificates without Apple prior approval; incident closed after remediation

RESOLVED FIXED 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. The issue was discovered by SECOM during an internal review prompted by Bug 2066068, and SECOM notified the Apple Root Program the same day it identified the non-compliance. Apple later told SECOM that the five subordinate CA certificates were mis-issued and that retrospective approval was not available. SECOM and Cybertrust Japan stopped end-entity issuance under the affected subordinate CAs, and SECOM revoked all five subordinate CA certificates on 2026-09-05. SECOM also updated the corresponding CCADB records and submitted reissuance requests to the Apple and Chrome Root Programs. On 2026-09-15, SECOM said it had completed all remaining action items, including a compliance gate, mandatory training, a tabletop exercise, and an effectiveness review. On 2026-09-24, SECOM posted a report closure summary and requested closure of the incident, and CCADB issued a final call for comments saying the case would be closed around 2026-10-01.

Model: gpt-5.4-mini Generated: 2026-09-06 11:01 UTC Revised: 2026-10-04 08:00 UTC Confidence: 0.98 12 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.
  5. SECOM completed the remaining corrective action items, including a compliance gate, training, and an effectiveness review.
  6. SECOM submitted a report closure summary and requested closure of the incident.
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.
  4. Mitaka representative — A commenter quoted SECOM’s revocation and reissuance update.
  5. Ml representative — SECOM said it completed action items #3, #4, and #5, including a compliance gate, mandatory training, and auditor notification.
  6. Ml representative — SECOM said all action items were complete and that it planned to request closure within one week if there were no outstanding comments or questions.
  7. Ml representative — SECOM posted a report closure summary and requested closure of the incident.
  8. CCADB representative — CCADB issued a final call for comments or questions and said the incident would be closed approximately on 2026-10-01.
Participants
Ml representative Mitaka representative CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2066472 RESOLVED Policy Document Issue Cp Cps Document Self Reported Incident Incident Opened 2026-08-25 · Closed 2026-09-22 · 100% 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 · 98% similar
SECOM: 2025 S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)
#2017840 RESOLVED Incident Self Reported Incident Opened 2026-02-19 · Closed 2026-04-30 · 97% similar
SECOM: Repository service disruption affecting subordinate CAs (CTJ)
#2004654 RESOLVED Certificate Misissuance Opened 2025-12-08 · Closed 2026-02-12 · 88% similar
SECOM: Invalid stateOrProvinceName
#1950574 RESOLVED Ca Certificate Compliance Incident Revocation Issue Opened 2025-02-26 · Closed 2025-09-15 · 88% similar
SECOM: S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)
#2007070 RESOLVED Self Reported Incident Certificate Misissuance Revocation Issue Opened 2025-12-19 · Closed 2026-03-30 · 87% similar
SECOM: Non conformant SCT Encoding Due to SCT Modification by Cybertrust Japan (CTJ)
#2058503 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-07-28 · Closed 2026-09-02 · 86% similar
GlobalSign: SubCA created with incorrect CPS Policy OID
#1950574 RESOLVED Self Reported Incident Opened 2025-02-26 · Closed 2025-09-15 · 86% similar
SECOM: S/MIME CA Modified Opinion Report of Cybertrust Japan (CTJ)

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

⚠

Confirm action