TAIWAN-CA INC. Public Key Infrastructure Certificate Policy (Version 2.0)

Transcription

1 TAIWAN-CA INC. Public Key Infrastructure Certificate Policy (Version 2.0) Effective Date: 23 November

2 Revision Record Rev Effective Date Issuer Note Apr 2001 TaiCA PMA CP first issue Jan 2002 TaiCA PMA Revised by integrating TaiCA CA PKI system documentation (CPS, CP etc) to combine with the TRAVAN EDI PAA CP Apr 2002 TaiCA PMA Revised according to the items to be specified in the Certificate Practice Statement (CPS) and Certification Authority Management Regulations (CAMR) established by the Department of Commerce, MOEA Aug 2008 TWCA PMA Approval of PMA change Mar 2009 TWCA PMA Supplementation made to the OID to indicates the different assurance level. Changed the public key validity Aug 2009 TWCA PMA Revised section according to the resolution made at the PMA meeting on 29 July Aug 2012 TWCA PMA Revised section 1.2 according to the resolution made at the PMA meeting on 22 Aug 2012 to modify OID of EC Security Certificate Nov 2012 TWCA PMA Modify OID of every CA. 2

3 Contents 1. Introduction Overview Document Name and Identification PKI Participants Certification Authority (CA) Registration Authority (RA) Subscriber Relying Parties Other Participant 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 Publication and Repository Responsibilities Repositories Publication of Certificate Information Frequency of Publication Access Control of Repository Identification and Authentication Naming Types of names Need for Names to be Meaningful Anonymity and Pseudonymity of Subscribers Rules for Interpreting Various Name Forms Uniqueness of Names Recognition, Authentication, and Role of Trademarks Identification, Authentication and Role of Trademarks Initial Identity Verification 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 Request of Certificate Revocation Certificate Life-Cycle Operational Requirements Certificate Application Submition of Certificate Application Enrollment Process and Responsibilities Certificate Application Processing Performing Identification and Authentication Functions Approval or Rejection of Certificate Application

4 4.2.3 Time to process Certificate Applications Certificates Issuance CA Actions During Certificate Issuance Notifications to Subscriber of Certificate Issuance 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 Certificates Usage Subscriber Private Key and Certificate Usage Relying Party Public Keys and Certificates Usage Certificate Renewal Circumstances for Certificate Renewal Who May Request Renewal Processing Certificate Renewal Request Notification of New Certificate to Subscribers Conduct Constituting Acceptance of a Renewal Certificate Publication of Renewal Certificate by the CA Notification of Certificate issuance by the CA to Other Entities Certificate Re-Keys Circumstances for Certificate Re-Keys Who May Request Certification of a New Public Key Processing Certificate Re-Keying Requests Notification of New Certificate Issuance to Subscribers Conduct Constituting Acceptance of a Re-Keyed Certificate Publication of the Re-Keyed Certificate by the CA Notification of Certificate Issuance by the CA Other Entities Certificate Modification Circumstances for Certificate Modification Who May Request Certificate Modification Processing Certificate Modification Requests Notification of New Certificate Issuance to Subscriber Conduct Constituting Acceptance of Modified Certificate Publication of the Modified Certificate by the CA Notification of Certificate Issuance by the CA to Other Entities Certificate Revocation and Suspension Circumstances for Certificate Revocations Who Can Request Revocations Procedure for Revocation Request Revocation Request Grace Period Time Within Which CA Must Process the Revocation Request Revocation Checking Requirements 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 Related To Key Compromise Circumstances for Suspension Who Can Request Suspension Procedures for Suspension

5 Limits on Suspension Period Certificate Status Service Operational Characteristics Service Availability Operational 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 Physical Control Site Location and Construction Physical Access Power and Air Conditioning Water Exposures Fire Prevention and Protection Media Storage Waste Disposal Off-Site Backup Procedural Controls Trusted Roles Number of Persons Required per Task Identification and Authentication for Each Role Roles Requiring Separation of Duties Personnel Control Qualifications, Experience, and Clearance Requirements Background Check Procedures Training Requirements Retraining Frequency and Requirements Job Rotation Frequency and Sequence Sanctions for Unauthorized Actions Independent Contractor Requirements Documentation Supplied to Personnel Audit Logging Procedures Types of Events Recorded Frequency of Processing Log Retention Period of Audit Log Protection of Audit Log Audit Log Backup Procedures Audit Collection System (Internal vs. External) Notification to Event-Causing Subject Vulnerability Assessments Record Archival Types of Records Archived Retention Period for Archive Protection of Archive Archive Backup Procedures Requirements for Time-Stamping of Records Archive Collection System (Internal or External) Procedures to Obtain and Verify Archive Information Key Changeover

6 5.7 Compromise and Disaster Recovery Incident and Compromise Handling Procedures Computing Resources, Software, and/or Data Are Corrupted Entity Private Key Compromise Procedures Business Continuity Capabilities After a Disaster CA or RA Termination Technical Security Control Key Pair Generation and Installation Key Pair Generation Private Key Delivery to Subscriber Public Key Delivery to Certificate Issuer CA Public Keys 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 Private Key Escrow Private Key Backup Private Keys Archive 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 Computer Security Control Specific Computer Security Technical Requirements Computer Security Rating Life Cycle Technical Controls System Development Controls Security Management Controls Life Cycle Security Controls Network Security Controls Time-Stamping Certificate, CRL, and OCSP Profiles Certificate Profiles Version Number Certificate Extensions s Algorithm Object Identifier Name Forms Name Constraints Certificate Policy Object Identifier

7 7.1.7 Usage of Certificate Policies Extension Policy Qualifiers Syntax and Semantics Processing Semantics for the Critical Certificate Policies Extension CRL Profiles Version Number(s) CRL and CRL Entry Extensions OCSP Profiles Version Number(s) Online Certificate Status Protocol Expansion Field Compliance Audits and Other Assessments Frequency and Circumstances of Assessment Identity/Qualifications of Assessor Assessor's Relationship to Assessed Entity Topics Covered by Assessment Actions Taken as a Result of Deficiency Communications of Results Other Businesses 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 Insurance Coverage Other Assets Insurance or Warranty Coverage for End-Entities Confidentiality of Business Information Scope Types of Confidential Information Information Not Within the Scope of Confidential Information Responsibility to Protect Confidential Information Privacy of Personal Information Privacy Plan Information Treated as Private Information Not Deemed Private Responsibility to Protect Private Information Notice and Consent to Use Private Information Disclosure Pursuant to Judicial or Administrative Process Other Information Disclosure Circumstances Intellectual Property Right Representations and Warranties CA Representations and Warranties RA Representations and Warranties Subscriber Representations and Warranties Relying Party Representations and Warranties Representations and Warranties of Other Participants Disclaimers of Warranties Limitations of Liability Indemnities Term and Termination Term

8 Termination Effect of Termination and Survival Individual Notices and Communications with Participants Amendments Procedures for Amendment Notification Mechanism and Period Circumstances Under Which OID Must be Changed Dispute Resolution Provisions Governing Law Compliance with Applicable Law Miscellaneous Provisions Entire Agreement Assignment Severability Enforcement (Attorney's Fees and Waiver of Rights) Force Majeure Other Provisions Appendix 2: Acronyms and Abbreviations

9 1. Introduction Taiwan-CA INC. (TWCA) is a joint-venture company formed by Taiwan Stock Exchange Corporation (TWSE), Taiwan Depository and Clearing Corporation (TDCC) Financial Information Service Corporation (FISC), and HiTrust Inc (HiTrust). In order to build a secure and trusted network transaction environment; to ensure information transmitted over the network is not fabricated, interpolated or marauded; to authenticate the identity of both parties of transactions and to prevent the repudiation of transactions afterwards, TWCA has established a public key infrastructure (PKI) to be the root certification authority (RCA) for the trust anchor. TWCA has also established various subordinate certification authorities (Sub-CA) to provide the subscriber network identity and transaction certification services in order to build up the user s faith in e-commerce transactions and to ensure the rights and benefits of both parties. In order to provide subscribes the certification service required for transactions made over the Internet, TWCA has established the Internet certification service system equipped with the related certification security mechanism. The service system is equipped with the leading-edge public key cryptography with security standards complying with the Electronic Banking Security Control Standards for Financial Institutions announced by the Ministry of Finance. The feature includes the non-repudiation, subscriber identify authentication, verification of information integrity, information encryption, and other forms of security controls required in network transaction security. The system can be applied to e-banking, online ordering, as well as other e-commerce systems, such as insurance, bonds and notes, enterprise enquiries, purchasing, and payment. 1.1 Overview The certificate policy (CP) of the PKI established by TWCA, collectively known as TWCA PKI CP, or CP), is a technical policy document established in accordance with the Electronic Signature Act of the Republic of China and the relevant international standards (e.g. IETF RFC 3647) as a reference for the PKI CAs to establish the certification practice statement (CPS). In order to cope with the e-commerce security requirements of various businesses, the PKI has included different kinds of CAs. CAs should follow this PKI CP to carry out the operating procedures, usage of certificates, responsibility and authority, and certificate administration specific to their CAs. 9

