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

Google Android 16 must be configured to enable audit logging.

DISA Rule

SV-276850r1140342_rule

Vulnerability Number

V-276850

Group Title

PP-MDF-993300

Rule Version

GOOG-16-002800

Severity

CAT II

CCI(s)

• CCI-000154 - Provide the capability to centrally review and analyze audit records from multiple components within the system.

Weight

10

Fix Recommendation

Configure the Google Android 16 device to enable audit logging.

On the EMM console:

COBO and COPE:

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

Configuration API: setSecurityLoggingEnabled

Check Contents

Inspect the configuration on the managed Google Android 16 device to enable audit logging.

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

On the EMM console:

COBO and COPE:

1. Open "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 audit logging, this is a finding.

Vulnerability Number

V-276850

Documentable

False

Rule Version

GOOG-16-002800

Severity Override Guidance

Inspect the configuration on the managed Google Android 16 device to enable audit logging.

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

On the EMM console:

COBO and COPE:

1. Open "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 audit logging, this is a finding.

Check Content Reference

M

Target Key

5717