-**[REQ-TECH-0]** The product shall not connect to unknown RDPS services.
-**[REQ-TECH-1]** The product shall implement [5.2.4 State-of-the-art cryptographic libraries] to allow the protection of the requirements of the foreseeable use.
-**[REQ-TECH-2]** When privileged information is transferred or accessed, a secure channel shall be used in transport [5.2.1 Secure channel].
-**[REQ-TECH-3]** All endpoints in a secure channel shall cryptographically verify others through mutual auhentication.
For medium risk:
-**[REQ-TECH-4]** The product shall be designed in a way that [5.2.2 Cryptographic key intialisation and rotation] is made possilbe.
@@ -159,6 +158,7 @@ For high risk:
A **secure channel** referred in [REQ-TECH-2] and used in transportation is a cryptographically protected communication channel, that may be implemented with TLS.
-**[REQ-CRYPTO-0]** The product shall ensure that the channel uses appropriate cryptographic functions and configuration according to the requirements of the foreseeable use.
-**[REQ-TECH-3]** All endpoints in a secure channel shall cryptographically verify others through mutual auhentication.
-**[REQ-CRYPTO-1]** The product shall ensure that the channel can not be impaired by downgrading it [i.10].
-**[REQ-CRYPTO-2]** The product shall implement secure channel as per Annex K.
-**[REQ-CRYPTO-3]** The product shall protect the data transfer, the confidentiality and the integrity of the data according to the requirements of the foreseeable use.