10 Special considerations have been made to the following items when establishing this CP: (1) whether or not relying party can identify the associations between the certificate holder (individual subscriber, corporate subscribers or subscriber of relevant hardware, software and application systems) and the public key specified in the certificate. (2) whether or not relying party can identify if the certificate holder has the corresponding private key; (3) whether or not subscribers and the relying party trust the security of PKI CAs, and their systems, keys, and operating procedures; and (4) the specifications of the Electronic Signature Act. 1.2 Document Name and Identification Based on the security level of certificates issued, the contents of certificates, the type of certificate, and the usage of certificate, assurance level are established in this CP, and each assurance level has a corresponding object identifier (OID). 10

11 The OID of this CP is: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) CP(5) id-twca-pki-cp-policy(5) } TWCA(40869) certificates(1) policies(1) } Based on the type of certificates, the OID of corresponding CPs is as follows: Commercial XML Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)XML(8) id-cp-policy(5) } TWCA (40869) certificates(1) policies(1) XML(12) } Commercial EC Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) EC+(3) id-cp-policy(1) } TWCA(40869) certificates(1) policies(1) EC(11) } Internet NB Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) NB(1) id-cp-policy(5) } TWCA(40869) certificates(1) policies(1) NB(13) } EC Security Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EC+(3) id-cp-policy(1) } TWCA(40869) certificates(1) policies(1) ECSECURITY(24) } SSL: 11

12 { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)SSL(3) id-cp-policy(5) } TWCA(40869) certificates(1) policies(1) SSL(21) } EV SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EV(6) id-cp-policy(5) } TWCA(40869) certificates(1) policies(1) EV(22) } InfoSec UCA: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) InfoSec(3) id-cp-policy(5) } TWCA(40869) certificates(1) policies(1) InfoSec(23) } Five assurance levels are defined in this CP, and their OIBs are as follows: assurance level OID Testing Class {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) CP(5) id-twca-pki-cp-policy(5) test(0)} TWCA(40869) certificates(1) policies(1) class0(0) }Commercial XML Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)XML(8) id-cp-policy(5) test(0)} TWCA(40869) certificates(1) policies(1) XML(12) class0(0) } Commercial EC Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) EC+(3) id-cp-policy(1) test(0)} TWCA(40869) certificates(1) policies(1) EC(11) class0(0) } Internet NB Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) NB(1) 12

13 id-cp-policy(5) test(0)} TWCA(40869) certificates(1) policies(1) NB(13) class0(0) } EC Security Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EC+(3) id-cp-policy(1) test(0)} TWCA(40869) certificates(1) policies(1) ECSECURITY(24) class0(0) } SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)SSL(3) id-cp-policy(5) test(0) } TWCA(40869) certificates(1) policies(1) SSL(21) class0(0) } EV SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EV(6) id-cp-policy(5) test(0) } TWCA(40869) certificates(1) policies(1) EV(22) class0(0) } InfoSec UCA: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) InfoSec(3) id-cp-policy(5) test(0) } TWCA(40869) certificates(1) policies(1) InfoSec(23) class0(0) } Class 1 {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) CP(5) id-twca-pki-cp-policy(5) class 1 Assurance(1)} TWCA(40869) certificates(1) policies(1) class1(1) } Commercial XML Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)XML(8) id-cp-policy(5) class 1 Assurance(1)} TWCA(40869) certificates(1) policies(1) XML(12) class1(1) } 13

14 Commercial EC Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) EC+(3) id-cp-policy(1) class 1 Assurance(1)} TWCA(40869) certificates(1) policies(1) EC(11) class1(1) } Internet NB Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) NB(1) id-cp-policy(5) class 1 Assurance(1)} TWCA(40869) certificates(1) policies(1) NB(13) class1(1) } EC Security Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EC+(3) id-cp-policy(1) class 1 Assurance(1)} TWCA(40869) certificates(1) policies(1) ECSECURITY(24) class1(1) } SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)SSL(3) id-cp-policy(5) class 1 Assurance(1) } TWCA(40869) certificates(1) policies(1) SSL(21) class1(1) } EV SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EV(6) id-cp-policy(5) class 1 Assurance(1) } TWCA(40869) certificates(1) policies(1) EV(22) class1(1) } InfoSec UCA: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) InfoSec(3) id-cp-policy(5) class 1 Assurance(1) } TWCA(40869) certificates(1) policies(1) InfoSec(23) class1(1) } Class 2 {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) CP(5) id-twca-pki-cp-policy(5) class 2 Assurance(2)} 14

15 TWCA(40869) certificates(1) policies(1) class2(2) } Commercial XML Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)XML(8) id-cp-policy(5) class 2 Assurance(2)} TWCA(40869) certificates(1) policies(1) XML(12) class2(2) } Commercial EC Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) EC+(3) id-cp-policy(1) class 2 Assurance(2)} TWCA(40869) certificates(1) policies(1) EC(11) class2(2) } Internet NB Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) NB(1) id-cp-policy(5) class 2 Assurance(2)} TWCA(40869) certificates(1) policies(1) NBCA(13) class2(2) } EC Security Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EC+(3) id-cp-policy(1) class 2 Assurance(2)} TWCA(40869) certificates(1) policies(1) ECSECURITY(24) class2(2) } SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)SSL(3) id-cp-policy(5) class 2 Assurance(2) } TWCA(40869) certificates(1) policies(1) SSL(21) class2(2) } EV SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EV(6) id-cp-policy(5) class 2 Assurance(2) } TWCA(40869) certificates(1) policies(1) EV(22) class2(2) } 15

16 InfoSec UCA: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) InfoSec(3) id-cp-policy(5) class 2 Assurance(2) } TWCA(40869) certificates(1) policies(1) InfoSec(23) class2(2) } Class 3 {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) CP(5) id-twca-pki-cp-policy(5) class 3 Assurance(3)} TWCA(40869) certificates(1) policies(1) class3(3) } Commercial XML Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)XML(8) id-cp-policy(5) class 3 Assurance(3)} TWCA(40869) certificates(1) policies(1) XML(12) class3(3) } Commercial EC Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) EC+(3) id-cp-policy(1) class 3 Assurance(3)} TWCA(40869) certificates(1) policies(1) EC(11) class3(3) } Internet NB Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) NB(1) id-cp-policy(5) class 3 Assurance(3)} TWCA(40869) certificates(1) policies(1) NB(13) class3(3) } EC Security Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EC+(3) id-cp-policy(1) class 3 Assurance(3)} TWCA(40869) certificates(1) policies(1) ECSECURITY(24) class3(3) } SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)SSL(3) id-cp-policy(5) class 3 Assurance(3) } 16

17 TWCA(40869) certificates(1) policies(1) SSL(21) class3(3) } EV SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EV(6) id-cp-policy(5) class 3 Assurance(3) } TWCA(40869) certificates(1) policies(1) EV(22) class3(3) } InfoSec UCA: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) InfoSec(3) id-cp-policy(5) class 3 Assurance(3) } TWCA(40869) certificates(1) policies(1) InfoSec(23) class3(3) } Class 4 {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) CP(5) id-twca-pki-cp-policy(5) class 4 Assurance(4)} TWCA(40869) certificates(1) policies(1) class4(4) } Commercial XML Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)XML(8) id-cp-policy(5) class 4 Assurance(4)} TWCA(40869) certificates(1) policies(1) XML(12) class4(4) } Commercial EC Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) EC+(3) id-cp-policy(1) class 4 Assurance(4)} TWCA(40869) certificates(1) policies(1) EC(11) class4(4) } Internet NB Certificate: {joint-iso-itu-t(2) country(16) Taiwan(886) TWCA(3) CA(1) NB(1) id-cp-policy(5) class 4 Assurance(4)} TWCA(40869) certificates(1) policies(1) NB(13) class4(4) } EC Security Certificate: {joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EC+(3) 17

18 id-cp-policy(1) class 4 Assurance(4)} TWCA(40869) certificates(1) policies(1) ECSECURITY(24) class4(4) } SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1)SSL(3) id-cp-policy(5) class 4 Assurance(4) } TWCA(40869) certificates(1) policies(1) SSL(21) class4(4) } EV SSL: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) EV(3) id-cp-policy(5) class 4 Assurance(4) } TWCA(40869) certificates(1) policies(1) EV(22) class4(4) } InfoSec UCA: { joint-iso-itu-t(2) country(16) Taiwan(158) TWCA(3) CA(1) InfoSec(3) id-cp-policy(5) class 4 Assurance(4) } TWCA(40869) certificates(1) policies(1) InfoSec(23) class4(4) } CAs under this PKI should specify and use in their CPS the OIDs specified in this CP. Where new OIDs are needed to identify with the new items in the certificate usage, CAs must expand these new OIDs according to the certificate OIDs defined in this CP. 1.3 PKI Participants All individuals applying this CP shall be the participants of this PKI. When using on application transaction systems, the public key certificates for a natural person or legal person specified in this CP provides the identification and authentication of the identify of both the activator and recipient of the transaction; authentication of information integrity; information privacy protection; the applicability and the rights and obligations of the non-repudiation mechanism; and the rules for certificate usage. 18

