| **[RQ-4]** | Deployment of a production distribution exposes only documented interfaces. |
| **[RQ-5]** | Relevant actions are recorded and can not be modified later. |
| **[RQ-6]** | See [5.2.1 Secure channel definition](#521-secure-channel-definition). |
| **[RQ-7]** | See [5.2.2 Cryptographic key intialization and rotation](#522-cryptographic-key-intialization-and-rotation) |
### 5.2.1 Secure channel definition
A **secure channel** referred in [RQ-4] and used in transportation is a cryptographically protected communication channel, that may be implemented with TLS. When TLS is used, manufacturer shall ensure that the channel uses appropriate cryptographic functions and configuration according to the requirements of the forseeable use. Manufacturer shall ensure that the channel can not be impaired by downgrading it [i.10].
@@ -548,13 +555,23 @@ A **secure channel** referred in [RQ-4] and used in transportation is a cryptogr
When TLS is not used to encrypt the traffic in the secure channel, manufacturer shall provide detailed description how the channel is secured in the technical documentation.
The chosen method shall follow the intent in the CRA by protecting the data transfer, and protect the confidentiality and integrity of the data according to the requirements of the forseeable use.
### 5.2.2 Network segmentation
### 5.2.2 Cryptographic key intialization and rotation
Manufacturer shall design and implementd support for on-demand rotation of cryptographic keys.
The technical documentation shall include:
1. instructions on how to intialize trust
1. how to use the trust to accept managed elements to the network
1. how to the established trust to rotate all keys
### 5.2.3 Network segmentation
Network segmentation is encouraged to be used where applicapble. The best practise is to use dedicated network segment for network management traffic.
Management traffic can be configuration updates, encryption keys, software updates, and others alike.
Regardless of what connectivity structure manufacturer implements in the NMS design from [ACC-L-0] to [ACC-L-3], manufacturer shall implement mitigations described in the following section [Risk Mitigations](#53-risk-mitigations).
ZeroTrust routing is also encouraged where applicable.
## 5.3 Risk Mitigations
The following sections describe how technical security requirement in previous [Section 5.2](#52-technical-security-requirements-specifications) are mapped to the risk factors in [Section 4.5 Risk Factors](#45-risk-factors).
