@@ -1026,12 +1026,12 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
- REFERENCE: REQ-PKI-INT-06
- REQUIREMENT: The product shall create certificate signature only by means of a Secure Cryptographic Device (SCD).
- 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. It covers key tampering and disclosure threats: T_GEN01 to T_GEN08, T.Stored_Certificates_Tampering.
- APPLICABILITY: UC2, UC3, UC4, UC5
- 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 and UC5
- REFERENCE: REQ-PKI-INT-07
- REQUIREMENT: The cryptographic mechanisms used to create certificate signature shall be as stated in Annex K.
- RATIONALE: TODO
- REQUIREMENT: The cryptographic mechanisms used to create certificate signatures shall be as stated in Annex K.
- RATIONALE: The use of recognized and validated cryptographic algorithms is mandatory for a PKI and thus a PKI product to ensure trust. Known weak or insufficiently validated algorithms are not allowed.
- APPLICABILITY: All use cases.
@@ -1045,7 +1045,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
- REQUIREMENT: The product shall only maintain configuration data sufficient to connect to other elements of the PKI system that the product serves.
- RATIONALE: XXX
- NOTE:XXX
- APPLICABILITY: XXXX
- APPLICABILITY: UC1, UC2, UC3, and UC5
- REFERENCE: REQ-PKI-DM-002
- REQUIREMENT: The product shall only maintain and process user data necessary for certificate management (e.g. certificate requests, updates)
@@ -1566,6 +1566,32 @@ The assessment criteria for each security requirements are described in a struct
- The documentation of private and symmetric keys profiles and how these keys are created.
REFERENCE: ACC_PKI_DM_004 (TODO numbering)
- OBJECTIVE:
- Verify that the product establishes and maintains a secure and correctly configured communication link with the SCD, and that the SCD interface is properly configured and called.
- PREPARATION:
- Document the following:
- The communication protocols (e.g., TLS, IPsec) and their configurations used to connect to the SCD.
- The SCD interface specifications, including supported commands, data formats, and authentication mechanisms.
- The expected behavior of the product when interacting with the SCD (e.g., error handling, retries, timeouts).
- ACTIVITIES:
- Verify that the communication link with the SCD is encrypted and authenticated according to the documented protocols and configurations.
- Verify that the product correctly configures the SCD interface (e.g., parameters, credentials, or certificates).
- Verify that all calls to the SCD interface use the correct commands, data formats, and authentication mechanisms as specified.
- Test edge cases, such as network interruptions or invalid responses, to ensure robust handling.
- VERDICT:
- SUCCESS: All communication links are secure, and the SCD interface is correctly configured and called.
- FAIL: Identification of insecure communication links, misconfigured SCD interfaces, or incorrect calls to the SCD interface.
- EVIDENCE:
- Documentation of the communication protocols, configurations, and SCD interface specifications.
- Logs or test results demonstrating secure communication and correct SCD interface calls.
- Evidence of error handling and robustness during edge case testing.
- REFERENCE: ACC_PKI_DM_004
- OBJECTIVE: Verify the product does not persistently store private or symmetric keys in plaintext form.
