@@ -747,13 +747,13 @@ Mitigations are how a technical requirement can be satisfied. Mitigations should
Format:
5.X.Y**TR-XXXX**:
### 5.2.X **TR-XXXX**:
5.X.Y.Z Requirement
#### 5.2.X.x Requirement
_Description of high-level requirement in “shall” format._
5.X.Y.Z**MI-XXXX**:
#### 5.2.X.x **MI-XXXX**:
_Description of mitigation implementing the requirement in "shall" format._
@@ -807,7 +807,7 @@ Some risks may be transferred partially or fully to other components of the syst
### 5.2.X **TR-MISO**: Prevent local unauthorized access of memory-addressable security-relevant data
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall protect memory addresses from unauthorized access by executables under the product's control, including the product itself. This includes system memory, storage addressable via memory mapping, memory for I/O devices, and anything else accessible via the memory-related instructions in the platform.
@@ -936,7 +936,7 @@ Mitigations satisfy technical requirements only under when they mitigate the rel
### 5.2.X **TR-MIME**: Mitigate memory errors
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall appropriately mitigate memory errors.
@@ -1138,7 +1138,7 @@ Both kernel and userspace threads shall use hardware-supported memory tagging to
### 5.2.X **TR-SDEF**: Secure by default configuration
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall operate in a secure configuration by default.
@@ -1170,9 +1170,9 @@ The product shall require appropriate authorization by default to access securit
|---------------------|----------------------|
| all | ADEF |
#### 5.2.X **TR-CDST**: Confidentiality of data stored on the product
### 5.2.X **TR-CDST**: Confidentiality of data stored on the product
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall protect data stored on the product from unauthorized access.
@@ -1206,9 +1206,9 @@ Guidance: Data may be protected by the environment, permissions, encryption, sal
| LR, IoT-1 | none |
| all others | CDST |
#### 5.2.X **TR-CDTX**: Confidentiality of data transmitted by product
### 5.2.X **TR-CDTX**: Confidentiality of data transmitted by product
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall protect data transmitted by the product from unauthorized access.
@@ -1244,9 +1244,9 @@ Guidance: Data transmitted may be protected by the environment or encryption.
> TODO: Rate use cases by sensitivity of data transmitted and update the security profile list above.
#### 5.2.X **TR-IDST**: Integrity of data stored on the product
### 5.2.X **TR-IDST**: Integrity of data stored on the product
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall protect the integrity of data stored on the product from unauthorized modification and report corruption.
@@ -1300,9 +1300,9 @@ The product shall detect corruption of the data stored on the product.
> TODO: Rate use cases by sensitivity of data transmitted and update the security profile list above.
#### 5.2.X **TR-IDTX**: Integrity of data transmitted by the product
### 5.2.X **TR-IDTX**: Integrity of data transmitted by the product
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall detect corruption of the data transmitted by the product.
@@ -1340,7 +1340,7 @@ The product shall detect corruption of the data transmitted by the product.
The manufacturer shall minimize exposed interfaces in the default configuration of the product in all operating modes, including initial configuration, during initialization, while in use, while shutting down or paused, or after reset.
@@ -1377,7 +1377,7 @@ All exposed interfaces on the product in any state that is part of its reasonabl
### 5.2.X **TR-SCDL**: Secure deletion
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall provide a method of deleting all data and settings and resetting the product to its secure-by-default configuration.
@@ -1447,7 +1447,7 @@ The product shall reset to its secure-by-default state after the secure deletion
### 5.2.X **TR-SDTR**: Secure data read and transfer
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall provide a method to read all data and settings from the product, and if provided, securely transfer data and settings to another product.
@@ -1499,7 +1499,7 @@ The product shall provide a method by which an authorized user can securely tran
### 5.2.X **TR-DMIN**:
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall minimize the data processed.
@@ -1534,13 +1534,13 @@ All sources of data processed by the product in its secure-by-default configurat
> FIXME: When full use case risk factor and tolerances are available, update above table.
5.X.Y **TR-LOGG**: Logging and monitoring
### 5.X.Y **TR-LOGG**: Logging and monitoring
5.X.Y.Z Requirement
#### 5.2.X.x Requirement
The product shall record security-relevant internal events, including but not limited to changes to configuration and access or modification of data and functions. The product shall provide an opt-out mechanism.
5.X.Y.Z**MI-LOGG**:
#### 5.2.X.x **MI-LOGG**:
The product shall record log messages indicating security-relevant internal events in an internal or external log. The log messages shall not include any confidential information such as PII, secrets, or credentials, or any information which might reasonably be expected to include such items.
@@ -1567,11 +1567,11 @@ Guidance: One type of event whose log message must take care to not accidentally
> FIXME: Update when risk factors are updated
5.X.Y **TR-MIMP**:
### 5.X.Y **TR-MIMP**:
The product shall minimise its negative impact on other products or services.
5.X.Y.Z**MI-MNET**:
#### 5.2.X.x **MI-MNET**:
The product shall minimise its negative impact on other products or services via the data it transmits on the network. Each source of network data shall be documented, along with the ways it can interfere with other products or services, and methods the product uses to minimise that interference.
@@ -1582,7 +1582,7 @@ The product shall minimise its negative impact on other products or services via
* Verdict: Every method of sending network data is documented with ways it can interface and methods used to minimise => PASS, otherwise FAIL
* Evidence: All configuration files for network services, documentation of network services and their impact and methods to minimise it, internal lists of listening ports, results of an external port scan
5.X.Y.Z**MI-MAMP**:
#### 5.2.X.x **MI-MAMP**:
The product shall mitigate abuse of network services that amplify network traffic in manner that can be used to attack other devices. Each network service and its associated mitigations shall be documented.
@@ -1605,11 +1605,11 @@ The product shall mitigate abuse of network services that amplify network traffi
| IoT-2, IoT-3 | MNET |
| all others | MNET, MAMP |
5.X.Y **TR-AVAI**:
### 5.X.Y **TR-AVAI**:
The product shall protect the availability of essential and core functions.
5.X.Y.Z**MI-AVNT**:
#### 5.2.X.x **MI-AVNT**:
The product shall protect the availability of essential and core network services through mitigation of denial-of-service attacks.
@@ -1630,11 +1630,11 @@ The product shall protect the availability of essential and core network service
| LR, IoT-1 | none |
| all others | AVNT |
5.X.Y **TR-NKEV**:
### 5.X.Y **TR-NKEV**:
The product shall be made available on the market with no known vulnerabilities.
5.X.Y.Z**MI-KEVD**:
#### 5.2.X.x **MI-KEVD**:
The product shall be accompanied by documentation of how to report vulnerabilities, how to find out what vulnerabilities have been fixed, the timeline in which vulnerabilities will be remediated, and how the product may be securely updated before use.
@@ -1645,7 +1645,7 @@ The product shall be accompanied by documentation of how to report vulnerabiliti
* Verdict: If the secure update completes successfully, the most recently fixed vulnerability is fixed, and the documentation includes all the required information => PASS, otherwise FAIL
* Evidence: Documentation of vulnerability handling, documentation of how to securely update the product, the report for the selected vulnerability, description of how to scan for the vulnerability, log of vulnerability scan results
5.X.Y.Z**MI-SCAN**:
#### 5.2.X.x **MI-SCAN**:
If automated, freely usable vulnerability scanners are available for the product, the product shall either (1) not have any vulnerabilities discoverable by the top three most comprehensive scanners (or fewer, if there are fewer than three automated, freely usable scanners), or (2) have documentation explaining why the risk of any detected vulnerability has been mitigated.
@@ -1669,7 +1669,7 @@ If automated, freely usable vulnerability scanners are available for the product
### 5.2.X **TR-SCUD**: Secure updates
### 5.2.X.x Requirement
#### 5.2.X.x Requirement
The product shall be securely updateable by the user.
