Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

More documents

Recommendations

Info

6.1.7 Key Usage Purposes (as per X.509 v3 key usage field) The use of a specific key is determined by the key usage extension in the X.509 certificate. In particular, certificates to be used for digital signatures (including authentication) shall set the digitalsignature and nonrepudiation bits. Certificates to be used for encryption shall set the keyEncipherment bit. Certificates to be used for key agreement shall set the keyAgreement bit. CA certificates shall set cRLSign and CertSign bits. Public keys that are bound into certificates shall be certified for use in signing or encrypting, but not both. This restriction is not intended to prohibit use of protocols (like the Secure Sockets Layer) that provide authenticated connections using key management certificates and require setting both digitalsignature and keyEncipherment bits to be set. 62 7/25/2011
6.2 Private Key Protection and Cryptographic Module Engineering Controls 6.2.1 Cryptographic Module Standards and Controls The relevant standard for cryptographic modules is FIPS PUB 140-2, Security Requirements for Cryptographic Modules. The RPMA may determine that other comparable validation, certification, or verification standards are sufficient. These standards shall be published by the RPMA. Cryptographic modules shall be validated to the FIPS 140-2 level identified in this section, or validated, certified, or verified to requirements published by the RPMA. Additionally, the RPMA reserves the right to review technical documentation associated with any cryptographic modules under consideration for use by the CAs. The table in Section 6.1.1 summarizes the minimum requirements for cryptographic modules; higher levels may be used. In addition, medium-hardware and high-hardware assurance token shall not output private keys in plaintext form. 6.2.2 Private Key Multi-Person Control Use of a CA private signing key shall require action by at least two persons. 6.2.3 Private Key Escrow Under no circumstances shall the signature keys be escrowed by a third party. The end entity private keys used solely for decryption shall be escrowed prior to the generation of the corresponding certificates. For some purposes (such as data recovery) it shall be necessary to provide key retrieval for the private component of the encryption certificate key pair. To facilitate this, the PKI shall provide a key escrow capability. The method, procedures and controls which shall apply to the storage, request for, extraction and/or retrieval, delivery, protection and destruction of the requested copy of an escrowed key shall be described in the Raytheon Key Recovery Practice Statement (KRPS) which shall become an integral component of this CP. 6.2.4 Private Key Backup 6.2.4.1 Backup of CA Private Signature Key The CA private signature keys shall be backed up under the same multi-person control as the operational signature key. A single backup copy of the signature key shall be stored at or near the CA location. A second backup copy shall be kept at the CA backup location. Procedures for CA private signature key backup shall be included in the appropriate CPS and shall meet the multiparty control requirement of Section 5.2.2. 6.2.4.2 Backup of Subscriber Private Signature Key Subscriber private signature keys whose corresponding public key is contained in a certificate asserting the medium-software may be backed up or copied, but must be held in the Subscriber’s control. Subscriber private signature keys whose corresponding public key is contained in a certificate asserting the medium-hardware and/or high-hardware may not be backed up or copied. 63 7/25/2011
Page 1 and 2:
Raytheon Company Public Key Infrast
Page 3 and 4:
Table of Contents 1 INTRODUCTION ..
Page 5 and 6:
4.6.7 Notification of Certificate I
Page 7 and 8:
5.4.8 Vulnerability Assessments ...
Page 9 and 10:
9 OTHER BUSINESS AND LEGAL MATTERS
Page 11 and 12: 1 INTRODUCTION This Certificate Pol
Page 13 and 14: 1.1.3 Scope The following diagram r
Page 15 and 16: 1. The CAs asserting id-raytheon-SH
Page 17 and 18: approval of the PMA. The ROA activi
Page 19 and 20: � Raytheon employees and eligible
Page 21 and 22: 1.5 Policy Administration 1.5.1 Org
Page 23 and 24: 3.1 Naming 3 IDENTIFICATION & AUTHE
Page 25 and 26: establishing how the applicant is k
Page 27 and 28: 4. The Identity Verifier shall reco
Page 29 and 30: 3.3.1 Identification and Authentica
Page 31 and 32: For subscriber certificates, the pr
Page 33 and 34: 4.3.1 CA Actions during Certificate
Page 35 and 36: 4.7.4 Notification of New Certifica
Page 37 and 38: Any CA may unilaterally revoke anot
Page 39 and 40: 4.9.8 Maximum Latency for CRLs The
Page 41 and 42: 4.12.2 Session Key Encapsulation an
Page 43 and 44: depart shall initial a sign-out she
Page 45 and 46: � Performing or overseeing intern
Page 47 and 48: � Be trustworthy; � Have no oth
Page 49 and 50: administrative documents (e.g., Adm
Page 51 and 52: REVOCATION PROFILE MANAGEMENT Audit
Page 53 and 54: It is acceptable for the system to
Page 55 and 56: 5.6 Key Changeover A CA uses a sign
Page 57 and 58: If a RA signature keys are compromi
Page 59 and 60: show that appropriate role separati
Page 61: Hashing: Cryptographic Function Has
Page 65 and 66: 6.3 Other Aspects of Key Management
Page 67 and 68: � All hardware must be shipped or
Page 69 and 70: 7 CERTIFICATE, CRL AND OCSP PROFILE
Page 71 and 72: When multiple values exist for an a
Page 73 and 74: 8 COMPLIANCE AUDIT AND OTHER ASSESS
Page 75 and 76: 9.1 Fees 9 OTHER BUSINESS AND LEGAL
Page 77 and 78: � There are no material misrepres
Page 79 and 80: � Ensure that certificate and rev
Page 81 and 82: as a termination of this CP unless
Page 83 and 84: enforce the agreement to arbitrate,
Page 85 and 86: 10 CERTIFICATE, CRL, AND OCSP FORMA
Page 87 and 88: Field Value Policy Mapping For SHA-
Page 89 and 90: 10.3 Raytheon Root CA Certificate (
Page 91 and 92: 91 7/25/2011
Page 93 and 94: 10.6 Medium Assurance Signing CA Ce
Page 95 and 96: Field Value Entrust Version Info c=
Page 97 and 98: 10.9 Medium Assurance Code Signing
Page 99 and 100: Field Value Entrust Version Info En
Page 101 and 102: 10.12 Medium Assurance Domain Contr
Page 103 and 104: 10.13 Medium Assurance Role Signatu
Page 105 and 106: 10.15 OCSP Responder Certificate Th
Page 107 and 108: 10.17 Medium Assurance CA CRL Forma
Page 109 and 110: 11 PKI REPOSITORY INTEROPERABILITY
Page 111 and 112: BIBLIOGRAPHY The following document
Page 113 and 114:
HTTP Hypertext Transfer Protocol IA
Page 115 and 116:
13 GLOSSARY Access Ability to make
Page 117 and 118:
Client (application) A system entit
Page 119 and 120:
Non-Repudiation Assurance that the
Page 121 and 122:
other CA. (See superior CA). Subscr
show all

Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?