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 generate audit records for the following auditable events: Detected integrity violations.

DISA Rule

SV-276761r1140075_rule

Vulnerability Number

V-276761

Group Title

PP-MDF-333170

Rule Version

GOOG-16-007800

Severity

CAT II

CCI(s)

• CCI-000169 - Provide audit record generation capability for the event types the system is capable of auditing as defined in AU-2 a. on organization-defined information system components.

Weight

10

Fix Recommendation

Configure the Google Android 16 device to generate audit records for the following auditable events: Detected integrity violations.

On the EMM console:

COBO and COPE:

1. Open the "Device owner management" section.
2. Toggle "Enable security logging" to "ON".

Configuration API: setSecurityLoggingEnabled

Check Contents

Review managed Google Android 16 device configuration settings to determine if the mobile device is configured to generate audit records for the following auditable events: Detected integrity violations.

This validation procedure is performed only on the EMM Administration Console.

On the EMM console:

COBO and COPE:

1. Open the "Device owner management" section.
2. Verify that "Enable security logging" is toggled to "ON".

If the EMM console device policy is not set to enable security logging, this is a finding.

Vulnerability Number

V-276761

Documentable

False

Rule Version

GOOG-16-007800

Severity Override Guidance

Review managed Google Android 16 device configuration settings to determine if the mobile device is configured to generate audit records for the following auditable events: Detected integrity violations.

This validation procedure is performed only on the EMM Administration Console.

On the EMM console:

COBO and COPE:

1. Open the "Device owner management" section.
2. Verify that "Enable security logging" is toggled to "ON".

If the EMM console device policy is not set to enable security logging, this is a finding.

Check Content Reference

M

Target Key

5716