19 1.3.1 Certification Authority (CA) A CA is mainly responsible for the issue and administration of certificates. Based on the characteristics of operations, the CA falls into the RCA (root certification authority) and Sub-CA (subordinate certification authority). All CAs established under this PKI must follow the rules specified in this CP and must establish a contact window. When a CA is also a Sub-CA of other PKIs, this CP shall not apply to its up level of CA. As the trust anchor of this PKI, the RCA shall maintain the highest credibility and operate according to the highest assurance level of security specified in this CP. The Sub-CA is a Level 2 or Level 3 CA under this PKI. The certificate of a Level 2 CA is issued by the RCA, and the certificate of the Level 3 CA is issued by the Level 2 CA. for: As the highest certificate administration authority of the TWCA, the RCA is responsible (1) the issue and administration of the Sub-CA certificates; (2) the administration and publication of the certificates and certificate revocation lists (CRL) of Sub-CA stored in the repository; and (3) maintaining the stability and operations of the repository. The main duties of Sub-CAs are: (1) issue and administration of subscriber certificates; (2) issue and administration of registration authority (RA) certificates; (3) administering and publishing the certificates and CRLs stored in the repository; and (4) maintenance of the stability and operations of the repository. Sub-CAs issuing certificates to its Sub-CAs shall also be responsible for: (1) the issue and administration of Sub-CA certificates; and (2) the administration and publication of the certificates and CRLs of the Sub-CAs stored in the repository 19

20 1.3.2 Registration Authority (RA) The responsibilities of RA is to authenticate the identity of subscribers and the required information of the certificate for CAs to issue the subscriber certificate. CAs under this PKI shall specify the responsibilities of RAs in their CPS. When issuing a Sub-CA certificate, CAs under this PKI must be the RA and carry out the RA responsibilities specified in their CPS Subscriber The subscriber is the end entity specified in the CA certificate subject and the holder of the private key corresponding to the certificate public key. The usage of subscriber certificates shall be specified in the CPS. When issuing a certificate to an entity without the capacity specified by the law for the purpose of identification in the application system, such subscribers shall be the natural or legal person applying for the certificate Relying Parties A relying party means the acceptance the certificate of others (subscribers) for verifying the validity of the signature information or delivery of encryption information to the subscriber after encrypting the information of the subscriber certificate in order to maintain the privacy of the information contents of both parties in communication. Based on the information specified in the certificate, the relying party shall determine the reliability of certificate or if the certificate is intended for special usage Other Participant New members wishing to join this PKI shall be approved by the Policy Management Authority (PMA) center of the TWCA. For example, when it is necessary for the CAs of this PKI to cross certifued with the CAs of other PKIs. 20

21 1.4 Certificate Usage The assurance level of certificate specified in this CP and their appropriate uses are as follows: Testing Class: Testing assurance level is for the certificate testing of subscribers or relying party, and usage other than certificate testing is not guaranteed. Class 1: Basic assurance level is for identifying data integrity in network environments of very low threat of malicious interpolation. Class 2: Preliminary assurance level is for basic identity authentication suitable for use in network environments of lower risk of malicious interpolation but still with potential threat of information interpolation. Class 3: Intermediate assurance level is suitable for use in network environments of higher risk of malicious information interception or interpolation. Class 4: High assurance level is suitable for use in network environments of high risk of malicious information interpolation requiring a high recovery cost. When applying the assurance level and their limitations on the scope of these guarantees specified in this CP to certificates, CAs shall specify them in their CPS. Subscribers and relying party shall select the appropriate certificates according to the assurance level and their scopes of usage specified in the CPS Appropriate Certificate Uses Subject to the CPS of individual CAs Prohibited Certificate Uses Subject to the CPS of individual CAs. 1.5 Policy Administration Organization Administering the Document The Policy Management Authority (PMA or TWCA PMA), of the TWCA is responsible for the establishment, update, and publication of this CP. 21

22 1.5.2 Contact Person Subscribers may or mail their suggestions, description of suggestions, and contact information to the following contact window if they have any opinions on the certificate policy: Company TAIWAN-CA INC. (TWCA) Contact Window Policy Management Authority (PMA) Address 10th Floor, 85 Yen-Ping South Road, Taipei City, Taiwan, R.O.C Phone Fax Person Determining CPS Suitability for the Policy The certification practice statement (CPS) established by CAs under this PKI must be approved by the PMA CPS Approval Procedures CAs shall establish the CPS and ensure their consistency with this CP. Also, according to the Electronic Signature Act, CPSs established by CAs must be approved by the Ministry of Economic Affairs (MOEA) before they are allowed to issue certificates. 22

23 2. Publication and Repository Responsibilities 2.1 Repositories The repositories shall offer the enquiry and download of information relating to certificate operations, such as certificates, CRLs, certificate status, CP, and CPS. Each CA under this PKI must provide at least one external repository, and its universal resources location (URL) shall be specified in the CA s CPS. The CA shall ensure the availability, accessibility, and information integrity of the repository. 2.2 Publication of Certificate Information CAs shall publish the information required by subscribers and relying party, including but not limited to the CPS and CRL. The CA information to be published shall be subject to the CPS of respective CAs. 2.3 Frequency of Publication The frequency of publication of the CA information shall be subject to the CPS of respective CAs. The frequency of publication of the CRL shall be published in the CPS. 2.4 Access Control of Repository CAs shall establish the specifications for repository access control in their CPS. 23

24 3. Identification and Authentication CAs under this PKI shall establish in their CPS and registration specifications the procedures for identifying and authenticating the subscriber identity. 3.1 Naming Types of names CAs shall be able to issue the X.509 certificate using the X.500 unique identifier as subject name. CAs shall specify in the CPS the types of names. CAs may use the expanded subject alternate name extension field where necessary, provided that the subject name field must not be null, and the subject alternate name shall comply with the X.500 standard Need for Names to be Meaningful The subject identity name specified in the certificate shall be able to identify the particular organization, unit or individual, and shall be readily identifiable by the relying party Anonymity and Pseudonymity of Subscribers The CA shall not issue anonymous or pseudonymous certificates Rules for Interpreting Various Name Forms The interpretation rules for subscriber name shall be subject to the relevant rules and regulations specified by the competent authorities. For example, the identifier of an Internet account shall be processed according to the rules governing the bank code and the user account for banks assigned by the Financial Data Center, Ministry of Finance; the uniformed identifier for the citizen identity card of individuals shall be processed according to the rules specified by the Ministry of the Interiors; the identifier of the profit business tax code shall be processed according to the rules specified by the MOEA; and the rules for interpreting other subscriber identifiers shall be subject to the CPS of respective CAs Uniqueness of Names CAs shall ensure the uniqueness of the name in the certificates issued by them, and shall 24

25 specify in their CPSs the nominalization rules and rules for ensuring name uniqueness Recognition, Authentication, and Role of Trademarks When identical identifiers are detected, CAs shall assign the identifier to the first applicant. However, when another applicant requests the same identifier with the documents issued by the relevant competent authorities, CAs shall settle the dispute over such identifier. CAs shall specify in the CPS the procedures for settling disputes over identifier Identification, Authentication and Role of Trademarks Subject to the CPS of respective CAs. 3.2 Initial Identity Verification Method to Prove Possession of Private Key If the private key corresponding to the certificate public key is generated by the subscriber, a CA shall request the subscriber to submit the prove possession of the private key, such as verify the signature information signed by private key (e.g. using the methods specified in the RFC 2314, RFC 2510 and RFC 2511 standards). It will be no need to verify private key possession when the private key is generated by the RA, CA or other authorized third-party, provided that the security measures for private key delivery shall be specified in the CPS Authentication of Organization Identity When authenticating the status of organizations, the organization shall submit documents issued by the competent authorities or other certifications proving its existence. The identity and authorization of its statutory representative shall be verified. If the application is made by the authorized agent of an organization, this agent shall also submit his/her identify certifications. All documents and/or certifications shall be submitted in writing or carried to the count by the agent in person. The following shows the requirements for the identity authentication of organization under 25

