STIGQter: STIG Summary: Google Android 16 COBO Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 13 May 2026:

Google Android 16 must be configured to disable Bluetooth or configured via User Based Enforcement (UBE) to allow Bluetooth for only Headset Profile (HSP), Hands-Free Profile (HFP), and Serial Port Profile (SPP).

DISA Rule

SV-276767r1140665_rule

Vulnerability Number

V-276767

Group Title

PP-MDF-333320

Rule Version

GOOG-16-009400

Severity

CAT III

CCI(s)

• CCI-000381 - Configure the system to provide only organization-defined mission essential capabilities.
• CCI-001761 - Defines the functions, ports, protocols, software, and services within the information system that are to be disabled or removed when deemed unnecessary and/or nonsecure.

Weight

10

Fix Recommendation

Configure the Google Android 16 device to disable Bluetooth, or if the AO has approved the use of Bluetooth (for example, for car hands-free use), train the user to connect to only authorized Bluetooth devices using only HSP, HFP, or SPP Bluetooth-capable devices (User-Based Enforcement).

To disable Bluetooth, use the following procedure:

On the EMM console:

COBO:

1. Open the "User restrictions" section.
2. Toggle "Disallow Bluetooth" to "ON".

COPE:

1. Open the "User restrictions on parent" section.
2. Toggle "Disallow Bluetooth" to "ON".

The user training requirement is satisfied in GOOG-16-009800.

Configuration API: DISALLOW_CONFIG_BLUETOOTH

Check Contents

Determine if the authorizing official (AO) has approved the use of Bluetooth at the site. If the AO has not approved the use of Bluetooth, verify that Bluetooth has been disabled.

On the EMM console:

COBO:

1. Open the "User restrictions" section.
2. Verify that "Disallow Bluetooth" is toggled to "ON".

COPE:

1. Open the "User restrictions on parent" section.
2. Verify that "Disallow Bluetooth" is toggled to "ON".

On the managed Google Android 16 device:

COBO and COPE:

1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth.
2. Verify that "Use Bluetooth" is set to "OFF" and cannot be toggled to "ON".

If the AO has approved the use of Bluetooth, on the managed Android 16 device:

1. Go to Settings >> Connected Devices.
2. Verify that only approved Bluetooth-connected devices using approved profiles are listed.

If the AO has not approved the use of Bluetooth, and Bluetooth use is not disabled via an EMM-managed device policy, this is a finding.

If the AO has approved the use of Bluetooth, and Bluetooth devices using unauthorized Bluetooth profiles are listed on the device under "Connected devices", this is a finding.

Vulnerability Number

V-276767

Documentable

False

Rule Version

GOOG-16-009400

Severity Override Guidance

Determine if the authorizing official (AO) has approved the use of Bluetooth at the site. If the AO has not approved the use of Bluetooth, verify that Bluetooth has been disabled.

On the EMM console:

COBO:

1. Open the "User restrictions" section.
2. Verify that "Disallow Bluetooth" is toggled to "ON".

COPE:

1. Open the "User restrictions on parent" section.
2. Verify that "Disallow Bluetooth" is toggled to "ON".

On the managed Google Android 16 device:

COBO and COPE:

1. Go to Settings >> Connected Devices >> Connection Preferences >> Bluetooth.
2. Verify that "Use Bluetooth" is set to "OFF" and cannot be toggled to "ON".

If the AO has approved the use of Bluetooth, on the managed Android 16 device:

1. Go to Settings >> Connected Devices.
2. Verify that only approved Bluetooth-connected devices using approved profiles are listed.

If the AO has not approved the use of Bluetooth, and Bluetooth use is not disabled via an EMM-managed device policy, this is a finding.

If the AO has approved the use of Bluetooth, and Bluetooth devices using unauthorized Bluetooth profiles are listed on the device under "Connected devices", this is a finding.

Check Content Reference

M

Target Key

5716