Adding of REQ-PKI-DM-004 on proper use and secure communication with the SCD or KMS

### 5.8.2 Secret management

- REFERENCE: REQ-PKI-DM-003

  - REQUIREMENT: The product shall only create keys by means of a Secure Cryptographic Device (SCD) or remote Key Management System appropriate for this use.

  - 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.

  - 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

- REFERENCE: REQ-PKI-DM-004

  - REQUIREMENT: The product shall be able to establish and maintain a secure and link with the SCD or KMS, and that the SCD or KMS interfaces are properly called.

    - 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

- REFERENCE: REQ-PKI-DM-005

  - 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.

  - RATIONALE: To ensure trust the product 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: All use cases.

    - The documentation of private and symmetric keys profiles and how these keys are created.

REFERENCE: ACC_PKI_DM_004 (TODO numbering)

REFERENCE: ACC_PKI_DM_004 

- 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.

  - Evidence of error handling and robustness during edge case testing.

- REFERENCE: ACC_PKI_DM_004

- REFERENCE: ACC_PKI_DM_005

  - OBJECTIVE: Verify the product does not persistently store private or symmetric keys in plaintext form.

    a) The documentation of private and symmetric keys profiles and how these keys are manipulated.

- REFERENCE: ACC_PKI_DM_005

- REFERENCE: ACC_PKI_DM_006

  - OBJECTIVE: Verify public keys stored within the product outside a secure cryptographic device are protected against undetected modification, and that public keys are not released or used after a detected modification.

    c) the way operations making use of public keys were attempted to be triggered, and the response from the product;

- REFERENCE: ACC_PKI_DM_006

- REFERENCE: ACC_PKI_DM_007

  - OBJECTIVE: Verify the product zeroizes secrets in plaintext form.

    b) the documentation of zeroization methods employed.

- REFERENCE: ACC_PKI_DM_007

- REFERENCE: ACC_PKI_DM_008

  - OBJECTIVE: Verify the product cannot export private or symmetric keys in plaintext form.