TeliaSonera Server Certificate Policy and Certification Practice Statement

Transcription

1 TeliaSonera Server Certificate Policy and Certification Practice Statement v.1.4 TeliaSonera Server Certificate Policy and Certification Practice Statement CA name Validation OID TeliaSonera Server CA v1 OV TeliaSonera Server CA v2 TeliaSonera Extended Validation SSL CA v1 EV Revision Date: 16 th November 2015 Version: 1.4 Published by: TeliaSonera

2 TeliaSonera Server Certificate CP and CPS No part of this document may be reproduced, modified or distributed in any form or by any means, in whole or in part, or stored in a database or retrieval system, without prior written permission of TeliaSonera. However, permission generally applies for reproducing and disseminating this CPS in its entirety provided that this is at no charge and that no information in the document is added to, removed or changed. Page II

3 TeliaSonera Server Certificate CP and CPS Table of Contents Table of Contents...III Revision History... VII 1 INTRODUCTION Overview Document name and identification PKI participants Certification authorities Registration authorities Subscribers Relying parties Other participants Certificate usage Appropriate certificate uses Prohibited certificate uses Policy administration Organization administering the document Contact person Person determining CPS suitability for the policy CPS approval procedures Definitions and acronyms PUBLICATION AND REPOSITORY RESPONSIBILITIES Repositories CPS Repository Revocation Information Repository Certificate Repository Publication of certification information Time or frequency of publication Access controls on repositories IDENTIFICATION AND AUTHENTICATION Naming Types of names Need for names to be meaningful Anonymity or pseudonymity of Subscribers Rules for interpreting various name forms Uniqueness of names Recognition, authentication, and role of trademarks Initial identity validation Method to prove possession of private key Authentication of organization identity Authentication of individual identity Non-verified Subscriber information Validation of authority Criteria for interoperation Identification and authentication for re-key requests Identification and authentication for routine re-key Identification and authentication for re-key after revocation Identification and authentication for revocation request CERTIFICATE LIFE-CYCLE OPERATIONAL REQUIREMENTS Certificate Application Who can submit a certificate application Enrollment process and responsibilities Certificate application processing Performing identification and authentication functions Approval or rejection of certificate applications Page 3

4 TeliaSonera Server Certificate CP and CPS Time to process certificate applications Certificate Authority Authorization (CAA) Certificate issuance CA actions during certificate issuance Notification to Subscriber by the CA of issuance of certificate Certificate acceptance Conduct constituting certificate acceptance Publication of the certificate by the CA Notification of certificate issuance by the CA to other entities Key pair and certificate usage Subscriber private key and certificate usage Relying party public key and certificate usage Certificate renewal Circumstance for certificate renewal Who may request renewal Processing certificate renewal requests Notification of new certificate issuance to Subscriber Conduct constituting acceptance of a renewal certificate Publication of the renewal certificate by the CA Notification of certificate issuance by the CA to other entities Certificate re-key Certificate modification Certificate revocation and suspension Circumstances for revocation Who can request revocation Procedure for revocation request Revocation request grace period Time within which CA must process the revocation request Revocation checking requirement for relying parties CRL issuance frequency Maximum latency for CRLs On-line revocation/status checking availability On-line revocation checking requirements Other forms of revocation advertisements available Special requirements regarding key compromise Circumstances for suspension Who can request suspension Procedure for suspension request Limits on suspension period Certificate status services Operational characteristics Service availability Optional features End of subscription Key escrow and recovery Key escrow and recovery policy and practices Session key encapsulation and recovery policy and practices FACILITY, MANAGEMENT, AND OPERATIONAL CONTROLS TECHNICAL SECURITY CONTROLS Key pair generation and installation Key pair generation Private key delivery to Subscriber Public key delivery to certificate issuer CA public key delivery to relying parties Key sizes Public key parameters generation and quality checking Key usage purposes (as per X.509 v3 key usage field) Private key protection and cryptographic module engineering controls Cryptographic module standards and controls Private key (n out of m) multi-person control Page 4