26 various assurance level: Testing Class: To be specified by CAs in their CPS. Class 1: Limited verification of the subscriber name and information with simple procedures by . Class 2: In addition to organization name clearance, subscribers shall submit legal and correct certifications, without completing the procedures over the counter. Class 3: In addition to the information clearance specified in Class 2, an authorized agent carrying a valid letter of assignment shall make the application over the counter, and the agent shall submit his/her own certifications of identity or any procedures valid for authenticating the true identity of subscribers. Class 4: In addition to the information clearance specified in Class 3, the application shall be made by the statutory representative in person over the counter, and the statutory representative shall submit certifications valid for identifying his/her identity. When performing the initial verification of the information or communication hardware and software equipment of an organization (e.g. routers, firewalls, and servers), the equipment administrator shall submit the following registration information: equipment identification (e.g. serial number) or service name (e.g. domain name); equipment public key; the licensing usage and attributes of equipment (e.g. the licensing usage or attributes shall be only be specified when it is included in the certificate); the contact information of administrators for contacts made by the RA or CA; CAs shall verify registration data with methods corresponding to the assurance level of certificates being applied for. The verification methods shall include, but not limited to, the methods specified in this part for authenticating the identity or the digital signature of subscribers (signature certificates shall be issued according to this CP). 26

27 3.2.3 Authentication of Individual Identity The following show the requirements for the identity authentication of individual subscribers under various assurance level: Testing Class: To be specified by CAs in their CPS. Class 1: Limited verification of the subscriber name and information with simple procedures by . Class 2: In addition to individual name clearance, subscribers shall submit legal and correct certifications, without completing the procedures over the counter. Class 3: In addition to the information clearance specified in Class 2, the individual subscriber or his/her agent carrying a valid letter of assignment shall make in person the application over the counter Class 4: In addition to the information clearance specified in Class 3, the application shall be made by the individual subscriber in person over the counter. For the information or communication hardware and software equipment held by individual subscribers, the individual subscribers shall be deemed as the administrator of such equipment and shall complete the verification according to section Non-Verified Subscriber Information No applicable Validation of Authority The certifications of identity of an individual, organization agent and organization shall be issued by the relevant government agencies. The RA shall validate the authenticity of the letter of assignment submitted by an agent. 27

28 3.2.6 Criteria for Interoperation No applicable. 3.3 Identification and Authentication for Re-Key Requests Subscribers of CAs shall follow the identity authentication requirements below to perform the subscriber identity identification and authentication for re-key request. Testing Class: No stipulation. Class 1: No stipulation. Class 2: The key identify authentication shall be performed with the password of the authorized account or the use of current signature key. Class 3: The key identify authentication shall be performed the use of current signature key. Class 4: The initial verification shall be performed for every re-key request Identification and Authentication for Routine Re-Key The longer the time of use of a key, the higher the risk of key discloser or compromise. For this reason, it is necessary to change over the key for certificate subscribers to ensure key security. The changeover of certificate keys means to re-generate a public key and private key pair and to apply new certificate from the CA with the old registration data. The features and assurance level of the new certificate issued after re-key shall remain the same as the old certificate. CAs shall specify in the CPS the requirements of routine re-key for the subscriber identity identification and authentication. 28

29 3.3.2 Identification and Authentication for Re-Key After Revocation After revoking a certificate, subscribers shall repeat the initial verification specified in section 3.2 in order to apply new certificate. 3.4 Request of Certificate Revocation CAs shall authenticate the request of certificate revocation. In authenticating a request of certificate revocation, CAs may verify the signature generated with the private key of the corresponding certificate, whether or not the private key has been compromised. 29

30 4. Certificate Life-Cycle Operational Requirements 4.1 Certificate Application Submition of Certificate Application When the certificate user is a natural person, he/she is the certificate applicant. When the certificate user is an orgnization, the statutory representative or his/her agent is the certificate applicant Enrollment Process and Responsibilities Certificate applicants shall read through the terms of use (TOU) in advance. After agreeing to the TOU, applicants shall complete the application form together with the signed TOU to the RA. CAs shall specify in the CPS the methods for delivering the public key to the certificate issuer. 4.2 Certificate Application Processing Performing Identification and Authentication Functions The RA shall follow the procedures below to handle the certificate application. To acquire the relevant data of certificate application of applicants is described in section 3.2. To verify and record the identification data of applicants is described in section 3.2. To acquire the public key of applicants and check its associations with the private key of applications is described in section 3.2. To validate the authenticity of information specified in the certificate. 30

31 CAs shall establish and specified the steps for completing the above procedures in the CPS. These procedures shall be completed prior to the issue of certificates Approval or Rejection of Certificate Application After completing the Identification and authentication Procedures described in section 4.2.1, the application for certificates shall be deemed as accepted. When it is unable to complete the above identification and authentication procedures, the certificates application shall be rejected Time to process Certificate Applications No stipulation. 4.3 Certificates Issuance CA Actions During Certificate Issuance The identity authentication shall be performed in communication of any forms between the RA and the CA. The communication shall be made either online or offline. The integrity and privacy of information shall be maintained during the communication. When delivering the public key of certificate applicants to the CA, the CA shall ensure that the application data are correctly linked with public key. The CA may ensure the linkage with cryptographic methods or the non-cryptographic physical or procedural methods. These shall include, but not be limited to, the use of diskette (or other storage devices) delivered by with registered mail or courier service. After receiving the request of certificate issue, the CA shall verify the identity of sender; examine the integrity of delivered data; validate the contents of the request of certificate issue and generate and issue the certificate after ensuring that the certificate contents meet the requirements Notifications to Subscriber of Certificate Issuance After issuing certificates, CAs shall notify the issue of certificates with appropriate 31

32 methods and deliver the certificate to the corresponding subscribers. When the issue of certificates is rejected, CAs shall notify subscribers with appropriate methods and inform subscribers of the reasons of rejection. The notification and delivery also can be made through the RA. Apart from the applicant s failure to pass the verification, CAs may disapprove the issue of certificates for other reasons. 4.4 Certificate Acceptance CAs shall specify the following in the CPS: procedures of subscriber certificate acceptance; certificate applicants have accepted and understood the responsibilities and obligations for using the certificate; how to inform certificate applicants of the contents of certificates; and when a certificate applicant rejects the certificate issued after reviewing the certificate contents, the RA shall notify the CA to revoke the certificate Conduct Constituting Certificate Acceptance Subscribers shall validate if the contents registered in the certificate are correct and understand the TOU before start to use the certificate Publication of the Certificate by the CA CAs may publish the issued certificates to the repository Notification of Certificate Issuance by the CA to Other Entities Apart from delivery the certificate to the subscriber, CAs may deliver the certificate to the RA after the issue. 4.5 Key Pair and Certificates Usage Subscriber Private Key and Certificate Usage The subscriber is the holder of the private key corresponding to the certificate public key. Restrictions in the intended scope of usage for a private key are specified through certificate extensions, including the key usage and extended key usage extensions, in the associated certificate. 32

33 CAs shall specify in the CPS the scope of certificates usage they issue. When there are doubts of private key fraud, disclosure, compromise or loss, subscribers shall report to the RA or CA according to the procedures specified in the CPS of respective CAs. The usage and constrain of subscriber s certificate and private key shall follow the rule specified in this CP and the CA s CPS Relying Party Public Keys and Certificates Usage The examination steps for relying party to determine a trustee certificate are not specified in this CP. When examining a certificate, relying party shall follow the rules in the CPS of respective CAs to create a trust path and to verify the certificate status as a reference for determining to trust or not a certificate. The relying party shall only apply a certificate to examine the correctness of a digital signature in the electronic documents and the identity of the signature holder after trusting a certificate. 4.6 Certificate Renewal Circumstances for Certificate Renewal A certificate renewal means the issue of a new certificate using the same subscriber information and containing the same key but a different serial number and an extended validity. not. CAs under this PKI shall determine independently whether to accept certificate renewal or Who May Request Renewal All certificate subscribers are eligible for renewing a certificate Processing Certificate Renewal Request Prior to the expiration of a certificate, subscribers shall apply for the issue of a new certificate to the RA or CA with the original registration information and public key. After receiving an application for certificate renewal, the CA shall validate the 33

34 correctness of the registration information and public key of the applicant. The CA shall issue a new certificate as described in section Notification of New Certificate to Subscribers See section Conduct Constituting Acceptance of a Renewal Certificate See section Publication of Renewal Certificate by the CA See section Notification of Certificate issuance by the CA to Other Entities See section Certificate Re-Keys Circumstances for Certificate Re-Keys The certificate re-key means the generation of a new public and private key pair and apply a new certificate to the CA with the origin registration information. CAs under this PKI shall specify independently the certificate re-key procedures Who May Request Certification of a New Public Key All certificate subscribers are eligible for request the certification of a new public key Processing Certificate Re-Keying Requests CAs shall perform the identification and authentication of subscriber identity as 34

