Certification Practice Statement



Similar documents
TELSTRA RSS CA Subscriber Agreement (SA)

apple WWDR Certification Practice Statement Version 1.8 June 11, 2012 Apple Inc.

Ericsson Group Certificate Value Statement

Apple Corporate Certificates Certificate Policy and Certification Practice Statement. Apple Inc.

Neutralus Certification Practices Statement

Danske Bank Group Certificate Policy

SECOM Trust.net Root1 CA

Ford Motor Company CA Certification Practice Statement

Certification Practice Statement

Apple Inc. Certification Authority Certification Practice Statement Worldwide Developer Relations Version 1.14 Effective Date: September 9, 2015

Fraunhofer Corporate PKI. Certification Practice Statement

CERTIFICATION POLICY QUEBEC CERTIFICATION CENTRE Notarius Inc.

Certificate Policies and Certification Practice Statements

Registration Practices Statement. Grid Registration Authority Approved December, 2011 Version 1.00

TERMS OF USE FOR PUBLIC LAW CORPORATION PERSONAL CERTIFICATES FOR QUALIFIED DIGITAL SIGNATURE

TR-GRID CERTIFICATION AUTHORITY

Government CA Government AA. Certification Practice Statement

Land Registry. Version /09/2009. Certificate Policy

Certipost Trust Services. Certificate Policy. for Lightweight Certificates for EUROCONTROL. Version 1.2. Effective date 03 May 2012

TR-GRID CERTIFICATION AUTHORITY

TERMS OF USE TITLE CERTIFICATES FOR ELECTRONIC SIGNATURE

Certification Practice Statement

SwissSign Certificate Policy and Certification Practice Statement for Gold Certificates

ESnet SSL CA service Certificate Policy And Certification Practice Statement Version 1.0

CERTIMETIERSARTISANAT and ELECTRONIC SIGNATURE SERVICE SUBSCRIPTION CONTRACT SPECIFIC TERMS AND CONDITIONS

Certificate Policy. SWIFT Qualified Certificates SWIFT

THE WALT DISNEY COMPANY PUBLIC KEY INFRASTRUCTURE CERTIFICATE POLICY. July 2011 Version 2.0. Copyright , The Walt Disney Company

StartCom Certification Authority

SYMANTEC NON-FEDERAL SHARED SERVICE PROVIDER PKI SERVICE DESCRIPTION

The name of the Contract Signer (as hereinafter defined) duly authorized by the Applicant to bind the Applicant to this Agreement is.

DigiCert Certification Practice Statement

CMS Illinois Department of Central Management Services

USER AGREEMENT FOR: ELECTRONIC DEALINGS THROUGH THE CUSTOMS CONNECT FACILITY

National Identity Exchange Federation (NIEF) Trustmark Signing Certificate Policy. Version 1.1. February 2, 2016

CERTIFICATION PRACTICE STATEMENT UPDATE

Entrust Managed Services PKI. Getting started with digital certificates and Entrust Managed Services PKI. Document issue: 1.0

PKI NBP Certification Policy for ESCB Signature Certificates. OID: version 1.5

HKUST CA. Certification Practice Statement

GEOSURE PROTECTION PLAN

CA Certificate Policy. SCHEDULE 1 to the SERVICE PROVIDER AGREEMENT

- X.509 PKI SECURITY GATEWAY. Certificate Policy (CP) & Certification Practice Statement (CPS) Edition 1.1

"Certification Authority" means an entity which issues Certificates and performs all of the functions associated with issuing such Certificates.

Meeting the FDA s Requirements for Electronic Records and Electronic Signatures (21 CFR Part 11)

