Loading EN-304-624.md +68 −3 Original line number Diff line number Diff line Loading @@ -1797,7 +1797,7 @@ Validity of access control requirement are covered by section 6.5: - REFERENCE: ACC-PKI-CON-03 - OBJECTIVE: Verify that all transmissions of personal or sensitive data are protected using state-of-the-art cryptographic mechanisms in accordance with Annex K. - Verify that all transmissions of personal or sensitive data are protected using state-of-the-art cryptographic mechanisms in accordance with Annex K. - PREPARATION: - Data flow diagrams or interface specifications. - Data classification documentation identifying personal and sensitive data. Loading @@ -1807,8 +1807,7 @@ Validity of access control requirement are covered by section 6.5: - ACTIVITIES: - Identify all interfaces transmitting personal or sensitive data. - Verify that transmitted data is protected by cryptographic mechanisms compliant with Annex K. - Capture network traffic during data transmission. - Verify that sensitive information is not transmitted in plaintext. - Capture network traffic during data transmission. Verify that sensitive information is not transmitted in plaintext. - VERDICT: - SUCCESS: - All identified sensitive data transmissions are cryptographically protected. Loading @@ -1826,6 +1825,72 @@ Validity of access control requirement are covered by section 6.5: - Protocol inspection reports. - Test execution records. ### 6.6.2 CON - Secure storage and communications - REFERENCE: ACC-PKI-CON-04 - OBJECTIVE: - Verify that communications with the SCD or KMS are securely established, maintained, and use only authorized and correctly implemented interfaces. - PREPARATION: - SCD/KMS integration documentation or API documentation. - PKI product interface specifications and API documentation. - Cryptographic configuration documentation. - Running product with access to an operational SCD or KMS. - Network monitoring tools. - ACTIVITIES: - Review the architecture and communication methods used with the SCD or KMS. - Verify that communications are protected using authenticated and encrypted channels. - Verify that only documented interfaces and APIs are invoked. - Observe key management operations that invoke the SCD or KMS. - Capture network traffic during data transmission and verify that sensitive information is not transmitted in plaintext. - Introduce communication failures or invalid requests and verify proper error handling. - Verify that security-relevant interactions are logged. - VERDICT: - SUCCESS: - Secure authenticated communications with the SCD or KMS are established and maintained. - Only approved interfaces are used. - Communication failures are securely handled. - FAIL: - Communications occur without appropriate protection. - Undocumented or insecure interfaces are used. - Communication failures compromise security functions. - EVIDENCE: - Architecture documentation. - Interface specifications. - Communication configuration files. - Network captures. - API invocation logs. - Audit records. ### 6.6.2 CON - Key management - REFERENCE: ACC-PKI-CON-10 - OBJECTIVE: Verify that exported private or symmetric keys are protected against disclosure using cryptographic mechanisms conforming to Annex K. - PREPARATION: - Determine whether key export functionality exists. - Obtain export procedures and cryptographic documentation. - Prepare test keys and export environments. - ACTIVITIES: - Verify whether key export functionality is supported. - Review mechanisms protecting exported keys. - Export private and symmetric keys using supported procedures. - Verify that exported keys are encrypted using approved algorithms and key management procedures as defined by Annex K assessment requirements. - Attempt to access exported keys without possessing required decryption material. - VERDICT: - SUCCESS: - Exported keys are protected using approved cryptographic mechanisms. - Unauthorized parties cannot recover exported key material. - FAIL: - Keys are exported in plaintext. - Weak or non-approved protection mechanisms are used. - Exported key material can be recovered without authorization. - EVIDENCE: - Export procedures. - Cryptographic configurations. - Exported key files. - Key inspection results. - Test reports. ## 6.7 Integrity Loading Loading
EN-304-624.md +68 −3 Original line number Diff line number Diff line Loading @@ -1797,7 +1797,7 @@ Validity of access control requirement are covered by section 6.5: - REFERENCE: ACC-PKI-CON-03 - OBJECTIVE: Verify that all transmissions of personal or sensitive data are protected using state-of-the-art cryptographic mechanisms in accordance with Annex K. - Verify that all transmissions of personal or sensitive data are protected using state-of-the-art cryptographic mechanisms in accordance with Annex K. - PREPARATION: - Data flow diagrams or interface specifications. - Data classification documentation identifying personal and sensitive data. Loading @@ -1807,8 +1807,7 @@ Validity of access control requirement are covered by section 6.5: - ACTIVITIES: - Identify all interfaces transmitting personal or sensitive data. - Verify that transmitted data is protected by cryptographic mechanisms compliant with Annex K. - Capture network traffic during data transmission. - Verify that sensitive information is not transmitted in plaintext. - Capture network traffic during data transmission. Verify that sensitive information is not transmitted in plaintext. - VERDICT: - SUCCESS: - All identified sensitive data transmissions are cryptographically protected. Loading @@ -1826,6 +1825,72 @@ Validity of access control requirement are covered by section 6.5: - Protocol inspection reports. - Test execution records. ### 6.6.2 CON - Secure storage and communications - REFERENCE: ACC-PKI-CON-04 - OBJECTIVE: - Verify that communications with the SCD or KMS are securely established, maintained, and use only authorized and correctly implemented interfaces. - PREPARATION: - SCD/KMS integration documentation or API documentation. - PKI product interface specifications and API documentation. - Cryptographic configuration documentation. - Running product with access to an operational SCD or KMS. - Network monitoring tools. - ACTIVITIES: - Review the architecture and communication methods used with the SCD or KMS. - Verify that communications are protected using authenticated and encrypted channels. - Verify that only documented interfaces and APIs are invoked. - Observe key management operations that invoke the SCD or KMS. - Capture network traffic during data transmission and verify that sensitive information is not transmitted in plaintext. - Introduce communication failures or invalid requests and verify proper error handling. - Verify that security-relevant interactions are logged. - VERDICT: - SUCCESS: - Secure authenticated communications with the SCD or KMS are established and maintained. - Only approved interfaces are used. - Communication failures are securely handled. - FAIL: - Communications occur without appropriate protection. - Undocumented or insecure interfaces are used. - Communication failures compromise security functions. - EVIDENCE: - Architecture documentation. - Interface specifications. - Communication configuration files. - Network captures. - API invocation logs. - Audit records. ### 6.6.2 CON - Key management - REFERENCE: ACC-PKI-CON-10 - OBJECTIVE: Verify that exported private or symmetric keys are protected against disclosure using cryptographic mechanisms conforming to Annex K. - PREPARATION: - Determine whether key export functionality exists. - Obtain export procedures and cryptographic documentation. - Prepare test keys and export environments. - ACTIVITIES: - Verify whether key export functionality is supported. - Review mechanisms protecting exported keys. - Export private and symmetric keys using supported procedures. - Verify that exported keys are encrypted using approved algorithms and key management procedures as defined by Annex K assessment requirements. - Attempt to access exported keys without possessing required decryption material. - VERDICT: - SUCCESS: - Exported keys are protected using approved cryptographic mechanisms. - Unauthorized parties cannot recover exported key material. - FAIL: - Keys are exported in plaintext. - Weak or non-approved protection mechanisms are used. - Exported key material can be recovered without authorization. - EVIDENCE: - Export procedures. - Cryptographic configurations. - Exported key files. - Key inspection results. - Test reports. ## 6.7 Integrity Loading