35 described in section 3.3. CAs shall issue the certificate as described in section Notification of New Certificate Issuance to Subscribers See section Conduct Constituting Acceptance of a Re-Keyed Certificate See section Publication of the Re-Keyed Certificate by the CA See section Notification of Certificate Issuance by the CA Other Entities See section Certificate Modification A certificate modification means the issue of a new certificate after changing the identification information of the subscriber name, without changing the public key of the certificate Circumstances for Certificate Modification Subject to the rules specified in the CPS of respective CAs Who May Request Certificate Modification Subject to the rules specified in the CPS of respective CAs Processing Certificate Modification Requests Subject to the rules specified in the CPS of respective CAs. 35

36 4.8.4 Notification of New Certificate Issuance to Subscriber Subject to the rules specified in the CPS of respective CAs Conduct Constituting Acceptance of Modified Certificate Subject to the rules specified in the CPS of respective CAs Publication of the Modified Certificate by the CA Subject to the rules specified in the CPS of respective CAs Notification of Certificate Issuance by the CA to Other Entities Subject to the rules specified in the CPS of respective CAs. 4.9 Certificate Revocation and Suspension Circumstances for Certificate Revocations A certificate is revoked when (1) subscribers wish to terminate the use of a certificate or the certificate contract is terminated. (2) the subscriber information in the certificate has been changed during the certificate is valid. (3) the relevant private key of the certificate is proven or suspected to be compromised, damaged, lost, discloser and/or interpolated. (4) the subscriber breaches the CP, CPS or subscriber agreement. (5) The CA signature key is proven or suspected to be cracked. When the above situations occur, the relevant certificate shall be revoked and added to the CRL. All revoked certificates shall be included in the CRL published later than the revocation, until they are expired. 36

37 4.9.2 Who Can Request Revocations CAs shall specify in the CPS the eligibility for requesting a certificate revocation Procedure for Revocation Request Applicants applying for a certificate revocation shall specify the certificate(s) to be revoked and the reason(s) for revocation. CAs shall specify in the CPS the procedures of certificate revocation Revocation Request Grace Period CAs shall specify in the CPS the revocation request grace period Time Within Which CA Must Process the Revocation Request CAs shall specify in the CPS the handling time of requests of certificate revocation Revocation Checking Requirements for Relying Parties Relying party shall determine the interval for enquiring (or downloading) the revocation data (CRL) according to their risk, responsibility and consequences. When authenticating the digital signature of a subscriber certificate, relying party shall check if the certificate has been revoked. CAs shall specify in the CPS the requirements of relying party to verify the RCL CRL Issuance Frequency CAs shall generate the CRL at planned intervals. Information of revoked certificates shall be updated within the time specified in the Next Update field in the CRL and include the information of revoked certificate in the CRL in the next update for relying party to enquire. CAs shall publish the CRL at planned intervals; even no subscribers have revoked any certificate during the interval. Basically, CAs shall generate a CRL once every 24 hours, though the frequency of CRL generation may vary according to individual CPS. 37

38 CAs shall specify in the CPS the CRL issue frequency Maximum Latency for CRLs The maximum latency for CRL means the time difference between the CRL generation and publication to the repository. This is not defined in this CP On-Line Revocation/Status Checking Availability CAs may provide the Online Certificate Status Protocol (OCSP) according to the actual needs. As real-time enquiries of certificate status may not be required by all relying party, CAs shall provide at least the CRL download service and specify in the CPS the availability of OCSP On-Line Revocation Checking Requirements CAs shall specify in the CPS the OCSP inspection rules Other Forms of Revocation Advertisements Available CAs shall specify in the CPS the operating methods of other forms of certificate status query functions, and shall apply protection for in information equivalent to the CRL protection Special Requirements Related To Key Compromise When the signature key is compromised, CAs shall follow the instructions below: (1) Revoke all issued certificates. (2) Update the CRL or the certificate status information of the OCSP. (3) Generate the new signing key pair and corresponding new certificate. (4) Notify Sub-CAs that the superior CA key has been compromised. (5) When the key of an Sub-CA is compromised, the Sub-CA shall report to the superior CA within 24 hours. (6) Using new signing key, issue the new certificates to subscriber according to Parts 4.2 and 4.3. (7) The new certificates shall be delivered as described in

39 CAs shall specify in the CPS the handling procedures for key compromise Circumstances for Suspension Subject to the CPS of respective CAs Who Can Request Suspension Subject to the CPS of respective CAs Procedures for Suspension No certificate suspension is available, except for CAs issuing subscriber certificates. When provide certificate suspension service, CA shall specify in the CPS the procedures of certificate suspension Limits on Suspension Period Subject to the CPS of respective CAs Certificate Status Service Operational Characteristics See section 4.9.9, , and Service Availability See section 4.9.9, , and

40 Operational Features See section 4.9.9, , and End of Subscription Certificates issued by CAs shall be invalid when they are terminated or expired, or when the CA shuts down its business Key Escrow and Recovery Key Escrow and Recovery Policy and Practices See section Session Key Encapsulation and Recovery Policy and Practices No stipulation. 40

41 5. Facility, Management, and Operational Controls 5.1 Physical Control Site Location and Construction The construction of the site location of CAs shall comply with the standards of computer rooms for storing highly important and sensitive information and be equipped with physical security controls, such as access control, security, intrusion detection, and CCTV system, in order to prevent unauthorized access to certificate-related equipment Physical Access The physical controls of CAs shall comply with at least the following requirements: (1) to prevent unauthorized access to hardware storage devices; (2) to ensure that all mobile storage media or paper documents containing sensitive information are stored in a secure place; (3) to apply manned or automatic monitoring and recording of unauthorized access at all times; and (4) to review the access records and ensure their availability. CA computer rooms where certificate issuing equipment is located shall be equipped with access controls, and access is only made possible by two or more persons Power and Air Conditioning CAs shall be equipped with adequate power supply and air-conditioning equipment that can be operable or shut down regardless of external influences. Also, a backup power supply system shall be equipped to supply electricity of no less than 6 hours for the repository to perform data backup Water Exposures CA equipment shall be installed in locations containing physical protection against floods. 41

42 5.1.5 Fire Prevention and Protection CA computer rooms shall be equipped with automatic fire extinguishing equipment to automatically extinguish any fire detected. A manual control shall be equipped at all major entrances for onsite personnel to operate such equipment in an emergency Media Storage The media storage environment of CAs shall be sited or protected to prevent damage as a result of accidents. The backup copy of important data shall be stored in a location other than the CA s location Waste Disposal CAs shall establish and maintain and specify in the CPS procedures for the secure removal and destruction of sensitive information Off-Site Backup CAs shall be equipped with off-site backup facilities and specify in the CPS the off-site backup mechanism. 5.2 Procedural Controls Trusted Roles CAs shall perform certificate management with well-laid and secure operating procedures. In order to ensure optimal duty assignment and that the disaster recovery assignment shall not affect system security and operation integrity, CAs shall define in the CPS the trusted roles and their duties. The four roles and their duties under this CP are defined as follows: (1) Administrator: To be responsible for system installation, management, and environment parameter setup. (2) Officer: To be responsible for generating the Certificate Service Request(CSR) files and the revocation and issue of certificates. (3) Auditor: To be responsible for internal audits, and the review and maintenance of audit reports. (4) Operator: To be responsible for routine maintenance, such as data backup, data recovery, and website data maintenance. 42

43 5.2.2 Number of Persons Required per Task CAs shall specify in the CPS the number of persons required per task as described in Identification and Authentication for Each Role Each role shall be identified and authenticated prior to carrying out the designated duties Roles Requiring Separation of Duties CAs shall perform duty separation according to the following rules: (1) equip with the four roles as described in section 5.2.1; (2) the officer and the administrator shall not be the same person; (3) the officer and the auditor shall not be the same person; (4) the administrator and auditor shall not be the same person. 5.3 Personnel Control Qualifications, Experience, and Clearance Requirements CAs shall establish the competence requirements for operators implementing certificate management. These requirements shall at least include loyalty and reliability, and no criminal or credit records. The competence requirements shall be specified in the CPS, including the requirements for third-party personnel, if applicable Background Check Procedures CAs shall establish the procedures for reviewing the background and duties of operators operating the certificate management system, and such procedures shall meet the requirements as described in section Training Requirements Based on the duty of operators, CAs shall provide education and training concerning the operation of hardware and software functions, operating procedures, security control procedures, CP, CPS, and other related techniques and policies. 43

44 5.3.4 Retraining Frequency and Requirements After a modification of the operating environment or security management, CAs shall provide operators appropriate training and shall specify in the CPS the education and training plan and frequency Job Rotation Frequency and Sequence CAs shall establish the operating procedures for job rotation and specify these procedures in the CPS Sanctions for Unauthorized Actions CAs shall specify in the CPS the procedures for punishing unauthorized actions Independent Contractor Requirements CAs shall specify in the CPS the control procedures of contractor personnel Documentation Supplied to Personnel The operating documentation of CAs shall at least meet the requirements for personnel of different roles to carry out their duties. CAs shall specify in the CPS the requirements of operating documentation. 5.4 Audit Logging Procedures Types of Events Recorded Either manually or automatically recorded, CP audit records shall include at least the following items: (1) Type of event. (2) Event date and time. (3) Event place or location. (4) Results (success or failure) of certificate issue or revocation. (5) Entity or individual evoking the event. 44