INDEPENDENT AUDIT REPORT BASED ON THE REQUIREMENTS OF ETSI TS Aristotle University of Thessaloniki PKI ( WHOM IT MAY CONCERN

Certification Practice Statement (ANZ PKI)

TeliaSonera Server Certificate Policy and Certification Practice Statement

Certum QCA PKI Disclosure Statement

Brocade Engineering. PKI Tutorial. Jim Kleinsteiber. February 6, Page 1

Gandi CA Certification Practice Statement

User Guide Supplement. S/MIME Support Package for BlackBerry Smartphones BlackBerry Pearl 8100 Series

Citizen CA Certification Practice statement

EBIZID CPS Certification Practice Statement

e-authentication guidelines for esign- Online Electronic Signature Service

Comparing Cost of Ownership: Symantec Managed PKI Service vs. On- Premise Software

SWITCHaai Metadata CA. Certificate Policy and Certification Practice Statement

TACC ROOT CA CERTIFICATE POLICY

Comodo Certification Practice Statement

ARTL PKI. Certificate Policy PKI Disclosure Statement

Digital Certificates (Public Key Infrastructure) Reshma Afshar Indiana State University

Certificate Policy and Certification Practice Statement CNRS/CNRS-Projets/Datagrid-fr

EuropeanSSL Secure Certification Practice Statement

THE RSA ROOT SIGNING SERVICE Certification Practice Statement For RSA Certificate Authorities (CAs) Published By: RSA Security Inc.

Globe Hosting Certification Authority Globe Hosting, Inc. 501 Silverside Road, Suite 105, Wilmington, DE 19809, County of New Castle, United States

ENTRUST CERTIFICATE SERVICES

Bangladesh Bank Certification Authority (BBCA) Certification Practice Statement (CPS)

TERMS OF USE FOR NOTARIAL PERSONAL REPRESENTATION CERTIFICATES FOR AUTHENTICATION

X.509 Certificate Generator User Manual

REGISTRATION AUTHORITY (RA) POLICY. Registration Authority (RA) Fulfillment Characteristics SECURITY DATA SEGURIDAD EN DATOS Y FIRMA DIGITAL, S.A.

TREND MICRO SSL CERTIFICATION PRACTICE STATEMENT. Version 2.0

Qualified Electronic Signatures Act (SFS 2000:832)

LET S ENCRYPT SUBSCRIBER AGREEMENT

SSL.com Certification Practice Statement

PKI NBP Certification Policy for ESCB Encryption Certificates. OID: version 1.2

How To Understand And Understand The Security Of A Key Infrastructure

Certificate Policy and Certification Practice Statement

Visa Public Key Infrastructure Certificate Policy (CP)

Malaysian Identity Federation and Access Management Certification Authority Certificate Policy and Certification Practice Statement

Class 3 Registration Authority Charter

Equens Certificate Policy

PostSignum CA Certification Policy applicable to qualified personal certificates

Starfield Technologies, LLC. Certificate Policy and Certification Practice Statement (CP/CPS)

TeliaSonera Public Root CA. Certification Practice Statement. Revision Date: Version: Rev A. Published by: TeliaSonera Sverige AB

Chapter 7 Managing Users, Authentication, and Certificates

Trusted Certificate Service

NIST Test Personal Identity Verification (PIV) Cards

User Manual Internet Access. for the public key. certification service

SAUDI NATIONAL ROOT-CA CERTIFICATE POLICY

Public Key Infrastructure (PKI)

Vodafone Group CA Web Server Certificate Policy

OFFICE OF THE CONTROLLER OF CERTIFICATION AUTHORITIES TECHNICAL REQUIREMENTS FOR AUDIT OF CERTIFICATION AUTHORITIES

Certificate Policy for. SSL Client & S/MIME Certificates

Concept of Electronic Approvals

California Independent System Operator Certification Practice Statement for Basic Assurance Certification Authority. Version 3.

X.509 Certificate Policy for the Australian Department of Defence Root Certificate Authority and Subordinate Certificate Authorities

PEXA Public Key Infrastructure (PKI) Certification Authority Certificate Policy

Plantview can work in the following modes:

phicert Direct Certificate Policy and Certification Practices Statement

Website & Hosting Terms & Conditions

CERTIFICATE POLICIES (CP) Legal Person Certificate ICE SECURITY DATA SEGURIDAD EN DATOS Y FIRMA DIGITAL, S.A. CP

Transcription:

Certification Practice Statement Revision R1 2013-01-09 1

Copyright Printed: January 9, 2013 This work is the intellectual property of Salzburger Banken Software. Reproduction and distribution require the previous written consent of Salzburger Banken Software. Responsible for the content: SBS Software Ges.m.b.H. Weiserhofstraße 18 A-5020 Salzburg Table of Revision Version Author Date Changes R0 Andreas Hoheneder, 2012-09-01 Initial Version Christoph Meinhart R1 Andreas Hoheneder 2013-01-09 ISSUER is now called SBS-ISSUER Added OID for CPS Copyright SBS Software Ges.m.b.H. 2 January 9, 2013

Contents 1. Introduction 5 1.1. Overview of the Public Key Infrastructure (PKI) Architecture. 5 1.2. Document Name and Identification................ 6 1.3. Usage of Certificates........................ 6 1.3.1. Certificates for Access to Virtual Private Network (VPN) 6 1.3.2. Use in Software Development............... 6 1.3.3. Protection of Electronic Mail............... 7 1.3.4. Protection of Internal Infrastructure........... 7 1.4. Administration of the CPS.................... 7 1.5. Contacts............................... 7 2. Identification and Authentication 8 2.1. Identification of Certificates.................... 8 2.1.1. Certificate Names..................... 8 2.1.2. Algorithm Used to Construct X.509 Serial Numbers.. 8 2.1.3. Technical Details of Issued Certificates.......... 9 2.2. Verifying the Identity of Individuals............... 9 3. Publication and Distribution of Certificates 10 4. Life Cycle of Certificates 10 4.1. Application............................. 10 4.2. Issuance............................... 10 4.3. Renewal............................... 11 4.4. Revocation............................. 11 4.4.1. Revocation Process..................... 12 4.4.2. Modification of Certificates................ 13 4.4.3. Certificate Suspension................... 13 4.4.4. Private Key Escrow.................... 13 4.4.5. Publication of Revocation Lists.............. 14 Copyright SBS Software Ges.m.b.H. 3 January 9, 2013

5. Physical, Organizational and Human Resources Controls 14 5.1. Physical Security Controls..................... 14 5.1.1. Access Control....................... 14 5.1.2. Appropriately equipped Server Rooms.......... 15 5.1.3. Business Resilience..................... 15 5.2. Employee Requirements...................... 15 5.3. Cease of PKI Operation...................... 15 6. Technical Security Measures 16 6.1. Secure Issuance of Certificates................... 16 6.2. Private Key Protection....................... 16 6.3. Protection of Activation Information............... 16 7. Other business-related or legal regulation 17 7.1. Fees................................. 17 7.2. Obligations............................. 17 7.2.1. Obligations of the PKI................... 17 7.2.2. Obligations of Certificate Owners............. 18 7.3. Warranty.............................. 18 7.4. Liability............................... 19 7.5. Applicable Law........................... 19 A. Definitions and Acronyms 20 Copyright SBS Software Ges.m.b.H. 4 January 9, 2013

1. Introduction This Certification Practice Statement (CPS) defines the PKI security model of Salzburger Banken Software (SBS). It describes the requirements for issuance, usage, destruction and revoking of certificates within the PKI in accordance with SBS security policy to ensure a secure operation of the PKI. The structure of this document follows RFC 3647 Internet X.509 Public Key Infrastructure - Certificate Policy and Certification Practices Framework. 1.1. Overview of the PKI Architecture ROOT-CA-1 ROOT-CA-2 SBS-ISSUER-1 TEST-ISSUER-1 SBS-ISSUER-2 production certificates test certificates <not used> Figure 1: PKI Architecture The PKI uses two different root certificates, each of which signs issuer certificates. The certificates of ROOT-CA-2 use SHA1 for hashing, which the National Institute of Standards and Technology (NIST) advises against due Copyright SBS Software Ges.m.b.H. 5 January 9, 2013

to its cryptographic limitations 1. Therefore, ROOT-CA-2 is only used when technical limitations prevent the usage of SHA256 hashed certificates. 1.2. Document Name and Identification Description: Certification Practice Statement (CPS) Version: R1 EN Object-ID: 2.5.29.32.0 2 This document is rated public in accordance with our Quality Management System (QMS). 1.3. Usage of Certificates 1.3.1. Certificates for Access to VPN The VPN certificates are used to authenticate authorized access by employees and customers of SBS from external devices to the company network. These certificates also ensure the integrity and encryption of this communication. 1.3.2. Use in Software Development Certificates issued by the PKI are also used in software development. Thus, digital signatures protect the integrity of the software, and special test certificates are used for software tests. 1 http://csrc.nist.gov/groups/st/hash/statement.html 2 4.2.1.5 from http://www.ietf.org/rfc/rfc3280.txt Copyright SBS Software Ges.m.b.H. 6 January 9, 2013

1.3.3. Protection of Electronic Mail The e-mail correspondance between SBS and its customers is protected by the use of certificates encrypting the communication between mail servers. The e- mails themselves can be digitally signed and encrypted to prevent unauthorized reading and altering. 1.3.4. Protection of Internal Infrastructure Additionally to the aformentioned ones, the PKI issues certificates for internal use. These are deployed on network components and systems of SBS for ensuring confidentiality and integrity of internal communication. 1.4. Administration of the CPS This document is managed and versioned within the certified QMS of SBS. Additionally, the current version is available to the public on the SBS website. The security officer is in charge of maintaining the document 1.5. Contacts Information about the PKI of SBS can be obtained here: on the SBS website via http://pki.sbs.co.at Copyright SBS Software Ges.m.b.H. 7 January 9, 2013

via email to info@sbs.co.at via written request to: SBS Software Ges.m.b.H. Weiserhofstraße 18 5020 Salzburg Austria 2. Identification and Authentication 2.1. Identification of Certificates 2.1.1. Certificate Names The issued certificates use Distinguished Names according to X.501. The possible symbols are restricted to the letters of the English alphabet, "space" and the special characters "_", "-", "." and "@". Certificates issued for natural persons must include contact information (e.g. an e-mail address). Every certificate is assigned to one specific person. This PKI will not issue group certificates to natural persons. 2.1.2. Algorithm Used to Construct X.509 Serial Numbers X.509 serial numbers are issued according to the following schema: xx yy yy yy yy zz zz zz zz Copyright SBS Software Ges.m.b.H. 8 January 9, 2013

xx... 1 byte consecutive number of the root certificates: 01... SBS ROOT-CA-1 using sha256 and 4096 bit 02... SBS ROOT-CA-2 using sha1 and 2048 bit yy... 4 bytes consecutive number of the issuer certificates: 01 00 00 00 01... SBS-ISSUER-1 01 00 00 00 02... TEST-ISSUER-1 02 00 00 00 01... SBS-ISSUER-2 zz... 4 bytes consecutive number of the actual user certificates 2.1.3. Technical Details of Issued Certificates The PKI issues certificates according to X.509 version 3 (RFC 3280). The signature algorithm used is either SHA256 or SHA1 in combination with RSA. All issued certificates carry the extension "X509v3 Subject Key Identifier" (fingerprint of the certificate) and all non-ca-certificates carry the extension "X509v3 Authority Key Identifier". Additionally, the use of all certificates is restricted via the extension "X509v3 Key Usage". 2.2. Verifying the Identity of Individuals Certificates are only issued to employees or customers of SBS who are registered in the company-internal Lotus Notes database. Newly recruited employees are identified by an official photo identification. Copyright SBS Software Ges.m.b.H. 9 January 9, 2013

3. Publication and Distribution of Certificates Provided the receiving party is connected to SBS s Lotus Notes system the certificate will be delivered by encrypted email. If the recipient is not connected to this system the authenticity of the certificate has to be guaranteed either by personal delivery or download from a website combined with the verification of the fingerprint via telephone. 4. Life Cycle of Certificates 4.1. Application A Certificate can be requested from the SBS security officer. The reason for needing a certificate has to be stated. Certificates are only issued to employees or customers of SBS and not to people unrelated to the company. A Certificate Signing Request (CSR) can be submitted when filing an application. 4.2. Issuance After verifying the identity and eligibility of the application a certificate will be issued. If no CSR was submitted, a key pair is generated and used to build the certificate. If a CSR was handed in the following will be verified: Copyright SBS Software Ges.m.b.H. 10 January 9, 2013

correctness of the information stated in the CSR correctness of the characters used for certificate name conformity of the algorithms and key lengths with security policy Once all verifications are completed, the applicant will receive the certificate (and the corresponding private key if necessary) via encrypted e-mail. Otherwise, they are informed about their rejection and the reasons for it via e-mail. 4.3. Renewal The lifetime of the certificates issued by the PKI is defined as: ROOT-CA-1: 15 years (until September 2, 2026) ROOT-CA-2: 10 years (until September 3, 2021) Issuer certificates: 5 years End-user certificates (e-mail, VPN, web server): 2 years After half of the lifetime a new certificate is issued. This implies that usually two certificates of a kind are valid at any time. 4.4. Revocation Either the PKI or the certificate owner can initiate the revocation of a certificate. Copyright SBS Software Ges.m.b.H. 11 January 9, 2013

Reasons for a certificate revocation include: Information contained in the certificate is no longer true. The private key of the certificate is compromised or there is suspicion of compromise. The certificate is no longer needed. One or more algorithms used to create the certificate are cryptographically broken or are no longer regarded as safe. It is the security officer s choice to either revoke the certificate immediately or within a time span adequate to the threat level. The issuance CA has been compromised. The issuance CA ceases operation. The reason for a certificate revokation is specified in the Certification Revocation List (CRL) according to RFC 2459. The values mentioned in the standard are interpreted corresponding to the Microsoft Security Guidance 3. 4.4.1. Revocation Process The request for a certificate revocation is to be submitted to the security officer. The applicant either has to show a valid signature of the certificate in question, bring in the request via the Notes database used in the company or identify himself presenting official photo identification. The revocation is executed as soon as possible but not later than three days 3 http://technet.microsoft.com/en-us/library/cc700843.aspx Copyright SBS Software Ges.m.b.H. 12 January 9, 2013

after the revocation request through entries in the CRLs. The owner of the certificate is notified via e-mail. 4.4.2. Modification of Certificates The modification of existing certificates (the modification and signing of a certificate based on the same private key) will be carried out if there are reasons that suggest to do so. The reasons (for instance the information in the certificate is no longer true) will be reviewed and checked prior to certificate issuance. 4.4.3. Certificate Suspension The PKI does not suspend certificates (interrupt the validity for a limited period of time). If a certificate is temporarily not used it will be revoked and a request for a new certificate has to be placed as soon as it is needed again. 4.4.4. Private Key Escrow The PKI does not save user s private keys on principle. If a private key is lost or rendered unusuable (e.g. through a forgotten password), the security officer has to be notified. The certificate belonging to the private key will be revoked and a new one has to be applied for. Copyright SBS Software Ges.m.b.H. 13 January 9, 2013

4.4.5. Publication of Revocation Lists Certificate Revocation Lists (CRLs) are published on the SBS PKI website. Regardless of certificate revocations, these lists are valid for three months. If a certificate has been revoked, a new revocation list is published within eight hours. The current CRLs are available via: http://pki.sbs.co.at/sbs-issuer-1.crl http://pki.sbs.co.at/sbs-root-ca1.crl 5. Physical, Organizational and Human Resources Controls 5.1. Physical Security Controls 5.1.1. Access Control SBS buildings are secured by alarm systems, while PKI components are situated in separated, specially secured zones, which only authorized personel has access to. Copyright SBS Software Ges.m.b.H. 14 January 9, 2013

5.1.2. Appropriately equipped Server Rooms The PKI systems are protected from voltage fluctuations and power outages by means of Uninterrupted Power Supply (UPS) technology in order to ensure continuous operations. Furthermore, the systems are temperature controlled and monitored by fire alarm systems. 5.1.3. Business Resilience PKI information is regularly backed up and stored off-site. Systems and equipment are redundant and emergency plans ensure business continuation after disasters. 5.2. Employee Requirements All PKI staff have the necessary expertise and are trained in security relevant aspects of PKI operations. All employees fulfill the requirements regarding reliability and trustworthiness. New employees criminal records are checked to ensure they are suited to work in trusted positions. Furthermore, the Austrian data privacy law and the contract of employment oblige employees to keep secret all information they have access to in connection with their duties. 5.3. Cease of PKI Operation Owners of valid certificates are notified if the PKI ceases operation for businessrelated or other reasons. All existing certificates are revoked in this case. Copyright SBS Software Ges.m.b.H. 15 January 9, 2013

6. Technical Security Measures 6.1. Secure Issuance of Certificates Certificates are only issued within specially protected systems, which are completely isolated and unconnected to the business network and the internet. The transport of data to and from these systems is only carried out by authorized personnel using dedicated storage media. 6.2. Private Key Protection The private key of the root certificate is saved on redundant encrypted storage media. The issuer certificates private keys are stored on smart cards and protected by PINs. All storage media containing private keys is stored in protected areas with measures against physical access and monitored by alarm systems. When private keys are no longer needed, they are destroyed either by securely deleting the data or mechanically destroying the smart card. 6.3. Protection of Activation Information The activation information necessary to access private keys is protected by the following measures: All PKI staff are obliged to keep PINs and passwords entrusted to them secret and to not write them down. Copyright SBS Software Ges.m.b.H. 16 January 9, 2013

If an employee leaves the PKI, all passwords and PINs they knew are changed. The PINs used to access the issuer certificates private keys are only saved encrypted. The passwords to use the private keys of the root certificates are not saved electronically and only stored in specially secured locations. 7. Other business-related or legal regulation 7.1. Fees Currently, the PKI does not charge users anything for their services. 7.2. Obligations 7.2.1. Obligations of the PKI The PKI pledges to work according to the principle of data saving and only to collect and use information necessary to operate the PKI, issue a new certificate revocation list after each certificate revocation and at least a week before the current list is invalid. Copyright SBS Software Ges.m.b.H. 17 January 9, 2013

7.2.2. Obligations of Certificate Owners Every owner of a personal certificate is obligated to give correct and complete information in a certificate request and to notify the PKI if information in the certificate is incorrect or no longer true, keep PINs and private keys safe and not pass them on to other persons destroy certificates which are no longer used comply with the certificate usage restrictions immediately initiate the revocation of a certificate in case the according private key is compromised. A private key is regarded compromised if a third party has knowledge of the PIN or the private key password or if this cannot be completely ruled out. 7.3. Warranty SBS guarantees to a third party relying on correctness of an issued certificate, that the PKI complies with the X.509 standards as mentioned in this document performs all processes described in this document revokes a certificate if necessary Copyright SBS Software Ges.m.b.H. 18 January 9, 2013

7.4. Liability The company SBS is liable to the holders of the certificates and injured party for damages contractual in accordance with the regulations of the Austrian Data Protection Act, but assumes no liability under the Digital Signature Act and Signature Ordinance. The certificate holder shall indemnify and holds harmless the company on all matters relating to these certificates. The company is not liable for damage that occurs due to outages or unavailability of PKI or CA services delay between a certificate revocation and the next planned issuance of a certification revocation list unauthorized use of certificates or use for purposes not specified in this document disclosure of private data from certificates or certificate revocation lists 7.5. Applicable Law The general terms and conditions of the Salzburger Banken Software apply in their valid version. Court of jurisdiction is the responsible court in Salzburg. Copyright SBS Software Ges.m.b.H. 19 January 9, 2013

A. Definitions and Acronyms VPN Virtual Private Network QMS Quality Management System SBS PKI CPS CRL Salzburger Banken Software Public Key Infrastructure Certification Practice Statement Certification Revocation List NIST National Institute of Standards and Technology UPS CSR Uninterrupted Power Supply Certificate Signing Request Copyright SBS Software Ges.m.b.H. 20 January 9, 2013