@@ -936,7 +936,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
- REQUIREMENT: If the product sends data intended/labelled as personal or sensitive to another entity the product shall ensure that such data is protected from eavesdropping in a cryptographically protected way. The cryptographic mechanisms shall conform to the general state of the art as defined in Annex K.
- RATIONALE: Analysis has to be performed and justified by the developper to ensure that the product protects personal and sensitive data. This requires to define what data are considered personnal or sensitive.
- NOTE: This includes any remote administration.
- APPLICABILITY: XXXX
- APPLICABILITY: UC1, UC2, UC3, UC5
- REFERENCE: REQ-PKI-CON-05
- REQUIREMENT: A public key certificate request containing explicit personal data shall be protected in integrity and confidentiality by implementing cryptographic mechanisms as defined in Annex K.
@@ -1043,7 +1043,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
### 5.8.2 Secret management
- REFERENCE: REQ-PKI-DM-03
- REQUIREMENT: The product shall only create keys by means of a Secure Cryptographic Device (SCD) or remote Key Management System appropriate for this use.
- REQUIREMENT: The product shall only create keys by means of a Secure Cryptographic Device (SCD) or remote Key Management System providing cryptographic mechanisms conform to the general state of the art as defined in Annex K.
- RATIONALE: To ensure trust the product software must rely on secure and valid key creation and management systems accessible only to authorised users provided by hardware security devices.
- APPLICABILITY: UC2, UC3, UC4, UC5
@@ -1642,13 +1642,15 @@ REFERENCE: ACC_PKI_DM_04
- REFERENCE: ACC_PKI_DM_07
- OBJECTIVE: Verify the product zeroizes secrets in plaintext form.
- OBJECTIVE: Verify that the product perform zeroization of secrets when no longer used.
- PREPARATION: Document secrets manipulated by the product in plaintext form outside a secure cryptographic device. Access to product source codes.
- PREPARATION:
- Document secrets manipulated by the product in plaintext form outside a secure cryptographic device.
- When possible, access to product source codes.
- ACTIVITIES:
a) For every such secret, verify related source codes systematically perform its secure zeroization after the secret is used;
a) When source code is accessible, for every such secret, verify related source codes systematically perform its secure zeroization after the secret is used;
b) For every zeroization method employed, identify a related secret in memory while it is used, and verify the secret to be irrecoverable in full after zeroization.
