-**[REQ-TECH-2]** When privileged information is transferred or accessed, a secure channel shall be used in transport [5.2.1 Secure channel].
For medium risk:
-**[REQ-TECH-5]** All system components shall be synchronised to the same time that is acceptable for the system accuracy.
* This document does not have medium level requirements in this category.
For high risk:
-**[REQ-TECH-6]** All system time drift corrections shall be recorded as monitoring event.
@@ -883,28 +883,6 @@ Verify that:
1. References to to documentation sections.
### 6.2.0.5 REQ-TECH-5
**Objective:** Prevent errors and innaccuracvy in logging, metrics, and traces, due to unsynchronized component clocks.<br/>
**Preparation:**
1. Have the product initialised and available with the default configuration and required credentials.
**Activities:**
1. Dump all clock from all participating systems and computational nodes.
2. Ensure that the clock deviation is within limits specified in the techinal documentation.
3. Verify that time synchronisation mechanism is in use and functioning already with the default configuration.
**Verdict:**
1. Pass, if the clock deviation is under the specified limit in the technical documentation.
2. Fail otherwise.
**Supporting Evidence:**
1. Log output from the test.
#### 6.2.0.6 REQ-TECH-6
**Objective:** Where multiple monitoring sources all operate they shall have consistent system time where any drift or lack of synchronization shall be accurately documented and notification provided to administrator.<br/>
