Loading EN-304-621.md +9 −9 Original line number Diff line number Diff line Loading @@ -3452,7 +3452,7 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re ### 6.12.1 MAS_TECH-1 **Objective:** How the product communicates is understood and documented. **Objective:** The product user knows entirely all external product interfaces. **Preparation:** Loading @@ -3460,14 +3460,14 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re **Activities:** 1. Study the technical documentation. 1. Study the listed documented communication endpoints. 1. List all the interfaces the product is listening to. 1. Cross-reference the open interfaces to the documentation. 1. Study the technical documentation; 2. Study the listed documented communication endpoints; 3. List all the interfaces the product is listening to or writing to; 4. Cross-reference the open interfaces to the documentation. **Verdict:** 1. Pass, if all interfaces used for communication are documented. 1. Pass, if all interfaces used for communication are documented; 2. Fail otherwise. **Supporting Evidence:** Loading @@ -3479,7 +3479,7 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re ### 6.12.2 MAS_TECH-2 **Objective:** How the product communicates is understood and documented. **Objective:** How the product communicates with RDPS is documented and made known to the product user. **Preparation:** Loading @@ -3489,8 +3489,8 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re 1. Study the technical documentation. 2. Study the listed dependencies to RDPS systems. 3. Capture all network traffic metadata that is communicating outside of the product deployment boundaries. 4. Tricker all possible actions that might result in a communication with RDPS services, like update, licensing verifications, etc. 3. Capture all network traffic metadata that occurs by the product RDPS communication. 4. Trigger all possible actions that might result in a communication with RDPS services, like update, licensing verifications, etc. 5. Identify all systems with the help of the technical documentation. **Verdict:** Loading Loading
EN-304-621.md +9 −9 Original line number Diff line number Diff line Loading @@ -3452,7 +3452,7 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re ### 6.12.1 MAS_TECH-1 **Objective:** How the product communicates is understood and documented. **Objective:** The product user knows entirely all external product interfaces. **Preparation:** Loading @@ -3460,14 +3460,14 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re **Activities:** 1. Study the technical documentation. 1. Study the listed documented communication endpoints. 1. List all the interfaces the product is listening to. 1. Cross-reference the open interfaces to the documentation. 1. Study the technical documentation; 2. Study the listed documented communication endpoints; 3. List all the interfaces the product is listening to or writing to; 4. Cross-reference the open interfaces to the documentation. **Verdict:** 1. Pass, if all interfaces used for communication are documented. 1. Pass, if all interfaces used for communication are documented; 2. Fail otherwise. **Supporting Evidence:** Loading @@ -3479,7 +3479,7 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re ### 6.12.2 MAS_TECH-2 **Objective:** How the product communicates is understood and documented. **Objective:** How the product communicates with RDPS is documented and made known to the product user. **Preparation:** Loading @@ -3489,8 +3489,8 @@ Assessments are defined in [Annex K](#annex-k-normative-generic-cryptographic-re 1. Study the technical documentation. 2. Study the listed dependencies to RDPS systems. 3. Capture all network traffic metadata that is communicating outside of the product deployment boundaries. 4. Tricker all possible actions that might result in a communication with RDPS services, like update, licensing verifications, etc. 3. Capture all network traffic metadata that occurs by the product RDPS communication. 4. Trigger all possible actions that might result in a communication with RDPS services, like update, licensing verifications, etc. 5. Identify all systems with the help of the technical documentation. **Verdict:** Loading