@@ -1174,8 +1174,19 @@ 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.
