Public Discussion of Deutsche Telekom Security CA Inclusion Request

1,724 views
Skip to first unread message

Ryan Dickson

unread,
Nov 1, 2023, 9:08:30 AM11/1/23
to public

All,


This email commences a six-week public discussion of Deutsche Telekom Security’s request to include the following CA certificates as publicly trusted root certificates in one or more CCADB Root Store Member’s program. This discussion period is scheduled to close on December 13, 2023.


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: 00001269


Organization Background Information (listed in CCADB):


Certificates Requesting Inclusion:

  1. Telekom Security SMIME ECC Root 2021:

    • Certificate download links: (CA Repository, crt.sh)

    • Use cases served/EKUs: 

      • Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4

    • Test websites: N/A (S/MIME CA)


  1. Telekom Security TLS ECC Root 2020: 


  1. Telekom Security SMIME RSA Root 2023:

    • Certificate download links: (CA Repository, crt.sh)

    • Use cases served/EKUs: 

      • Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4

      • Client Authentication 1.3.6.1.5.5.7.3.2

    • Test websites: N/A (S/MIME CA)


  1. Telekom Security TLS RSA Root 2023:


Existing Publicly Trusted Root CAs from Deutsche Telekom Security:

  1. T-TeleSec GlobalRoot Class 2:

  • 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

  • Certificate Corpus: here (requires Censys account)

  • Included in: Apple, Chrome, Microsoft, Mozilla

  1. T-TeleSec GlobalRoot Class 3:

  • 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 (requires Censys account)

  • Included in: Apple, Chrome, Microsoft, Mozilla


Relevant Policy and Practices Documentation: 


Most Recent Self-Assessment:


Audit Statements:


Incident Summary (Bugzilla incidents from previous 24 months):



Thanks,
Ryan, on behalf of the CCADB Steering Committee

Moudrick M. Dadashov

unread,
Nov 1, 2023, 2:39:07 PM11/1/23
to Ryan Dickson, public
Thank you. I’m trying to understand the organisational structure of the applicant.

Could someone please introduce us the relationship between Deutsche Telekom GmbH, Deutsche Telekom Security GmbH and T-Systems International GmbH?

Specifically I’m interested to understand their roles within the CA operations.

Thanks,
M.D.


Sent from my Galaxy
--
You received this message because you are subscribed to the Google Groups "CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public+un...@ccadb.org.
To view this discussion on the web visit https://groups.google.com/a/ccadb.org/d/msgid/public/CADEW5O_%3DkLcjqCLTj-XsBzVt94JgD0zA-HYfx9G711QVEr6HYQ%40mail.gmail.com.

stefan...@telekom.de

unread,
Nov 2, 2023, 9:29:17 AM11/2/23
to pub...@ccadb.org, TrustCen...@telekom.de

Hi,

 

For our answer we assume that "Deutsche Telekom AG" is meant rather than "Deutsche Telekom GmbH" (such a company does not exist).

The relationship is as follows:

- Deutsche Telekom AG is the Group’s parent company

- Deutsche Telekom Security GmbH is a 100% subsidiary of Deutsche Telekom AG

- T-Systems International GmbH is a 100% subsidiary of Deutsche Telekom AG

 

With regard to the publicly trusted certificates, T-Systems International GmbH was the owner of the Root CA certificates as well as the operator of all Sub CAs of the Deutsche Telekom Group until 2020.

With the establishment of Deutsche Telekom Security GmbH in 2020, ownership of the Root CAs as well as operation of the Sub CAs of the Deutsche Telekom Group were transferred internally from T-Systems International GmbH to Deutsche Telekom Security GmbH.

As the transfer also included all employees concerned, and operations continued at the same physical locations under the same conditions, the change mainly only took place on paper, with the name "T-Systems International GmbH" being replaced by "Deutsche Telekom Security GmbH" in the relevant documents and contracts.

 

Regarding the change of the Root ownership see also