5 TeliaSonera Server Certificate CP and CPS Private key escrow Private key backup Private key archival Private key transfer into or from a cryptographic module Private key storage on cryptographic module Method of activating private key Method of deactivating private key Method of destroying private key Cryptographic module rating Other aspects of key pair management Public key archival Certificate operational periods and key pair usage periods Activation data Activation data generation and installation Activation data protection Other aspects of activation data CERTIFICATE, CRL, AND OCSP PROFILES Certificate profile Version number(s) Certificate extensions Algorithm object identifiers Name forms Name constraints Certificate policy object identifier Usage of Policy Constraints extension Policy qualifiers syntax and semantics Processing semantics for the critical Certificate Policies extension CRL profile Version number(s) CRL and CRL entry extensions OCSP profile Version number(s) OCSP extensions COMPLIANCE AUDIT AND OTHER ASSESSMENTS Frequency or circumstances of assessment Identity/qualifications of assessor Assessor's relationship to assessed entity Topics covered by assessment Actions taken as a result of deficiency Communication of results OTHER BUSINESS AND LEGAL MATTERS Fees Certificate issuance or renewal fees Certificate access fees Revocation or status information access fees Fees for other services Refund policy Financial responsibility Confidentiality of business information Privacy of personal information Intellectual property rights Representations and warranties Disclaimers of warranties Limitations of liability Indemnities Term and termination Term Termination Page 5

6 TeliaSonera Server Certificate CP and CPS Effect of termination and survival Individual notices and communications with participants Amendments Procedure for amendment Notification mechanism and period See Circumstances under which OID must be changed Dispute resolution provisions Governing law Compliance with applicable law Miscellaneous provisions Other provisions...35 ACRONYMS...36 DEFINITIONS...37 Page 6

7 Revision History Version Version date Change Author th June 2012 The first official version TeliaSonera CA Policy Management team th September 2012 Fixed minor errors in references TeliaSonera CA Policy Management team st December 2012 Added OCSP support, In validation a call back to technical contact person is an option, Fixed AIA extension description, Mandatory 2048 bit RSA key length TeliaSonera CA Policy Management team rd May 2013 Geographical definition to Server Certificates, Suspension no more used, small technical fixes 1.2 3rd April 2014 All Subject fields except O and OU will refer to registered O location. Small fixes and clarifications th April 2015 Extended Validation (EV) certificate processes were included, TeliaSonera Server CA v2 added, CA must understand all extensions in 3.2.4, validity max limited to 3y, OCSP specification rewritten, small clarifications in many places, fixed contact details th November 2015 Clarifications mainly to EV processes, Revocation link added, CAA record handling TeliaSonera CA Policy Management team TeliaSonera CA Policy Management team TeliaSonera CA Policy Management team TeliaSonera CA Policy Management team Page 7

8 1 INTRODUCTION 1.1 Overview A Certification Practice Statement (CPS) is a Certification Authority s (CA) description of the practices it follows when issuing certificates. The purpose of this CPS is to describe the procedures that the TeliaSonera Server CA v1-2 and TeliaSonera Extended Validation SSL CA v1 use when issuing certificates, and that all Registration Authorities, Subscribers and Relying Parties shall follow in connection with these certificates. This CPS describes the procedures and routines which apply when registering and completing a certificate and for revoking and revocation checking of certificates. This CPS will refer to separate TeliaSonera Production CPS, which describes the premises, procedures and routines which apply for the Production of TeliaSonera CA Services. This CPS generally conforms to the IETF PKIX Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practice Statement Framework (also known as RFC 3647). This document is divided into nine sections: Section 1 - provides an overview of the policy and set of provisions, as well as the types of entities and the appropriate applications for certificates. Section 2 - contains any applicable provisions regarding identification of the entity or entities that operate repositories; responsibility of a PKI participant to publish information regarding its practices, certificates, and the current status; frequency of publication; and access control on published information. Section 3 - covers the identification and authentication requirements for certificate related activity. Section 4 - deals with certificate life-cycle management and operational requirements including application for a certificate, revocation, suspension, audit, archival and compromise. Section 5 - covers facility, management and operational controls (physical and procedural security requirements). Section 6 - provides the technical controls with regard to cryptographic key requirements. Section 7 - defines requirements for certificate, Certificate Revocation List (CRL) and Online Certificate Status Protocol (OCSP) formats. This includes information on profiles, versions, and extensions used. Section 8 - addresses topics covered and methodology used for assessments/audits; frequency of compliance audits or assessments; identity and/or qualifications of the personnel performing the audit or assessment; actions taken as a result of deficiencies found during the assessment; and who is entitled to see results of an assessment. Section 9 - covers general business and legal matters: the business issues of fees, liabilities, obligations, legal requirements, governing laws, processes, and confidentiality. All certificates containing the OID value are so called Organization Validation (OV) SSL certificates and conform to the current version of the Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates published at In the event of any inconsistency between this document and those Documents, those Documents take precedence over this document. All certificates containing the OID value are so called Extended Validation (EV) certificates and conform to the current version of the Guidelines For The Issuance And Management Of Extended Validation Certificates published at In the event of any inconsistency between this document and those Documents, those Documents take precedence over this document. TeliaSonera SSL certificates provide a mean for relaying parties to evaluate trust when relying on such certificates. TeliaSonera SSL certificates are always organization validated (OV) certificates meaning that CA has verified the name and some other details of the entity that controls the website from official registers. TeliaSonera Extended Validation ("EV") Certificates are intended to provide enhanced assurance of the identity of the legal entity that controls a website, including the entity's name, address of Place of Business, Jurisdiction of Incorporation or Registration, and Registration Number. EV Certificates may be issued to Private Organizations, Government Entities, International Page 8

