STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Google Android 16 COBO Security Technical Implementation Guide

V-276779

CAT III (Low)

Android 16 devices must be configured to enable Common Criteria (CC) Mode.

Rule ID

SV-276779r1140129_rule

STIG

Google Android 16 COBO Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000366

Discussion

The CC Mode feature is a superset of other features and behavioral changes that are mandatory MDFPP requirements. If CC Mode is not implemented, the device will not be operating in the NIAP-certified compliant CC Mode of operation. CC Mode implements the following behavioral/functional changes: How the Bluetooth and Wi-Fi keys are stored using different types of encryption. SFR ID: FMT_SMF.1.1 #47

Check Content

Review the managed Google Android 16 configuration settings to confirm CC Mode is enabled. 
 
This procedure is performed on the EMM Administration Console.
 
COBO and COPE:

1. Open Device owner management.
2. Verify that "Enable Common Criteria mode" is toggled to "ON".

If CC Mode is not enabled, this is a finding.

Fix Text

Configure the Google Android 16 device to implement CC Mode. 
 
On the EMM console:

COBO and COPE:

1. Open Device owner management.
2. Toggle "Enable Common Criteria mode" to "ON".

Configuration API: setCommonCriteriaModeEnabled