BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

4 Applications

NIST platform security: roots of trust, firmware and secure enclaves SP 800-124 Rev. 1
All changes in this version
first version loaded 4 Applications

Title

Applications

Control

 Restrict which app stores may be used.

 Restrict which applications may be installed through whitelisting (preferable) or blacklisting.

 Restrict the permissions (e.g., camera access, location access) assigned to each application.

 Install, update, and remove applications. Safeguard the mechanisms used to perform these actions. Keep a current inventory of all applications installed on each device.

 Restrict the use of operating system and application synchronization services (e.g., local device synchronization, remote synchronization services and websites).

 Verify digital signatures on applications to ensure that only applications from trusted entities are installed on the device and that code has not been modified.

 Distribute the organization’s applications from a dedicated mobile application store.

7 Remote wipe is a fundamentally unreliable security control; for example, an attacker could access information on a device before it is wiped, or an attacker could power off a device to prevent it from receiving a remote wipe signal. Organizations should not rely on remote wipe as the sole security control for protecting sensitive data, but instead consider it to be one layer of a multi-layered approach to protection.