45 When an event occurs, the audit record shall be recorded either electronically or physically at the choice of the CA. The types of audit events recorded by CAs are as follows: (1) Security audit management. (2) Management, identification and authentication of personnel and trusted roles. (3) Creation, modification and deletion of subscriber information. (4) Generation of CA key. (5) Changes of private keys and trustee public keys. (6) Certificate applications, issue, revocation and status change. (7) Certificate management system configuration and change. (8) Activation and deactivation of systems and applications. (9) Personnel login and logout systems and applications. (10) Cryptographic Module installation, removal and destruction. (11) Access control management and access to physical environment. (12) Hardware and software system updates. (13) Data backup and recovery. (14) Unauthorized access to file systems. (15) Abnormal network system access. (16) Key compromise, system anomalies and hazards. (17) Violations of the CP and CPS Frequency of Processing Log CAs shall inspect the audit records at least once a month. The inspection shall include the integrity of audit records, the non-interpolation of audit records, and review of all record items. Anomalies or warnings shall be carefully investigated. Solutions for the inspection results shall be documented Retention Period of Audit Log The relevant audit records and reports and media data shall be retained at the CA for at least two months. The relevant audit records shall be archived prior to removal, except to video recordings Protection of Audit Log CAs shall prevent the retrieval of audit records by unauthorized personnel and make a backup copy of audit records, and shall prevent audit records from interpolation. 45

46 5.4.5 Audit Log Backup Procedures CAs shall specify in the CPS the procedures of making backup copies of audit records. Backup copies of audit records shall be made at least once a month, and a copy shall be stored in a off-site location outside of the CA Audit Collection System (Internal vs. External) Audit records may be collected outside of or inside the CA certificate management system. The automatic audit procedure shall be activated by the certificate management system until the system shuts down. Audit records may be collected automatically by the computer or manually by the operating system, certificate management system or certificate management operators Notification to Event-Causing Subject When an event is recorded by the audit system, there is no need to notify the related personnel generated the event. The reporting procedures of abnormal events shall be specified in the CPS of individual CAs Vulnerability Assessments CAs shall assess the vulnerabilities of the security control at planned intervals. 5.5 Record Archival Types of Records Archived The archival records of CAs shall include at least the following five types: (1) Data concerning the external accreditation of CAs (2) CPS (3) Contracts related to CA operations (4) System environment implementation and setup files (5) System change records (6) Certificate application files (7) All issued and published certificates (8) Key Changeover records (9) Audit data files (10) Revocation request record (11) Subscriber registration data (12) Subscriber contracts (13) Revoked certificate data files (14) Data and tools for verifying archival records 46

47 (15) Documents requested by auditors CAs offering subscriber key escrow service shall also archive such keys Retention Period for Archive CAs shall retain archival data for at least 7 years, and shall specify in the CPS the retention period of archival data Protection of Archive No writing, modification or deletion of archival data shall be allowed. Archival personal data of subscribers are allowed for retrieval by the subscriber, his/her agent, and legally approved agencies. A cope of archival data shall be retained in another site equipped with security controls and harmless to the storage media Archive Backup Procedures CAs shall specify in the CPS Requirements for Time-Stamping of Records CAs shall specify in the CPS Archive Collection System (Internal or External) CAs shall specify in the CPS Procedures to Obtain and Verify Archive Information CAs shall specify in the CPS. 5.6 Key Changeover In order to minimize the risk of compromise of the CA signing key, CAs shall change over 47

48 the CA signing key at plant intervals, and shall not use the previous key to issue certificates after the changeover. When selecting key validity, CAs shall consider the length, protection, controls and other factors related to the key. The key validity shall not exceed the term described in section Compromise and Disaster Recovery Incident and Compromise Handling Procedures CAs shall provide services of high reliability and specify procedures for handling incident, including procedures for handling natural disasters, accidents, and key compromise, in order to ensure the quick recovery of services interrupted as a result of incident Computing Resources, Software, and/or Data Are Corrupted CAs shall re-implement as soon as possible any abnormal or damaged equipment and shall put the recovery of certificate status information generation on the top priority. CAs shall specify in the CPS the recovery procedures and conduct an exercise on the recovery of computer resource, software and data damage at least once a year Entity Private Key Compromise Procedures CAs shall specify in the CPS or related documents the procedures for handling the compromised private key of members within this PKI Business Continuity Capabilities After a Disaster CPS shall specify in the CPS the procedures for rescuing CA equipment and maintaining business operations prior to the reconstruction of a secure environment after a natural disaster or other accidents. 5.8 CA or RA Termination CAs shall specify in the CPS the procedures to be followed after the termination of service, and such procedures shall comply with the Electronic Signature Act. 48

49 6. Technical Security Control 6.1 Key Pair Generation and Installation Key Pair Generation The process of key pair generation shall be specified in the CPS. The key generation equipment of CAs shall at least be equipped with the hardware cryptographic module complying with the FIPS 140-1, or FIPS level 3 or higher levels Private Key Delivery to Subscriber CAs offering subscriber key pair generation service shall specify in the CPS the security controls for private key delivery Public Key Delivery to Certificate Issuer When delivering the subscriber public key to the CA, the authenticity of data shall be validated. The public key shall be delivered by means of electronic signature-protected message, physical media (e.g. diskette) by courier service or the applicant in person, or other means. CAs shall establish in the CPS the methods of public key delivery to CAs CA Public Keys Delivery to Relying Parties When it is necessary for CAs to deliver a public key, the protection for the information integrity of the public key shall at least be provided Key Sizes The size of RCA RSA key shall at least be 2048 bits. The size of the RSA key of other CAs of other levels shall at least be 1024 bits. The size of the subscriber RSA key shall at least be 1024 bits, except for SSL certificates issued for encryption purposes and certificates issued for special information systems, or certificates with special requirements specified by relying party. 49

50 6.1.6 Public Key Parameters Generation and Quality Checking The generation and selection of CA public key parameters shall be the prime number parameters generated by the random number generator complying with FIPS 186-2, FIPS 186-1, or similar specifications; or the generation of random numbered public key parameters shall comply with FIPS or FIPS When subscribers use hardware cryptographic modules (e.g. IC card), such modules shall comply with FIPS or FIPS Level 2 (inclusive) or other specifications of the same security level Key Usage Purposes (as per X.509 v3 Key Usage Field) The constraints of key usage purposes shall be specified in the extension field of key usage purposes of the X.509 certificate. Only the keycertsign and crlsign bits shall be set in CA certificates for issuing certificates and CRLs. The digitalsignature and/or nonrepudiation bit shall be set in the subscriber signature certificate, and the keyencipherment and/or dataencipherment bit shall be set for encrypted certificates. CAs issuing certificates for other usage shall specify the key usage purposes in the CPS, except for signature and encrypted certificates. 6.2 Private Key Protection and Cryptographic Module Engineering Controls Cryptographic Module Standards and Controls CA cryptographic modules shall pass the Level 3 (or higher) certification of FIPS or FIPS 140-1, or other specifications of the same security level. 50

51 RA software and hardware cryptographic modules shall comply with pass the Level 2 (or higher) of FIPS or FIPS 140-1, or other specifications of the same security level. When subscribers use hardware cryptographic modules (e.g. IC card), such modules shall comply with FIPS or FIPS Level 2 (inclusive), or other specifications of the same security level. All CA cryptographic modules shall be equipped with multiparty security controls Private Key (n out of m) Multi-Person Control The signature private key of CAs shall comply with the multiparty security control procedure described in section Private Key Escrow No CA signing private keys shall be escrowed. CAs offering subscriber private key escrow, recovery and retention services shall specify in the CPS the relevant operating procedures Private Key Backup The backup of CA private keys stored in an encrypted hardware cryptographic module after encryption shall be performed by means of multi-person control, and the backup copy shall be retained in the off site. CAs shall specify in the CPS the produces for making private key backup copies. The procedures for making and retaining backup copies of RA and subscriber private keys are not specified in this CP Private Keys Archive No CA signing private keys shall be archived. CA encryption private keys can be archived, and CAs shall specify in the CPS the procedures for CA encryption private key encryption. 51

