@@ -609,7 +609,7 @@ Products with digital elements used as part of a public key cryptography scheme
-**F.ExternalKeyManagement**: Request key suppression, export, or renewal from an external SCD or KMS.
-**F.InternalKeyManagement**: Suppress, export, or renew software keys.
-**F.UserAccountManagement**: Create, modify, assign rights to, and modify the different user accounts.
-**F.PrivateKeyExport**: Private keys, secret keys, or critical data can be encrypted and then exported in the form of an encrypted file.
-**F.PrivateKeyImportExport**: Private keys, secret keys, or critical data can be encrypted and then exported in the form of an encrypted file.
-**F.OfficerCertGenApproval**: Authorized users can approve and execute this issuance when certificates are issued.
-**F.CertificateProfileManagement**: Administration functions to define the format and default values of certificates to be signed.
-**F.PseudonymCertIssuance**: Issue pseudonym certificates derived from long-term certificates. These certificates shall not include user identification data.
@@ -876,7 +876,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
- Registration
- F.OnlineRegService
- F.CertificateDissemination
- F.PrivateKeyExport
- F.PrivateKeyImportExport
- F.OfficerRegistrationApproval
- Certificate generation
@@ -902,7 +902,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
### 5.6.1 CON - General
- REFERENCE: REQ-PKI-CON-01
- REQUIREMENT: The product shall provide capabilities to ensure that the private key generated by the product cannot be removed or copied from the product.
- REQUIREMENT: The product shall provide capabilities to ensure that the private key generated by the product cannot be removed or copied from the product by unauthorized users.
- RATIONALE: Private keys are the root of trust in a PKI. When they are not generated or protected by an external SCD or KMS, this requirement ensures that only the product has access to them, protecting them from export, copying, or disclosure.
- NOTE: Where a device creates a public-private key pair and maintains the related PKC that set (key pair and PKC) can be moved from one physical entity to another within a strictly controlled environment as per use case.
- APPLICABILITY: UC1.
@@ -955,10 +955,10 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
### 5.6.2 CON - Key management
- REFERENCE: REQ-PKI-CON-10
- REQUIREMENT: If the product exports private or symmetric keys it shall use state of the art techniques for guaranteeing its confidentiality as defined in Annex K.
- REQUIREMENT: [CONDITIONAL] If the product exports private or symmetric keys it shall use state of the art techniques for guaranteeing its confidentiality as defined in Annex K.
- RATIONALE: A secret key should not be compromised if its exported form is intercepted.
- EXAMPLES: The exported private or symmetric key can be encrypted such that only its designated recipient can decrypt it.
- APPLICABILITY: All use cases
- APPLICABILITY: All use cases where key export is supported.
- REFERENCE: REQ-PKI-CON-11
- REQUIREMENT: Secret keys shall not be stored persistently in plaintext form. They shall be stored within a secure cryptographic device or encrypted using approved algorithms as defined in Annex K using independently managed keys. They may only be accessed in plaintext form temporarily for a single operation or batch of operations.
