Google Android 16 must be configured to enable audit logging.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-276850 | GOOG-16-002800 | SV-276850r1140342_rule | CCI-000154 | medium |
| Description | ||||
| 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 | ||||
| STIG | Date | |||
| Google Android 16 COPE Security Technical Implementation Guide | 2026-02-12 | |||
Related Frameworks
2 paths across 2 frameworks
Related Frameworks
NIST 800-531 mapping
AU-6(4)
1.00
- DISA · V1R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
CCI1 mapping
CCI-000154
1.00
- DISA · V1R2 · disa_xccdf · related
Details
Check Text (C-276850r1140342_chk)
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 (F-80910r1140341_fix)
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