This email commences a six-week public discussion of Cybertrust Japan / JCSI’s request to include the following three (3) certificates as publicly trusted root certificates in one or more CCADB Root Store Operator’s program. This discussion period is scheduled to close on June 21, 2024.
The purpose of this public discussion process is to promote openness and transparency. However, each Root Store makes its inclusion decisions independently, on its own timelines, and based on its own inclusion criteria. Successful completion of this public discussion process does not guarantee any favorable action by any Root Store.
Anyone with concerns or questions is urged to raise them on this CCADB Public list by replying directly in this discussion thread. Likewise, a representative of the applicant must promptly respond directly in the discussion thread to all questions that are posted.
CCADB Case Number: 00000585
Organization Background Information (listed in CCADB):
CA Owner Name: Cybertrust Japan / JCSI
Website: https://www.cybertrust.co.jp/
Address: ARK Hills Sengokuyama Mori Tower 35F, 1-9-10 Roppongi, Minato-ku, Tokyo, 106-0032, Japan
Problem Reporting Mechanisms: evc-r...@cybertrust.ne.jp
Organization Type: Public Corporation
Repository URL: https://www.cybertrust.ne.jp/ssl/repository_rt/
Certificates Requested for Inclusion:
SecureSign Root CA12 (included in case 00000585):
Certificate download links: (CA Repository, crt.sh)
Use cases served/EKUs:
Server Authentication (TLS) 1.3.6.1.5.5.7.3.1
Client Authentication 1.3.6.1.5.5.7.3.2
Test websites:
SecureSign Root CA14 (included in case 00000585):
Certificate download links: (CA Repository, crt.sh)
Use cases served/EKUs:
Server Authentication (TLS) 1.3.6.1.5.5.7.3.1
Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
Client Authentication 1.3.6.1.5.5.7.3.2
Code Signing 1.3.6.1.5.5.7.3.3
Time Stamping 1.3.6.1.5.5.7.3.8
Test websites:
SecureSign Root CA15 (included in case 00000585):
Certificate download links: (CA Repository, crt.sh)
Use cases served/EKUs:
Server Authentication (TLS) 1.3.6.1.5.5.7.3.1
Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
Client Authentication 1.3.6.1.5.5.7.3.2
Code Signing 1.3.6.1.5.5.7.3.3
Time Stamping 1.3.6.1.5.5.7.3.8
Test websites:
Existing Publicly Trusted Root CAs from Cybertrust Japan / JCSI:
SecureSign RootCA11:
Certificate download links: (CA Repository, crt.sh)
Use cases served/EKUs:
Server Authentication (TLS) 1.3.6.1.5.5.7.3.1
Client Authentication 1.3.6.1.5.5.7.3.2
Certificate corpus: here (Censys login required)
Included in: Chrome, Microsoft, and Mozilla
Cybertrust iTrust Root Certification Authority:
Certificate download links: (CA Repository, crt.sh)
Use cases served/EKUs:
Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
Code Signing 1.3.6.1.5.5.7.3.3
Certificate corpus: here (Censys login required)
Included in: Microsoft
Relevant Policy and Practices Documentation:
The following policy documents apply to all applicant root CA certificates:
Most Recent Self-Assessment:
The following Self-Assessment applies to all applicant root CA certificates:
https://bugzilla.mozilla.org/attachment.cgi?id=9370203 (completed 12/25/2023)
Audit Statements:
Audit Criteria: WebTrust
Date of Audit Issuance: 12/6/2023
For Period Ending: 10/5/2023
Audit Statement(s):
Standard Audit (covers all applicant root CA certificates)
TLS BR Audit (covers all applicant root CA certificates)
TLS EVG Audit (covers all applicant root CA certificates)
Incident Summary (Bugzilla incidents from previous 24 months):
1827490: Cybertrust Japan: CRL signature algorithm encoding error
Thank you
-Chris, on behalf of the CCADB Steering Committee
On May 10, 2024, we began a six-week, public discussion[1] on the request from Cybertrust Japan / JCSI for inclusion of its root certificate(s):
The public discussion period has now ended.
We did not receive any objections or other questions or comments in opposition to Cybertrust Japan / JCSI’s request. We thank the community for its review and consideration during this period. Root Store Programs will make final inclusion decisions independently, on their own timelines, and based on each Root Store Member’s inclusion criteria. Further discussion may take place in the independently managed Root Store community forums (i.e., MDSP).
[1] https://groups.google.com/a/ccadb.org/g/public/c/4OuyyOD-7ng/m/nl-bbjr-AQAJ
Thank you
-Chris, on behalf of the CCADB Steering Committee
P.S. Members of this group may have noticed recent spam calendar invitation(s) related to past root inclusion public discussions. The CCADB Steering Committee only conducts root inclusion public discussions within this group as detailed on ccadb.org. Please ignore any spam as we continue to refine group moderation. The original senders have been blocked from the community.