Commit 70bca2e2 authored by Valerie Aurora (Bow Shock)'s avatar Valerie Aurora (Bow Shock)
Browse files

Minor edits before sending for public review

parent 36cf9e35
Loading
Loading
Loading
Loading
+4 −4
Original line number Diff line number Diff line
@@ -727,9 +727,8 @@ Potential additional risk factors:
* Running on bare metal vs. hypervisor
* Many devices have multiple OS's for elements

Val: Phone should be significantly riskier than a personal laptop. The phone goes everywhere, is always on, always connected, filled with sensors, super loaded with personally identifiable data, practically begs you to install with data stealing apps.
Phone should be significantly riskier than a personal laptop. The phone goes everywhere, is always on, always connected, filled with sensors, super loaded with personally identifiable data, practically begs you to install with data stealing apps.

Carl-Daniel:
Separate question for the application delivery mechanism:
1. App is not preinstalled, but by default gets installed during initial configuration by the user if the user always picks the preselected option -> IMHO part of the device, forcing installation later should not be an allowed trick to make the scope smaller.
2. Third party app is installed through the official app store/repository, but vetted less (or not at all) by the OS vendor. Do we want to require a vetting level indicator if the same source has multiple tiers of vetting?
@@ -821,13 +820,14 @@ For example, most individual hardware components do not have a built-in method o

### 4.10.2 Security functions provided outside the product

The operating system relies on correctly functioning hardware to implement its functions. It relies on security functions and configuration provided by the hardware, boot manager, and any virtualization prior to the beginning of its execution. Such security functions may include:
The operating system relies on correctly functioning hardware to implement its functions. It relies on security functions and configuration provided by the environment, hardware, boot manager, and any virtualization prior to the beginning of its execution. Such security functions may include:

* Memory protection
* Secure or measured boot
* Confidential data transmission
* Encryption of data at rest
* Secure updates
* Access control

### 4.10.3 Security functions provided to other components