The product may provide security functions that the operational environment may make use of to provide integrity protection for a product that integrates this product as a component. But products in the scope of the present document are not required to provide integrity protection independently of their operational environment to protect their own cybersecurity. Products may choose to implement integrity protection of data stored or transmitted for other reasons, such as to satisfy regulatory requirements by preventing an authorized user on the host system from installing non-conforming firmware.
## 5.9 Data minimisation
### 5.9.1 Overview
This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 Part 1 (2) (g).
### 5.9.2 REQ-DM-01 (MI-DJST): Data minimisation
#### 5.9.2.1 Requirement
The product shall minimize the data processing by the product.
#### 5.9.2.2 Applicability
TODO
### 5.2.4 ER-MINI: Minimize impact on other devices and services
#### 5.2.4.1 Cybersecurity requirement
@@ -1043,43 +1059,6 @@ The product shall implement methods of detecting and mitigating denial of servic
See clause 5.3 for which mitigations are necessary for which security profiles and Annex C.4 for the rationale.
### 5.2.12 ER-DMIN: Data Minimization
#### 5.2.12.1 Cybersecurity requirement
The product shall minimize the data processed.
#### 5.2.12.2 MI-DJST: Document and justify processed data
The product operation can require storing information relevant for the protocol implementation like out-of-order TCP packets, that are later recombined for the receiver as a continuos stream of information.
This can be often considered to be part of the core functionality of the product.
Outside of the core functionality, the default set size of data that needs to be collected from the operation is zero. Therefore:
All sources of data processed by the product in its secure-by-default configuration shall be documented. All sources of data processed shall have a documented rationale for why its processing is necessary for the functioning of the product in its secure-by-default configuration.
> Example MI-DJST-1: The product supports NetFlow protocol and collects information from traffic going through the interface.
> Example MI-DJST-2: The product is a managed interface and supports a variety of different collectable metrics which are by default off, but the collection and reporting can be activated remotely.
> Example MI-DJST-3: The product is purpose-built for high level application co-operation and participates on the content delivery network function by storing most frequent replies in the network interface volatile memory. The replies are served directly from the memory without relying the request forward. Key information and metrics are collected and relied for the application.
* Reference: ER-DMIN
* Objective: Minimize data processed
* Preparation: List all potential sources of data for the product. For each source of data, identify a method to detect whether the product is processing data from that source.
* Activities: Using the list of sources of data, and the method to detect whether the product is processing data from that source, list all sources of data processed. Compare to the documented list.
* Verdict: All sources of processed data are documented, including rationale => PASS, otherwise => FAIL
* Evidence: List of sources of data, documentation of each source of data, list of sources of data processed, connection between each discovered source of processed data to its documentation
#### 5.2.12.3 Mapping of mitigations to risk factors and security profiles
See clause 5.3 for which mitigations are necessary for which security profiles and Annex C.4 for the rationale.
### 5.2.13 ER-AVAI: Availability
#### 5.2.13.1 Cybersecurity requirement
@@ -1985,6 +1964,54 @@ Examples of attempts to modify data without authorization:
* Attempt to write to the memory mapped to the network interface's registers and memory without the necessary memory permissions
* Attempt to write to the file containing the virtual network interface's executable without the necessary file system permissions
## 6.9 Data minimisation
### 6.9.2 REQ-DM-01 (MI-DJST): Minimise data processed
#### 6.9.2.1 Objective
Minimise data processed by the product.
#### 6.9.2.2 Preparation
Determine all data processing done by the product, using as necessary:
* product technical documentation
* product functions
* product interfaces
* data transmitted by the product
* data stored by the product
* product binaries
* source code
* other sources of product information
#### 6.9.2.3 Activities
For each type of data processing identified, analyse its relevance and necessity for the intended purpose of the product.
#### 6.9.2.4 Verdict
PASS if, for every type of data processing identified, the data processed is determined to be relevant and limited to what is necessary for the intended purpose of the product.
Otherwise FAIL
#### 6.9.2.5 Evidence
* Product information used to determine what data processing the product does
* Sufficiency analyses of relevance, limitation, and necessity of data for product purpose
#### 6.9.2.6 Guidance
The product operation can require storing information relevant for the protocol implementation like out-of-order TCP packets, that are later recombined for the receiver as a continuous stream of information. This can be often considered to be part of the core functionality of the product.
Outside of the core functionality, the default set size of data that needs to be collected from the operation is zero. Therefore:
> Example DM-01-1: The product supports NetFlow protocol and collects information from traffic going through the interface.
> Example DM-01-2: The product is a managed interface and supports a variety of different collectable metrics which are by default off, but the collection and reporting can be activated remotely.
> Example DM-01-3: The product is purpose-built for high level application co-operation and participates on the content delivery network function by storing most frequent replies in the network interface volatile memory. The replies are served directly from the memory without relying the request forward. Key information and metrics are collected and relied for the application.
### 6.2.13.4 MI-FDRP assessment
**[MI-FDRP]** Verify the product performs ordered validity checks on incoming packets and drops invalid packets before further processing.
