BaselineWatch
5 STIGs
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

Mobile STIGs

5 STIGs followed · All platforms
All 44 CAT I 2CAT II 35CAT III 7 Browse in the Register

CAT I 2

Any vulnerability, the exploitation of which will directly and immediately result in loss of confidentiality, availability or integrity.

  1. GOOG-17-009400 CAT I V-284730 · PP-MDF-994000

    Android 17 devices must have the latest available Google Android 17 operating system installed.

    Maps to CM-6 via CCI-000366
    Check

    Review device configuration settings to confirm the Google Android device has the most recently released version of managed Google Android 17 installed. This procedure is performed on both the EMM administration console and the managed Google Android 17 device. On the EMM console, review the version of Google Android 17 installed on a sample of managed devices. This procedure will vary depending on the EMM product. On the managed Google Android 17 device, to determine the installed operating system version: COBO and COPE: 1. Open Settings. 2. Tap "About phone". 3. Verify "Build number". If the installed version of the Google Android 17 operating system on any reviewed device is not the latest released by Google, this is a finding. Google's Android operating system patch website: https://source.android.com/security/bulletin/ Android versions for Pixel devices: https://developers.google.com/android/images

    Fix

    Install the latest released version of the Google Android 17 operating system on all managed Google devices. Note: Google Android device operating system updates are released directly by Google or can be distributed via the EMM. Check each device manufacturer and/or carriers for current updates.

  2. GOOG-17-010000 CAT I V-284736 · PP-MDF-994000

    Google Android 17 must be configured to disable Private Space use.

    Maps to CM-6(1) via CCI-000370
    Check

    Review the Google Android 17 work profile configuration settings to confirm that Private Space is disabled. This procedure is performed only on the EMM administration console. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Verify that "Disallow add private profile" is set to "ON". COPE: 1. Open "Set user restrictions". 2. Verify that "Disallow add private profile" is set to "ON". If on the EMM console "Disallow add private profile" is not selected, this is a finding.

    Fix

    Configure the Google Android 17 device to disable Private Space. On the EMM console: COBO: 1. Open "Set user restrictions". 2. Toggle "Disallow add private profile" to "ON". COPE: 1. Open "Set user restrictions". 2. Toggle "Disallow add private profile" to "ON". Configuration API: DISALLOW_ADD_PRIVATE_PROFILE