@@ -1581,6 +1581,8 @@ All exposed interfaces on the product in any state that is part of its reasonabl
The product shall provide a method of deleting all data and settings and resetting the product to its secure-by-default configuration.
Guidance: Overwriting all storage or encrypting all data and deleting the key are two secure deletion mechanisms.
#### 5.2.X.x **MI-RSET**:
The product shall reset to its secure-by-default state after a power cycle or reset command.
@@ -1591,17 +1593,79 @@ The product shall reset to its secure-by-default state after a power cycle or re
* Preparation: Document every kind of data or setting that may be stored on the product, how to store it on the product, and how to read it from the product
* Activities: For each kind of user data or setting that may be stored on the product, write an instance of the data or setting stored on the product that is different from the default, read it from the product, power cycle or reset the product, and read the data again
* Activities: For each kind of user data or setting that may be stored on the product, write an instance of the data or setting stored on the product that is different from the default and read it from the product; once all kinds of data have been written and read, power cycle or reset the product, and read each kind of data again
* Verdict: If any data or setting is the same for both of the reads => FAIL, otherwise => PASS
* Evidence: Record of each type of data or setting, what data or setting was written, what data or setting was returned by the first read, and what data or setting was returned by the second read, comparison of each one
#### 5.2.X.x **MI-INST**:
The product shall reset to its secure-by-default state after a reinstallation that securely deletes all previous user data or settings.
* Reference: TR-SCDL
* Objective: Secure deletion
* Preparation: Document every kind of data or setting that may be stored on the product, how to store it on the product, and how to read it from the product
* Activities: For each kind of user data or setting that may be stored on the product, write an instance of the data or setting stored on the product that is different from the default and read it from the product; once all kinds of data have been written and read, reinstall the product with the secure delete option, and read the data or settings again
* Verdict: If any data or setting is the same for both of the reads => FAIL, otherwise => PASS
* Evidence: Record of each type of data or setting, what data or setting was written, what data or setting was returned by the first read, and what data or setting was returned by the second read, comparison of each one
#### 5.2.X.x **MI-DELE**:
The product shall reset to its secure-by-default state after the secure deletion function is used.
* Reference: TR-SCDL
* Objective: Secure deletion
* Preparation: Document every kind of data or setting that may be stored on the product, how to store it on the product, and how to read it from the product
* Activities: For each kind of user data or setting that may be stored on the product, write an instance of the data or setting stored on the product that is different from the default and read it from the product; once all kinds of data have been written and read, activate the secure deletion function, and read the data or settings again
* Verdict: If any data or setting is the same for both of the reads => FAIL, otherwise => PASS
* Evidence: Record of each type of data or setting, what data or setting was written, what data or setting was returned by the first read, and what data or setting was returned by the second read, comparison of each one
#### 5.2.X.x Mapping of mitigations to risk factors and security profiles
| Risk factors | Requires mitigations |
|--------------|----------------------|
| SEND < 1 | None |
| all others | RSET or INST or DELE |
| Security Profile | Requires mitigations |
|------------------|----------------------|
| LR, IoT-1 | None |
| all others | RSET or INST or DELE |
> FIXME: Make the method of deletion depend on risk tolerance (low or med: simple reformat, high: overwrite once or delete key to encryped storage)
### 5.2.X **TR-SDTR**: Secure data transfer
The product shall provide a method to securely transfer all data and settings from the product to other products or systems.
The product shall provide a method to securely transfer all data and settings from the product.
#### 5.2.X.x **MI-DTTH**: Secure data transfer from product
The product shall provide a method by which an authorized user can securely transfer all data and settings from the product.
* Reference: TR-SDTR
* Objective: Secure data transfer
* Preparation: List all data and settings.
* Activities: For each kind of data or setting, read the data or setting as an authorized user, then attempt read the data or setting as an unauthorized user, if any exists
* Verdict: All data and settings can be read by the authorized user, and no data or setting can be read by an unauthorized user
* Evidence: List of data and settings, log message showing success or failure of each read by the authorized user and, if applicable, the unauthorized user
#### 5.2.X.x **MI-DTTH**: Data transfer
#### 5.2.X.x **MI-DTTH**: Secure read of data
The product shall provide a method by which an authorized user can securely read all data and settings from the product.
@@ -1998,7 +2062,7 @@ Risk Tolerances are applied to the foreseeable risks associated to each Security
Description: A non-internet-connected device such as a bluetooth speaker
| Use Case | NUSR | CUSR | DATA | SENS | PHYS | LOSS | HWMD | SWMD | DVCS | TNET | FNET | CONF | _TOTAL_ |
| Use Case | NUSR | CUSR | DATA | SEND | PHYS | LOSS | HWMD | SWMD | DVCS | TNET | FNET | CONF | _TOTAL_ |