https://groups.google.com/g/mozilla.dev.security.policy/c/pOu_jWY0SVY/m/2uLyuK4TAwAJ  

 

Greetings

 

Stefan

o   Deutsche Telekom Security is a subsidiary of Deutsche Telekom AG

·        Repository URL: https://www.telesec.de/en/service/downloads/pki-repository/ 

 

Certificates Requesting Inclusion:

1.     Telekom Security SMIME ECC Root 2021:

o   Certificate download links: (CA Repository, crt.sh)

o   Use cases served/EKUs: 

§  Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4

o   Test websites: N/A (S/MIME CA)

 

2.     Telekom Security TLS ECC Root 2020: 

o   Certificate download links: (CA Repository, crt.sh)

o   Use cases served/EKUs: 

§  Server Authentication 1.3.6.1.5.5.7.3.1

§  Client Authentication 1.3.6.1.5.5.7.3.2

o   Test websites:

3.     Telekom Security SMIME RSA Root 2023:

o   Certificate download links: (CA Repository, crt.sh)

o   Use cases served/EKUs: 

§  Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4

§  Client Authentication 1.3.6.1.5.5.7.3.2

o   Test websites: N/A (S/MIME CA)

 

4.     Telekom Security TLS RSA Root 2023:

o   Certificate download links: (CA Repository, crt.sh)

o   Use cases served/EKUs: 

§  Server Authentication 1.3.6.1.5.5.7.3.1

§  Client Authentication 1.3.6.1.5.5.7.3.2

o   Test websites:

§  Valid: https://active.tstlsrr23.test.telesec.de/ 

§  Revoked: https://revoked.tstlsrr23.test.telesec.de/ 

§  Expired: https://expired.tstlsrr23.test.telesec.de/ 

 

Existing Publicly Trusted Root CAs from Deutsche Telekom Security:

1.     T-TeleSec GlobalRoot Class 2:

o   Certificate download links: CA Repository, crt.sh

o   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

o   Certificate Corpus: here (requires Censys account)

o   Included in: Apple, Chrome, Microsoft, Mozilla

2.               T-TeleSec GlobalRoot Class 3:

o   Certificate download links: CA Repository, crt.sh

o   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

o   Certificate Corpus: here (requires Censys account)

o   Included in: Apple, Chrome, Microsoft, Mozilla



Relevant Policy and Practices Documentation: 

·        Certificate Policy - v. 4.0 (Sept. 1, 2023), https://www.telesec.de/assets/downloads/PKI-Repository/Telekom-Security-CP-EN-V4.0.pdf   

·        Certification Practices Statement - v. 6.0 (Sept. 1, 2023), https://www.telesec.de/assets/downloads/PKI-Repository/Telekom-Security-CPS-Public-EN-V6.0.pdf 

 

Most Recent Self-Assessment:

·        https://www.telesec.de/assets/downloads/2023-08-28_Telekom_Security_CCADB_Self_Assessment_Framework_v1.2.xlsx 

 

Audit Statements:

·        Auditor: TÜV Informationstechnik GmbH

·        Audit Criteria: ETSI EN 319 411-1 V1.3.1 (2021-05); ETSI EN 319 411-2, V2.4.1 (2021-11)

·        Date of Audit Letter Issuance: June 21, 2023

·        For Period of Time: April 8, 2022, through April 7, 2023

·        Audit Statement(s):  

 

Incident Summary (Bugzilla incidents from previous 24 months):

