T-Systems has applied to add the “T-TeleSec GlobalRoot Class 3” root
certificate, turn on the Websites trust bit, and enable EV.
T-Systems is a wholly-owned subsidiary of Deutsche Telekom AG.
The request is documented in the following bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=669849
And in the pending certificates list here:
http://www.mozilla.org/projects/security/certs/pending/#T-Systems
Summary of Information Gathered and Verified:
https://bugzilla.mozilla.org/attachment.cgi?id=619163
Noteworthy points:
* The primary documents are the CP, CPS, and the ServerPass CP/CPS. The
documents are provided in English.
Document Repository:
http://www.telesec.de/pki/roots.html
ServerPass CP/CPS (German):
http://www.telesec.de/serverpass/cps.html
ServerPass CP/CPS (English):
https://bugzilla.mozilla.org/attachment.cgi?id=555341
CP:
http://www.telesec.de/pki/service/GlobalRoot_Class_3/cp_en.pdf
CPS:
http://www.telesec.de/pki/service/GlobalRoot_Class_3/cps_en.pdf
This is an offline root that will have internally-operated subordinate
CAs corresponding to the high security services that are offered.
The request is to turn on the Websites trust bit.
* ServerPass CP/CPS section 3.2.2: The initial request can only be
placed after successful registration in the customer portal
<myServerPass>. In order to confirm the legal person named in the
Subject Distinguished Name (subjectDN) of the certificate under
Organization (O), the following document is required according to the
business category:
Legal person: The request form signed by an authorized signatory.
Authority: The request form signed by an authorized representative of
the authority and stamped with the official seal.
Association: The certified copy (no more than 30 days old) of the
register of associations excerpt must be submitted together with the
signed request form.
Trader(s): The certified copy (no more than 30 days old) of a current
trade license and the personal ID of the trader must be submitted
together with the signed request form.
The following is checked for all business categories:
- Is the information on the request form identical to the information in
the Certificate Signing Request (CSR) of the online request?
- Does the company name of the organization/company correspond to the
entry in the electronic commercial register or comparable directories?
Do current organization documents (no more than 30 days old) issued by a
competent authority also confirm the organization's existence (e.g.,
register of associations or comparable document, official stamp)?
- The authorization of the responsible contact at the organization named
in the request (legal person),
- Does the domain name correspond to the official directories? Does the
customer own the domain; i.e., has he been given the exclusive right of
use by means of a corresponding authorization?
- If a third party carries out the certificate request/management on
behalf of the organization, it must have a corresponding written
authorization concerning the transfer of rights
- Are any necessary Whois entries available.
Additional checks are carried out as required.
* Additionally there is an “Operation Manual” for Trust Center staff
including employees working on the registration and validation
procedure. To summarize,
www.denic.de is the first tool which is used to
verify the ownership of a domain under TLD .de , which most of the
issued certificates are. For international TLD WHOIS is used instead
(
www.whois.net). The domainholder must be the same organization stated
within the O field of the certificate. If this is not the case, a letter
of attorney is needed stating, that the one applying for the certificate
is acting on behalf of the domain owner.
The request is to also enable EV.
* ServerPass CP/CPS section 3.2.2: TeleSec ServerPass EV: The initial
request can only be placed after successful registration in the customer
portal <myServerPass>. The required checks are carried out in accordance
with [WTEVGUIDE].
[WTEVGUIDE] = Guidelines For The Issuance and Management Of Extended
Validation Certificates, The CA / Browser Forum Version 1.2, October 1, 2009
* EV Policy OID: 1.3.6.1.4.1.7879.13.24.1
* Root Cert URL:
http://www.telesec.de/downloads/GlobalRoot_Class_3.cer
* Test Website:
https://root-class3.test.telesec.de
* CRL
http://pki.telesec.de/rl/GlobalRoot_Class_3.crl
http://crl.serverpass.telesec.de/rl/EV_SSL_CA_Class_3.crl (NextUpdate:
24hours)
ServerPass CP/CPS section 4.9.7: The certificate revocation list (CRL),
which contains the revoked certificates of end entities, is updated
twice a day and published by the repository.
* OCSP
OCSP URI in EE Cert:
http://ocsp.telesec.de/ocspr
OCSP URI in EV Intermediate Cert:
http://ocsp.serverpass.telesec.de/ocspr
Global Root Class 3 CPS section 4.9.9: Sub-CAs must maintain an OCSP
responder to validate issued certificates. OCSP responses must have a
maximum expiration time of ten (10) days. The OCSP repository must be
updated at least every four (4) days.
* Audit: Annual audits are performed by Ernst & Young GmbH according to
the WebTrust for CA and EV criteria, and posted on the
webtrust.org website.
https://cert.webtrust.org/SealFile?seal=1219&file=pdf
https://cert.webtrust.org/SealFile?seal=1220&file=pdf
* Potentially Problematic Practices – None Noted
(
http://wiki.mozilla.org/CA:Problematic_Practices):
This begins the discussion of the request from T-Systems to add the
“T-TeleSec GlobalRoot Class 3” root certificate, turn on the Websites
trust bit, and enable EV. At the conclusion of this discussion I will
provide a summary of issues noted and action items. If there are
outstanding issues, then an additional discussion may be needed as
follow-up. If there are no outstanding issues, then I will recommend
approval of this request in the bug.
Kathleen