52 The procedures for RA and subscriber private key achieve are not specified in this CP Private Key Transfer Into or From a Cryptographic Module Private keys shall be generated in the cryptographic module. When it is necessary to transfer a private key from one cryptographic module to another cryptographic module, the transfer shall be performed by authorized personnel. Also, private keys shall not exist in plaintext outside of the cryptographic module. The encryption key for encrypting private keys shall be protected against leakage Private Key Storage on Cryptographic Module Private keys shall be stored in the cryptographic module in either plaintext or cipher text Method of Activating Private Key Private keys stored in the cryptographic module shall be activated by authorized personnel after identity authentication. The authentication shall include, but not be limited to, password, PIN, or biometric identification. Activation data shall be protected against leakage during data entry Method of Deactivating Private Key Private keys shall be deactivated by authorized personnel. CAs shall specify in the CPS the procedures for private key deactivation Method of Destroying Private Key When the CA signing private key is no more in use, or the corresponding public key has expired or is revoked, the private key in the cryptographic module shall be expunged by means of zeroization Cryptographic Module Rating The cryptographic modules used by CAs shall pass the Level 3 or higher level certification of FIPS or FIPS 140-1, or other specifications of the same security level. CAs shall specify in the CPS the specification of subscriber cryptographic modules. 52

53 6.3 Other Aspects of Key Pair Management Public Key Archival The public key has been archived when the certificate is archived. Therefore, it is not need to archive the public key again Certificate Operational Periods and Key Pair Usage Periods The validity of the public key and private key of participants of this PKI may be the same. The validity by strength (key sizes) is as follows: (1) RSA 4096-bit key pair: maximum 40 years. (2) RSA 2048-bit key pair: maximum 30 years. (3) RSA 1024-bit key pair: maximum 10 years. CAs shall specify in the CPS or relevant operating procedures the validity of the Sub-CA and subscriber keys. 6.4 Activation Data CAs shall specify in the CPS the protection of activation data, including the protection of the entire lifecycle of data from generation, archive to destruction Activation Data Generation and Installation Activation data for deciphering CA s or subscriber s private keys or the relevant access control mechanisms shall be protected appropriately. CA activation data may be selected by the user by means of multi-person control. Activation data shall be protected with biometric or cryptographic-module-enhanced security mechanisms. Subscribers may select their own activation data. Data that must be generated prior to delivery shall be delivered through channels with appropriate protection. 53

54 6.4.2 Activation Data Protection CA activation data shall be protected with cryptographic or physical access control Other Aspects of Activation Data CAs may specify in the CPS the operating procedures of activation data according to the security requirements of the scope of certificate usage. 6.5 Computer Security Control Specific Computer Security Technical Requirements CAs shall provide the following security controls from the operating system or by integrating operating system, software and hardware protection technologies. User login identification and authentication. User-defined access control. Security audit capability. Access control constraints of CA services and PKI trusted roles. Identification and authentication of PKI trusted roles. Communication and database security. Secure and trusted channels for the identity authentication of PKI trusted roles. Procedural integrity and security control protection Computer Security Rating CA computer platforms shall comply with at least the EAL3 [ISO / IEC Common Criteria], C2 [TCSEC] or E2 [ITSEC] security standards. CAs shall specify in the CPS the standards of the security level of their computer platforms. 6.6 Life Cycle Technical Controls System Development Controls The development of the CA certificate management system shall comply with the following requirements: 54

55 Detailed documentation shall be furnished. The purchase of certificate management system software and hardware shall minimize the procedure of component interpolation. CA-specific software and hardware shall be developed in a controllable environment, and the development process shall be defined and documented Security Management Controls CAs shall ensure complete control and maintain records of the settings, modifications and upgrades of the certificate management system; and mechanisms for detecting unauthorized software modification or setting changes shall be equipped. CAs shall establish and maintain controls to ensure the software integrity of the certificate management system. CAs shall establish and maintain the operating procedures for the security control over the lifecycle of the hardware and software equipment of the certificate management system. A security clearance policy shall be established for accepting hardware and software equipment. CAs shall only install certification-related software in and run related operations on the hardware and software equipment of the certificate management system. Software unrelated to CA business or certification shall not be installed in the system. The installation and update of software and hardware equipment shall be subject to the relevant operating procedures in an environment with security control Life Cycle Security Controls No stipulation. 6.7 Network Security Controls The CA certificate management system shall be equipped with an independent operating system to be operated by authorized personnel. CAs shall install and implement firewalls, IDS and antivirus management system to protect the network against intrusions and damage in order to improve the security controls of the NMS(Network Management System). 55

56 The RCA certificate management system shall be installed in an environment with security control and shall be set to off-line status when not in use. The system shall only be used with an authorization. 6.8 Time-Stamping No stipulation. 56

57 7. Certificate, CRL, and OCSP Profiles 7.1 Certificate Profiles CAs shall specify in the CPS or the relevant operating procedures the format of certificates they issue Version Number CAs shall issue certificates in the X.509 V3 (ITU-T X /1997, ISO ) version Certificate Extensions s The use of certificate expansion fields shall comply with the ITUT X.509 or IETF RFC 3280 standards Algorithm Object Identifier The algorithm OIDs for certificate issues are as follows: Algorithm Type Algorithm OID Key rsaencryption {iso(1)member-body(2)us{840}rsadsi( )pkcs(1)pkcs-1(1)1} Signature sha1withrsaencryption {iso(1)member-body(2)us{840}rsadsi( )pkcs(1)pkcs-1(1)5} Signature sha256withrsaencryption {iso(1)member-body(2)us{840}rsadsi( )pkcs(1)pkcs-1(1)11} Name Forms The format of the subject alternate name of certificates issued by CAs shall comply with the X.500 Distinguished Name (DN) format Name Constraints CAs may use the Name Constraint extension field in the certificates issued if necessary. 57

58 7.1.6 Certificate Policy Object Identifier CAs may include the CP OID in the certificates issued if necessary Usage of Certificate Policies Extension CAs may use the Certificate Policy Constraints Extension Field if necessary Policy Qualifiers Syntax and Semantics CAs may use the Policy qualifiers if necessary Processing Semantics for the Critical Certificate Policies Extension No stipulation. 7.2 CRL Profiles CAs shall specify in the CPS or the relevant operating procedures the detailed contents of the CRL they issue Version Number(s) The CRL issued by CAs shall conform to the X.509 V2 format CRL and CRL Entry Extensions CAs shall specify in the CPS or the relevant operating procedures the format of the CRL extension field, if applicable. 7.3 OCSP Profiles CAs digitally sign the response message when provide OCSP service. 58

59 7.3.1 Version Number(s) No stipulation Online Certificate Status Protocol Expansion Field No stipulation. 59

60 8. Compliance Audits and Other Assessments 8.1 Frequency and Circumstances of Assessment The RCA shall conduct an internal audit and an external audit at least once a year. Other CAs shall specify the audit frequency in the CPS. 8.2 Identity/Qualifications of Assessor CA auditors shall at least be familiar with the CPS and this CP, as well as the audit criteria conforming to the audit. 8.3 Assessor's Relationship to Assessed Entity CA auditors shall audit the audited in independent, unimpaired and objective attitude. 8.4 Topics Covered by Assessment A CA audit shall include at least the following items: the conformance of the CPS to this CP the conformance to the CPS of the CA s certificate management. 8.5 Actions Taken as a Result of Deficiency When detecting nonconformities to the CPS, auditors shall itemize the defects by severity detected in the CA audit and notify the auditing and audited units of the audit results. The audited unit shall propose and implement the corrective and preventive actions for the detected defects. The results of improvements shall be followed up. 8.6 Communications of Results The audit results of all CAs shall be submitted to the PMA. 60

61 9. Other Businesses and Legal Matters 9.1 Fees Certificate Issuance or Renewal Fees CAs shall specify them in the CPS Certificate Access Fees CAs shall specify them in the CPS Revocation or Status Information Access Fees CAs shall specify them in the CPS Fees for Other Services CAs shall specify them in the CPS Refund Policy CAs shall specify this in the CPS. 9.2 Financial Responsibility Insurance Coverage CAs shall specify this in the CPS Other Assets No stipulation. 61

62 9.2.3 Insurance or Warranty Coverage for End-Entities CAs shall specify this in the CPS. 9.3 Confidentiality of Business Information Scope Types of Confidential Information CAs shall specify this in the CPS and implement according to the relevant laws and regulations Information Not Within the Scope of Confidential Information CAs shall specify this in the CPS and implement according to the relevant laws and regulations Responsibility to Protect Confidential Information CAs shall specify this in the CPS and implement according to the relevant laws and regulations. 9.4 Privacy of Personal Information Privacy Plan CAs shall operate according to the Computer-Processed Personal Data Protection Act or the relevant regulations of other government agencies. CAs shall also follow the Guidelines on the Protection of Privacy and Transborder Flows of Personal Data announced by the Organization for Economic Co-operation and Development (OECD) in transnational cooperation Information Treated as Private CAs shall specify in the CPS or the Privacy Protection Policy the types of personal privacy information to be kept confidential. 62