·        Improper use of a domain validation method (Bugzilla Bug #1825780)





Thanks,

Ryan, on behalf of the CCADB Steering Committee

--
You received this message because you are subscribed to the Google Groups "CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public+un...@ccadb.org.
To view this discussion on the web visit https://groups.google.com/a/ccadb.org/d/msgid/public/CADEW5O_%3DkLcjqCLTj-XsBzVt94JgD0zA-HYfx9G711QVEr6HYQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public+un...@ccadb.org.

Moudrick M. Dadashov

unread,
Nov 3, 2023, 3:50:45 PM11/3/23
to stefan...@telekom.de, pub...@ccadb.org, TrustCen...@telekom.de
Thank you, Stefan.

Do I understand correctly that, despite of the organisational structure and the relationship between the group members, this CA is fully managed by Deutsche Telekom Security GmbH?

stefan...@telekom.de

unread,
Nov 6, 2023, 2:51:46 AM11/6/23
to m...@ssc.lt, pub...@ccadb.org, Jan.V...@telekom.de, arnold...@telekom.de

Hi Moudrick,

 

yes, these Root-CAs that are the subject of this Root Inclusion Request are fully managed by Deutsche Telekom Security GmbH.

 

Greetings

 

Stefan

Chris Clements

unread,
Dec 6, 2023, 9:56:38 AM12/6/23
to stefan...@telekom.de, m...@ssc.lt, pub...@ccadb.org, Jan.V...@telekom.de, arnold...@telekom.de
All,

This is a reminder that the public discussion period on the inclusion application of Deutsche Telekom Security GmbH will close on Wednesday, December 13, 2023.

Thank you,
-Chris, on behalf of the CCADB Steering Committee

Amir Omidi (aaomidi)

unread,
Dec 18, 2023, 3:06:22 PM12/18/23
to CCADB Public, Chris Clements, m...@ssc.lt, pub...@ccadb.org, jan.v...@telekom.de, arnold...@telekom.de, stefan...@telekom.de
I understand that the period for discussion has closed, but I'd like to offer my $0.02 anyway.

I find the incident response in https://bugzilla.mozilla.org/show_bug.cgi?id=1825780 both lacking in detail, and adversarial in nature. Telekom's response to this incident makes me weary of accepting them into the pool of CAs.

> We determined that the validation of the de-domains could be trusted because the validation was carried out in a secure process directly with DENIC, i.e. the central registry for all de-domains.

I'm worried that this shows a pattern of internal behavior that is at odds with public trust and being a public CA. And a set of behavior that ignores the accepted methods for domain validation.

Thanks,
Amir

Chris Clements

unread,
Dec 21, 2023, 12:23:15 PM12/21/23
to Amir Omidi (aaomidi), CCADB Public, m...@ssc.lt, jan.v...@telekom.de, arnold...@telekom.de, stefan...@telekom.de

On November 1, 2023, we began a six-week, public discussion [1] on the request from Deutsche Telekom Security for inclusion of its root certificate(s):

    • Telekom Security SMIME ECC Root 2021

    • Telekom Security TLS ECC Root 2020

    • Telekom Security SMIME RSA Root 2023

    • Telekom Security TLS RSA Root 2023

    The public discussion period ended on December 13, 2023. 

    Note: the Summary of Discussion below includes an item that was stated after the public discussion period ended and as of the time of this message does not include a response from Deutsche Telekom Security. Deutsche Telekom Security can still respond to this item, if desired.

    ==========================

    Summary of Discussion

    Discussion Item #1: Clarification was sought regarding the applicant's organizational structure and CA management. 

    Deutsche Telekom Security Response to Discussion Item #1: Deutsche Telekom confirmed that the root CA certificates in the inclusion request are fully managed by Deutsche Telekom Security GmbH [2]. The organizational structure was defined [3] as:

      • Deutsche Telekom AG is the Group’s parent company

      • Deutsche Telekom Security GmbH is a 100% subsidiary of Deutsche Telekom AG

      • T-Systems International GmbH is a 100% subsidiary of Deutsche Telekom AG

      Discussion Item #2 [after the public discussion period ended]: A perspective was shared that the content and delivery of a past incident report was worrisome [4].

      ==========================


      We thank community members for their 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).


      Thank you,

      -Chris, on behalf of the CCADB Steering Committee 


      Reply all
      Reply to author
      Forward
      0 new messages