STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Google Android 16 COPE Security Technical Implementation Guide

V-276850

CAT II (Medium)

Google Android 16 must be configured to enable audit logging.

Rule ID

SV-276850r1140342_rule

STIG

Google Android 16 COPE Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000154

Discussion

Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. For the audit logs to be useful, administrators must have the ability to view them. SFR ID: FMT_SMF.1.1 #32

Check Content

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.

Fix Text

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