@@ -1494,13 +1494,13 @@ All sources of data processed by the product in its secure-by-default configurat
See Section 5.3 for which mitigations are necessary for which security profiles and Annex C.4 for the rationale.
### 5.2.X **TR-AVAI**: Availability
### 5.2.X TR-AVAI: Availability
#### 5.2.X.x Requirement
The product shall protect the availability of essential and core functions.
#### 5.2.X.x **MI-AVNT**: Availabilty of network services
#### 5.2.X.x MI-AVNT: Availability of network services
The product shall protect the availability of essential and core network services through mitigation of denial-of-service attacks.
@@ -1511,15 +1511,32 @@ The product shall protect the availability of essential and core network service
* Verdict: Every essential or core network service is documented and the mitigations are sufficient => PASS, otherwise FAIL
* Evidence: All configuration files for network services, documentation of network services and the ways to mitigate a denial-of-service attack on it, internal lists of listening ports, results of an external port scan
| Risk factors | Requires mitigations |
|---------------------|----------------------|
| TNET < 1 & FNET < 1 | none |
| all others | AVNT |
#### 5.2.13.2 MI-WDOG: Watchdog and self-initiated reset
| Security Profile | Requires mitigations |
|------------------|----------------------|
| LR, IoT-1 | none |
| all others | AVNT |
The product shall implement a mechanism to trigger an automatic reset when it detects that it is no longer able to perform its functions.
* Reference: TR-AVAI
* Objective: Availability
* Preparation: Document the conditions that indicate the product cannot perform its functions
* Activities: Cause each of the conditions to occur and observe whether the product resets
* Verdict: Every condition triggers an automatic reset => PASS, otherwise FAIL
* Evidence: Documentation, log messages
#### 5.2.13.4 MI-FDRP: Fast packet drop
> TODO: Write mitigation requiring the product to do validity checks on packets from both the network and the user in order of cheapest to most expensive so it can drop invalid packets with as little resource usage as possible.
#### 5.2.13.5 MI-LMEM: Limit memory usage
> TODO: Write mitigation requiring the product limit memory usage triggered by user input via network or local access.
#### 5.2.13.6 MI-FAIR: Fair resource usage and prioritization
> TODO: Write mitigation requiring the product implement some form of ensuring fair resource usage by multiple sources of input, including the ability to prioritize some sources of input.
#### 5.2.13.7 MI-DOST: Document risk transfer to operational environment for denial of service
> TODO: Write mitigation documenting that the operational environment must provide denial of service protection, such as an external or internal firewall, fair queueing or filtering, a proxy, etc.