63 9.4.3 Information Not Deemed Private CAs shall specify in the CPS the types of information that can be disclosed, such as subscriber certificate, certificate revocation and suspension information, and CPS. Information that will be disclosed in other business shall also be specified in the CPS Responsibility to Protect Private Information CAs shall specify this in the CPS and implement according to the relevant laws and regulations Notice and Consent to Use Private Information CAs shall specify this in the CPS and implement according to the relevant laws and regulations Disclosure Pursuant to Judicial or Administrative Process CAs shall specify in the CPS the types of protected information to be disclosed as a result of an executive order or judicial request Other Information Disclosure Circumstances CAs shall specify in the CPS the types of protected information to be disclosed at the subscriber s request in accordance with the relevant laws and regulations. 9.5 Intellectual Property Right The intellectual property right of this CP is owned by the TWCA Inc. 9.6 Representations and Warranties CA Representations and Warranties To establish the CPS according to this CP. To publish the CPS and ensure that all operations and services conform to the CPS. To issue and publish certificates and keep appropriate certification information. To revoke the certificate of subscribers breaching their obligations. 63

64 To issue and publish the CRL. To provide the repository services as described in section RA Representations and Warranties To carry out subscriber registration according to this CP and the CPS of CAs. To carry out subscriber registration according to the security requirements specified in this CP and the CPS of CAs. To accept certificate application request information and keep certification information valid for verifying the correctness of certificate application request information. To ensure that subscribers understand and agree to the subscriber obligations during the subscriber registration Subscriber Representations and Warranties To provide detailed and correct identity certifications and data when registering at the RA. To reliably, properly and securely protect the private key according to this CP and the CPS of CAs. To understand and agree to the terms governing the acceptance and use of certificates specified in this CP and the CPS of CAs and to use the certificate after accepting and agree to such terms. To report to the RA according to the CPS of CAs when there are doubts about the fraud, exposure and loss of the private key corresponding to the certificate. To follow the scope and restrictions specified in this CP and the CPS of CAs for the certificate and its corresponding private key Relying Party Representations and Warranties Relying party shall examine the certificate according to the relevant rules specified in the CPS of respective CAs by creating the certificate trusted path and authenticating the certificate as a reference to determine if it is to trust the certificate Representations and Warranties of Other Participants No stipulation. 9.7 Disclaimers of Warranties CAs shall specify them in the CPS. 64

65 9.8 Limitations of Liability CAs shall specify them in the CPS. 9.9 Indemnities CAs shall specify in the CPS the liability of CAs, RAs, subscribers and trustees according to the relevant terms in the Electronic Signature Act Term and Termination Term This CP shall be effective immediately after it is approved by the PMA Termination The termination of this CP shall be determined by the PMA Effect of Termination and Survival After the termination of this CP, its effect shall continue until the expiration or revocation of the last certificate issued under this CP Individual Notices and Communications with Participants The PMA shall establish contact channels with CAs under this PKI, including, but not limited to, phone, fax and/or Amendments 65

66 Procedures for Amendment The PMA of the TWCA shall be the supervisor of this CP. This CP shall be reviewed at least once a year. CAs using this CP shall review their CPS at least once a year. When this CP shall be amended as a result of changes in the regulatory requirements and/or updates of international standards, CAs using this CP shall also update their CPS correspondingly. Amendments made to this CP shall be approved by the PMA of the TWCA Notification Mechanism and Period When there are suggestions for updating this policy, please send or such suggestions to the contact window described in section for the PMA to review Circumstances Under Which OID Must be Changed The changes of OIDs in this CPS shall be approved by the PMA of the TWCA Dispute Resolution Provisions Disputes arising from or in connection with the use of this CP shall be settled in due faith by both parties through negotiations for a reasonable resolution. CAs shall specify in the CPS the procedures for settling disputes arising from or in connection with the use of certificates Governing Law The contents of this CP and the relevant CA businesses shall be implemented and interpreted in accordance with the relevant laws and regulations of the competent authorities and the law of the Republic of China. 66

67 9.15 Compliance with Applicable Law CAs shall specify in the CPS the applicable laws and regulations Miscellaneous Provisions Entire Agreement No stipulation Assignment No stipulation Severability Where terms and conditions in this CP shall be modified as a result of inapplicability, the rest of the terms and conditions shall remain effective and unaffected by the inapplicable terms and conditions until the updated version of the CP is completed and published. The amendment of CP is described in section Enforcement (Attorney's Fees and Waiver of Rights) No stipulation Force Majeure Where the certificates are damaged as a result of Force Majeure or events beyond the reasonable control of CAs (e.g. wars or earthquakes), the CA issuing the certificate shall be free from any liability Other Provisions No stipulation. 67

68 (1) Internet Appendix 1: Glossary It refers to the interconnection of various computer networks using a standard protocol for information interchange. (2) (Electronic) Message It refers to the record valid for expressing the intent of a text, voice, image, symbol or other data generated electronically, magnetically or with any means that cannot be directly perceived by the human senses but for electronic processing. (3) Electronic Signature It refers to a data message presented in an electronic format attaching to an electronic document that can identify and validate the identity of the person signed the electronic document; and the message generated by the signed person with digital, voice, fingerprint or other biometrical or optical technology attaching to the electronic message containing the same effect of a signature for identifying and validating the identity of the signed person and identifying the integrity of the signed message. (4) Encrypt/Encipher It refers to the enciphering of electronic documents using mathematical algorithms or other means to ensure data transmission security. (5) Decrypt/Decipher It refers to the reduction of an encrypted or enciphered message that is unable to identify or interpret by humans with relevant mathematical algorithms or other means into a message that can be identified and interpreted by humans. (6) Digital Signature A digital signature is a kind of electronic signature. It refers to a data message that can identify the authenticity of the signed person and his electronic document with corresponding public key can verify this encrypted digital message. A digital signature uses the asymmetric cryptosystem and hash function to compress a digital message of a particular size before encrypting with the private key of the signed person. 68

69 (7) Private Key It refers to a set of matching digital data that kept by the signed person for generating and verifying a digital signature. Apart from generating the digital signature, these digital data can be used to decrypt electronic messages. (8) Public Key In the digital signature using asymmetric cryptosystem, it refers to a set of matching public digital data for generating and verifying a digital signature. It can be used to verify the correctness of data in messages signed by the signed person, and can encrypt delivery messages when running the message privacy function. (9) <Public Key>Certification or Certificate It refers to a computer-based digital record issued by the CA containing the registration identifier of the applicant, the public key, the validity of the public key, the registration identifier and signature of the CA, and other identifying information to validate the identity of the signed person and to prove his possession of the paired public and private keys. (10) Certification Authority or Certificates Authority (CA) It refers to the authority providing digital signature generation and electronic certification services; i.e. it is an authority examining the correctness of the identity data of the applicant and his connection and legitimacy with the public and private keys to be verified in an unimpaired and objective position in order to issue the public key certificate. (11) Certification Practice Statement (CPS) It refers to the operating and application procedures for the CA to offer certificate issue, revocation and enquiry services to subscribers. The CPS includes the public key architecture and security mechanism and operating specifications and procedures of certification, the security mechanisms of CA hardware and software implementation, responsibility and authority management, and the relevant rules. (12) Asymmetric Cryptosystem It refers to a computer-based mathematical algorithm for generating and using an arithmetically correlated secure key pair. The private key generated can be used as the 69

70 message signature, and the corresponding public key can verify the signed message. The public key can also encrypt a message, and the corresponding private key can decrypt the message encrypted with the public key. (13) Hash Function It is an algorithm that can concert a long message (containing many bytes) into a fixed size message. The output of the same message after compression function computing must be identical, and it is absolutely impossible to reduce the input message from the output message. (14) Issue a Certificate (Electronic Certification) It refers to the public key certificate or other certificates issued by the certification center (CA) after reviewing the qualification and relevant documents of the public key certificate applicant and verifying the matching relationship between the public and private keys according to the CPS. 70

71 Appendix 2: Acronyms and Abbreviations CA CC Certification Authority Common Criteria CCITSE Common Criteria for Information Technology Security Evaluation CP CPS CRL DN EAL FIPS Certificate Policy Certification Practice Statement Certificate Revocation List Distinguished Name Evaluation Assurance Level Federal Information Processing Standard ISO/IEC the International Organization for Standardization, The International Electrotechnical Commission ITSEC LDAP NB OCSP OID OECD PAA PMA PKCS PKI RA RCA RSA Information Technology Security Evaluation Criteria Lightweight Directory Access Protocol Network Banking Online Certificate Status Protocol Object Identifier Organization for Economic Co-operation and Development Pan-Asian e-commence Alliance Policy Management Authority Public Key Cryptography Standard Public Key Infrastructure Registration Authority Root Certification Authority Rivest, Shamir, Adleman (encryption algorithm) TCSEC Trusted Computer System Evaluation Criteria 71

72 URL Universal Resources Location 72