9 Organization Entities, and Business Entities. TeliaSonera OV or EV Certificates do not, however, provide any guarantee that the Subject named in the Certificate is trustworthy, honest or reputable in its business dealings, or safe to do business with. Issued certificates only establish that TeliaSonera CA verified that the business was legally organized, used domain names were owned or managed by the Subject and in EV case also that Applicant s physical existence (business presence at a physical address), and operational existence (business activity) were verified. 1.2 Document name and identification This CPS is titled TeliaSonera Server Certificate CPS and the CPS name of this CPS is {TELIASONERA-SERVER-CPS-1}. This CPS is also a Certificate Policy for TeliaSonera server and EV certificates. The certificates issued according to this CPS contain Certificate policy object identifier corresponding to the applicable certificate type. The routines and roles resulting from this CPS apply only in connection with certificates referring to the following Certificate policy object identifiers: Certificate type Issuing CA Certificate policy object identifier Organization validation (OV) certificates TeliaSonera Server CA v1 TeliaSonera Server CA v Extended validation (EV) certificates TeliaSonera Extended Validation SSL CA v TeliaSonera Server CA v2 was introduced in to bring SHA256 algorithm to complement TeliaSonera s SSL certificate offering. Since then the default algorithm in SSL certificates has been SHA256 and older SHA1 has been used only in special circumstances. Otherwise v1 and v2 policies are identical. This CPS also refers to the TeliaSonera Production CPS with the name {TELIASONERA- PRODUCTION-CPS-2}. 1.3 PKI participants TeliaSonera OV and EV certificates are issued to devices (e.g. web servers) possessed by Customers of TeliaSonera or by TeliaSonera. All of the participating organizations shall undertake what s stated in this Certification Practice Statement Certification authorities The Certification Authority operating in compliance with this Certification Practice Statement is TeliaSonera. The name of the Certification Authority in the Issuer field of the certificate is TeliaSonera Server CA v1, TeliaSonera Server CA v2 or TeliaSonera Extended Validation SSL CA v1. TeliaSonera Server CA v1, TeliaSonera Server CA v2 and TeliaSonera Extended Validation SSL CA v1 are subordinate CAs of TeliaSonera Root CA v1. TeliaSonera Root CA has its own CP and CPS describing the management of the certificate life cycle of subordinate CA certificates signed by it. The title of that CPS is TeliaSonera Root CPS and its CPS name is {TELIASONERA-ROOT-CPS-2}. The Certification Authorities are responsible for managing the certificate life cycle of end entity certificates signed by the CAs. This will include: creating and signing of certificates binding Subjects with their public key promulgating certificate status through CRLs and/or OCSP responders Registration authorities The CA s units authorized to perform registration functions, Customers acting as Customers of certification services and authorized by CA, or other organizations selected and authorized as RAs, with which the CA makes written agreements, can act as Registration Authorities. Through those Page 9

10 agreements, RAs are obliged to follow this CPS for their part. Typically RA is responsible for the following activities on behalf of a CA: Identification and authentication of certificate subjects initiate or pass along revocation requests for certificates approve applications for renewal or re-keying certificates Subscribers The Subscriber is the legal entity that makes an agreement with the CA about issuance of a certificate to a Device in its possession. With both OV and EV certificates the Subscriber is typically also the Subject of a certificate Relying parties Any natural person or Legal Entity that relies on a Valid Certificate Other participants TeliaSonera has made agreements with Application Software Suppliers so that they may trust and display certificates issued by TeliaSonera as trusted when used via their software. 1.4 Certificate usage Appropriate certificate uses Certificates under this CPS are issued to servers or devices to be used for the following applications: - Subject authentication - Verification of digital data origin and integrity - Confidentiality of digital data TeliaSonera server certificates can be used, for example, to identify servers and secure SSL/TLS session Prohibited certificate uses Applications using certificates issued under this CPS shall take into account the key usage purpose stated in the Key Usage and Extended Key Usage extension fields of the certificate. Additionally, the key usage purposes and limitations possibly stated in the contract between the Subscriber and the CA shall be taken into account when using certificates. 1.5 Policy administration Organization administering the document TeliaSonera CA Policy Management Team is the responsible authority for reviewing and approving changes to this CPS. Written and signed comments on proposed changes shall be directed to the listed web form or to TeliaSonera contact as described in Section Decisions with respect to the proposed changes are at the sole discretion of the TeliaSonera CA Policy Management Team. Contact information regarding CPS issues: Contact person Contact person in matters related to this CPS: TeliaSonera CA Product Manager Phone: +358 (0) Internet: Page 10

11 Other contact information: Customer Service: Technical Customer Service: CA Customer Service: Revocation Service: +358 (0) (normal office hour Help Desk services) +358 (0) (any support issues) (PKI support issues) +358 (0) (revocation requests or any urgent issues) Note! Also can be used for reporting complaints or suspected private key compromise, Certificate misuse, or other types of fraud, compromise, misuse, or inappropriate conduct related to SSL Certificates Person determining CPS suitability for the policy TeliaSonera CA Policy Management Team is the administrative entity for determining this Certification Practice Statement (CPS) suitability to the applicable policies CPS approval procedures TeliaSonera CA Policy Management Team will review any modifications, additions or deletions from this CPS and determine if modifications, additions or deletions are acceptable and do not jeopardize operations or the security of the production environment. 1.6 Definitions and acronyms A list of definitions and acronyms can be found at the end of this document. Page 11

12 2 PUBLICATION AND REPOSITORY RESPONSIBILITIES 2.1 Repositories CPS Repository A full text version of this CPS is published at Revocation Information Repository OCSP is the recommended Revocation Information Repository. It can be found from Certificate Revocation Lists (CRLs) are published in the TeliaSonera LDAP directory and on the TeliaSonera website: Issuing CA TeliaSonera Server CA v1 CRL addresses (ldap://crl-1.trust.teliasonera.com/cn=teliasonera%20server%20ca %20v1,o=TeliaSonera?certificaterevocationlist;binary) TeliaSonera Server CA v2 (ldap://crl-1.trust.teliasonera.com/cn=teliasonera%20server%20ca %20v2,o=TeliaSonera?certificaterevocationlist;binary) TeliaSonera Extended Validation SSL CA v1 (ldap://crl-1.trust.teliasonera.com/cn=teliasonera%20extended %20Validation%20SSL%20CA%20v1,o=TeliaSonera?certificaterevocationl ist;binary) If OCSP is not used then http based CRL repository is recommended. It is listed at first on certificate s CDP extension Certificate Repository All issued certificates are stored in the local database of the CA system. Certificates may also be published to other repositories if it is a part of the TeliaSonera CA Service or agreed with a Customer. EV certificates may be distributed to external directories as required by Certificate Transparency specification at Publication of certification information It is TeliaSonera s duty to make the following information available: a) This CPS b) Certificate revocation lists and revocation status of revoked certificates c) Issued CA certificates and cross certificates for cross-certified CAs TeliaSonera may publish and supply certificate information in accordance with applicable legislation. Each published certificate revocation list (CRL) provides all processed revocation information at the time of publication for all revoked certificates of which the revocation list is intended to give notification. TeliaSonera supplies CA certificates for all public CA keys provided these can be used for verifying valid certificates. Subscribers will be notified that a CA may publish information submitted by them to publicly accessible Page 12

13 directories in association with certificate information. The publication of this information will be within the limits of sections 9.3 and Time or frequency of publication Updates to this CPS are published in accordance with the provisions specified in section Revocation information publication provisions are specified in section 4.9. All issued certificates are stored in the local database of the CA system promptly on issuing. Certificates may also be published to other repositories if it is a part of the TeliaSonera CA Service or agreed with a customer. 2.4 Access controls on repositories This CPS, CRLs and CA certificates are publicly available. Only authorized CA personnel have access to Subscriber certificates stored in the local database of the CA system. Page 13

14 3 IDENTIFICATION AND AUTHENTICATION 3.1 Naming Types of names An X.501 Distinguished Name (DN) is used as an unambiguous name of the Subject in the Subject field of the certificate. The name always includes the following attributes: commonname (CN, OID ) OrganizationName (O, OID ) Locality (L, OID: ) Country (ST, OID: ) Description OV SSL A single host domain name (FQDN) or IP address which is owned or controlled by the Subject and to be associated with the Subject s server. Such server MAY be owned and operated by the Subject or another entity (e.g., a hosting service). The CN value is always one of the values contained in the Certificate s subjectaltname extension. Customer in relation to which the Subject is identified. Common variations or abbreviations may also be used provided that the name owner is unambiguous. City name. A component of the address of the physical location of the Subject s Place of Business. Two character country code. A component of the address of the physical location of the Subject s Place of Business. subjectaltname:dnsname One or more host domain names (FQDN) which are owned or controlled by the Subject and to be associated with the Subject s server. Such server MAY be owned and operated by the Subject or another entity (e.g., a hosting service). Wildcard names are allowed. subjectaltname:ipaddress jurisdictioncountryname (OID: ) businesscategory (OID: ) serialnumber (OID: ) One or more IP addresses which are owned or controlled by the Subject and to be associated with the Subject s server. Such server MAY be owned and operated by the Subject or another entity (e.g., a hosting service). N/A. May be used like in EV. N/A. May be used like in EV. May be used like in EV. Optional in normal OV certificates. Description EV SSL A single host domain name (FQDN) which is owned or controlled by the Subject and to be associated with the Subject s server. Such server MAY be owned and operated by the Subject or another entity (e.g., a hosting service). Wildcard certificates are not allowed. The CN value is always one of the values contained in the Certificate s subjectaltname extension. Subject s full legal organization name as listed in the official records of the Incorporating or Registration Agency. Common abbreviations may be used in prefix or suffix parts. City name. A component of the address of the physical location of the Subject s Place of Business. Two character country code. A component of the address of the physical location of the Subject s Place of Business. One or more host domain names (FQDN) which are owned or controlled by the Subject and to be associated with the Subject s server. Such server MAY be owned and operated by the Subject or another entity (e.g., a hosting service). Wildcard names are not allowed. Not allowed Two character country code of the country in which the subject is registered One of the following strings: "Private Organization", "Government Entity", "Business Entity", or "Non-Commercial Entity" depending how the Subject qualifies in CA validation. Registration Number (e.g. Business ID or organization number) assigned to the Subject by the Incorporating or Registration Agency. Page 14

15 Additionally, the Subject field may include following attributes depending on the usage purpose of the certificate: Description Server Description EV SSL organizationalunit Name (OU,OID: ) streetaddress (OID: ) postalcode (OID: ) State or province (ST, OID: ) Organizational unit defined by the Subscriber. This attribute may also be a DBA, tradename, trademark, address, location, or other text that refers to the specific Legal Entity in the field OrganizationName. Optional. Street address. A component of the address of the physical location of the Subject s Place of Business. Optional. Postal code. A component of the address of the physical location of the Subject s Place of Business. Not recommended. A country or province name. A component of the address of the physical location of the Page 15 Organizational unit defined by the Subscriber. This attribute may also be a DBA, tradename, trademark, address, location, or other text that refers to the specific Legal Entity in the field OrganizationName. Optional. Street address. A component of the address of the physical location of the Subject s Place of Business. Optional. Postal code. A component of the address of the physical location of the Subject s Place of Business. Not recommended. A country or province name. A component of the address of the physical location of the Subject s Place of Business. Subject s Place of Business. Additional Distinguished Name (DN) or Subject Alternative Name attributes may be used as necessary providing that CA is able to verify that the additional attributes belong to the Subject Need for names to be meaningful Names will be meaningful as stated in the section Anonymity or pseudonymity of Subscribers Names will be meaningful as stated in the section Rules for interpreting various name forms No stipulation Uniqueness of names The Subject name stated in a certificate will be unique for all certificates issued within the domain of the CA, and conform to X.500 standards for name uniqueness. Subject name uniqueness means that the CA will not issue certificates with identical names to different organizations. However, the CA may issue several certificates to the same organization, and in that case the Subject names in those certificates may be the same Recognition, authentication, and role of trademarks The priority to entity names is given to registered trademark holders. TeliaSonera reserves the right not to issue such a certificate, or to revoke a certificate that has already been issued, when there is a name claim dispute involved concerning the certificate contents. 3.2 Initial identity validation Method to prove possession of private key The CA verifies the possession of the private key by verifying the electronic signature included in the PKCS #10 certificate request. The request is accepted only when signed with the private key associated with the public key to be certified Authentication of organization identity TeliaSonera CA or its authorized resellers do the authentication and verification of the certificate request data as described in this chapter. The data for verification is given to the CA either in hand-signed SSL certificate service agreement (Full SSL agreement) or in web order form of OV or EV certificate. Data may be given to CA in the PKCS#10 certificate signing request or separately on the order form so that the latter will override the former if both exist.

16 TeliaSonera CA verifies the organization name (O) of a new Customer by checking the existence of the company, its legal name, business identity code and other relevant organization information from an official business register maintained by an applicable government agency (e.g. ytj.fi in Finland). The list of applicable trusted registries is maintained in CA internal instructions.. Subject s registration number and address components (street, postalcode, locality, stateorprovince, country) are typically verified using the same register. In EV validation the verified registration number is added to the serialnumber attribute of a certificate. The address components may be added to the certificate. Mandatory attributes must have a successfully verified value. Metadata such as -,. or unknown are not allowed in these attributes. TeliaSonera verifies domain names and IP addresses from a trusted database maintained by a reliable third party registrar e.g. domain.fi (for domain.fi ), iis.se (for domain.se ), ripe.net (for IP addresses) and (for non-country domains), that as of the date the Certificate was issued, the Applicant either had the right to use, or had control of, the Fully-Qualified Domain Name(s) and IP address(es) listed in the Certificate, or was authorized by a person having such right or control (e.g. under a Principal-Agent or Licensor-Licensee relationship) to obtain a Certificate containing the Fully-Qualified Domain Name(s) and IP address(es). Connection to the third party database is SSL/TLS protected when applicable. In domain verification the domain name ownership is approved if the registered domain/ip owner is a Parent/Subsidiary Company of the Applicant or the ownership is registered to the old name/entity of the same Applicant. In such cases a reliable proof of company structure or name change must be available. If the Subject Identity Information is to include a name, DBA, trade name or trademark the CA verifies the Applicant s right to use the name from applicable government agency responsible of such names (e.g. ytj.fi in Finland). TeliaSonera may use its previously documented verification data. Old verification data will expire in three years in OV verification and in thirteen months in EV verification or earlier if the data had an internal expiration date. Old verification data including organization name, address components, Parent/Subsidiary/name change relationships, authorization documents and domain/ip ownership are stored related to organization s registration number. Other subject values like OU or E are verified each time separately. In FullSSL service such verification can be done by the Customer Registration Officer and TeliaSonera only verifies the Organization names and domain ownerships. In all cases TeliaSonera CA regularly validates that all Registration Officers have done the verification of all subject fields correctly. Alternatively the Registration Officer may use another allowed authentication or verification methods listed in the Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates (regarding OV certificates) or Guidelines For The Issuance And Management Of Extended Validation Certificates (regarding EV certificates) published at If such special verification method is used, it is always separately approved by a supervising TeliaSonera PKI board Authentication of individual identity The procedures to authenticate the identity of the Subscriber vary between the different TeliaSonera Server Certificate services: OV order via public web form TeliaSonera authenticates the administrative (or technical) contact person defined in the certificate application by calling the contact person via the Customer s PBX number or by making a call to some other verified number in the organization, which is looked up from a trusted phone directory maintained by a third party Page 16

17 EV certificate order via public web form CA requires that administrative contact person (Contract signer) makes a web Subscriber contract with CA. Contract is verified by calling to him/her like above in SSL order authentication. His/her identity and authority on behalf of the Applicant to do contracts is verified. After the initial authentication he/she will get an order confirmation message from each EV order. Each confirmation message can be used to cancel the contract or authorization. In the EV contract at least one technical contact person representing the Applicant is authorized by Contract Signer to order EV certificates. In EV terms he/she is the Certificate Requester and the Certificate Approver. Authorization is given to the address that will get the approved EV certificates. Each EV order is authenticated by CA by making a call or other applicable contact method to technical contact like above in the OV order authentication. Internal TeliaSonera OV or EV certificates or when CA has direct access to Applicant employee register When employee register is available CA verifies that both technical and administrative contact persons are using approved Applicant company addresses AND both persons are active employees in the Company according to the employee register. Normal web application authentication described above must be used instead of this if the requirements are not completely fulfilled. SSL order using TeliaSonera s self service software The Customer can make an agreement with TeliaSonera to act as a Registration Officer within the Customer Organization (Full SSL Service) and to register TeliaSonera Server certificates using TeliaSonera s RA system for Customers. The Customer Registration Officer is restricted to register certificates only within their own Organizations (O) and the domain names and other values authorized by the CA. Before enabling the service or adding new authorized Organization or domain names, the CA verifies the organization identity and the domain names as described in the section When registering Subjects, the identity of the Registration Officer is verified by means of the Registration Officers certificate issued by a TeliaSonera CA Non-verified Subscriber information The Registration Officer is obliged to always review all subject information and initiate additional checking routines if there are any unclear Subject values. Only well-known certificate extensions are verified and others are accepted only if CA is aware of the reason for including the extension. Domain name ownership of domains in addresses is not verified by TeliaSonera except when Applicant s employee register is used for authority verification. The value in OrganizationalUnit field is not verified unless it includes a name, DBA, tradename, trademark, address, location, or other text that refers to a specific Legal Entity. If such value is used TeliaSonera verifies that the Applicant has a right to use it according to a reliable data source Validation of authority OV order via public web form TeliaSonera verifies that the administrative contact person defined in the certificate application is employed by the Customer by calling the contact person via the Customer s PBX number or by making a call to some other verified number in the organization, which is looked up from a directory maintained by a trusted party. Page 17

18 EV order via public web form SSL order using TeliaSonera s self-service software TeliaSonera verifies that the administrative contact person (Contract Signer) has the authority to do contracts on behalf of the Customer. He/she must be an employee of the Applicant and have an applicable manager or director title or similar role according to certificate application. This title or role is verified via the Company switchboard or via other data source available excluding the person him/herself. The Administrative Contact Person, who grants the necessary initial authorizations in the Customer, has been identified in the service agreement or order. TeliaSonera verifies that the Organization has authorized the certificate service by contacting the contact person specified in the agreement by phone, mail or other similar methods. A Registration Officer in a Customer has the right to define new Registration Officers. Authorization is based on multi-factor authentication to TeliaSonera s self-service software (typically certificate and PIN code) Criteria for interoperation Not applicable. 3.3 Identification and authentication for re-key requests Identification and authentication for routine re-key No special routine exists for renewal of TeliaSonera Server certificates. In Subject registration the same process will be followed as in the initial registration. The previous verification data may be utilized by CA if it is not expired Identification and authentication for re-key after revocation After revocation of a Subject s certificate, if the Subscriber wants to have a new certificate, then the same process will be followed as in the initial registration. The previous verification data may be utilized by CA if it is not expired. 3.4 Identification and authentication for revocation request Revocation by Customer In cases where a Customer can issue SSL certificates using TeliaSonera s self-service software, the Subscriber shall submit a request for certificate revocation to the Registration Officer of its own organization, who has additionally the rights of a Revocation Officer. The Revocation Officer in the Customer is responsible for the verification of the authenticity of the request to revoke the certificate. The identity of the Revocation Officer in the Customer is verified based on a certificate. Revocation by the Revocation Service of the CA The Subscriber or Registration Officer in a Customer shall submit a request for certificate revocation to the Revocation Service by telephone or by . The revocation service checks that the origin of the request is the Customer who owns the certificate using message details. The Revocation Service may make a call back to the Customer and ask certain detailed data. This data is compared with the information recorded about the Subject or Subscriber at registration, and if necessary, with information in the agreements made with the Subscriber or with the Customer. If the data match the certificate will be revoked. In certain situations where there is an identified risk of abuse of the private key or when it is obvious that the authorized use of the key is prevented, it may be necessary to revoke the certificate on request of someone else but the above mentioned entities. In that case the verification of the authenticity of the revocation request can require other authentication methods. In cases where reliable verification cannot be immediately performed the CA may revoke the certificate to reduce risks. Page 18

19 4 CERTIFICATE LIFE-CYCLE OPERATIONAL REQUIREMENTS 4.1 Certificate Application Who can submit a certificate application OV or EV order via public web form Manually processed Certificate application can be submitted by a representative of the Organization, which possesses the Device to which the certificate is applied. If the application is submitted by a different organization from the organization that owns the domain name or the IP address (e.g. by an IT service provider), the application must be authorized by the organization owning the domain name or IP address. SSL order using TeliaSonera s self-service software Automatically processed Certificate application can be submitted by an authorized Registration Officer in a Customer that has made a SSL Service agreement with TeliaSonera. Authorized TeliaSonera personnel can also submit these applications for devices of TeliaSonera. TeliaSonera will issue server certificates only to organizations that are registered in the European Economic Area. The European Economic Area (EEA) comprises the countries of the European Union (EU), plus Iceland, Liechtenstein and Norway. TeliaSonera may refuse to issue certificates to organizations registered in countries where TeliaSonera cannot reliably validate information on the certificate application Enrollment process and responsibilities OV or EV order via public web form SSL order using TeliaSonera s self-service software A certificate to a Device (an EV or OV server certificate) is applied by filling in a form that is publicly available at TeliaSonera s web site. A Certificate Signing Request (CSR) that is a standard format certificate request generated by the Device shall be attached to the form. The completed application forms are directed to TeliaSonera s RA office where the sufficiency of the application is checked. Before the application can be submitted, the Subscriber has to accept the Subscriber responsibilities and terms and conditions of the service. A Registration Officer in a Customer applies for certificates to Devices (OV server certificates) directly from the CA system by using the selfservice application provided by TeliaSonera. The application will print all relevant certificate request values on screen for final review. If accepted by the Registration Officer and the CA configuration the request is processed automatically. It may contain only pre-defined Domain Name and Organization Name values allowed to this Customer. Only TeliaSonera Registration Officers may add new allowed Domain Name or Organization Name values for Customers. New values are always verified according to 3.2. The Customer is bound through a SSL Service Agreement with TeliaSonera. Customer s Registration Officers also accept Customer Responsibilities when they logon to TeliaSonera s self-service application for the first time. 4.2 Certificate application processing Performing identification and authentication functions TeliaSonera performs identification and authentication of Subject and Subscriber information in accordance with the section 3.2. Page 19

20 4.2.2 Approval or rejection of certificate applications TeliaSonera will approve a certificate application if it meets the requirements documented in this CPS and there are no other reasons to reject the application. All other certificate applications will be rejected. The Subscriber will be informed on why the certificate application was rejected and on how to proceed to be approved Time to process certificate applications OV or EV order via public web form OV order using TeliaSonera s self service software TeliaSonera process the applications within reasonable time frame. The certificate request is processed automatically by TeliaSonera s RA and CA systems immediately after the request is submitted Certificate Authority Authorization (CAA) CA is not currently checking CAA records. 4.3 Certificate issuance CA actions during certificate issuance If the certificate application is approved, the CA issues the certificate. The CA system accepts only such certificate requests the origin of which can be authenticated. The certificate is created by the CA according to the information contained in the certificate request and configured for the Customer. However, the CA may overwrite or delete some certificate information using pre-defined certificate profile specific standard values Notification to Subscriber by the CA of issuance of certificate OV or EV order via public web form Subscriber is informed of the acceptance or rejection of the certificate request. TeliaSonera s RA office delivers a web link to the contact person for fetching of the certificate. OV order using TeliaSonera s self-service software The certificate is available for the Customer s Registration Officer in the RA tool after the issuance. 4.4 Certificate acceptance Conduct constituting certificate acceptance The Subscriber is considered to have accepted the certificate when the private key associated with it has been used, or when the certificate has been installed into a Device Publication of the certificate by the CA TeliaSonera will not publish Subscriber certificates to a publicly available repository if not agreed upon with the Customer. EV certificates may be distributed to external directories as required by Certificate Transparency specification at Notification of certificate issuance by the CA to other entities EV certificates may be distributed to external directories as required by Certificate Transparency specification at Page 20

21 4.5 Key pair and certificate usage Subscriber private key and certificate usage The Subscriber shall only use certificates and their associated key pairs for the purposes identified in this CPS and in applicable agreements with TeliaSonera. Issued certificates contain information which defines suitable areas of application for the certificate and its associated keys. Area of application labelling takes place in accordance with X.509 and chapter 7 of this CPS. For more information regarding appropriate Subscriber key usage see sections and The Subscriber shall protect the Subject private key from unauthorized use and discontinue the use of the Subject private key immediately and permanently in case the private key is compromised Relying party public key and certificate usage Prior to accepting a TeliaSonera Server certificate, a relying party is responsible to: a) Verify that the certificate is appropriate for the intended use; b) Check the validity of the certificate, i.e. verify the validity dates and the validity of the certificate and issuance signatures; and c) Verify from a valid Certificate Revocation List (CRL) or other certificate status service provided by the CA that the certificate has not been revoked or suspended. If certificate status cannot be verified due to system failure or similar, the certificates shall not be accepted. 4.6 Certificate renewal Certificate renewal is the re-issuance of a certificate with a new validity date using the same public key corresponding to the same private key Circumstance for certificate renewal When the validity time of a certificate is about to end, the certificate can be renewed Who may request renewal Renewal may be requested by the same persons as the initial certificate application as described in section Processing certificate renewal requests OV or EV order via public web form Certificate renewal requests are processed like the initial certificate requests as described in section 4.2. CA may use the stored data of previous validations if available and such data is not expired. OV order using TeliaSonera s self-service software Registration Officer has an option to renew certificates using the tool provided by the CA, in which case the tool uses the old CSR file to renew the certificate. Registration Officer is responsible to ensure that the certificate information is still valid and that there are no other obstacles to the renewal. Certificate renewal and re-key requests may also be processed like the initial certificate requests as described in section Notification of new certificate issuance to Subscriber The Subscriber is notified as described in section Conduct constituting acceptance of a renewal certificate Conduct constituting acceptance of a renewal certificate is described in section Publication of the renewal certificate by the CA Page 21