BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

GOOG-17-006600 Google Android 17 must be configured to enable audit logging.

DISA STIG library Y26M06
All changes in this version
first version loaded CAT II

Maps to AU-6(4) via CCI-000154

Title

Google Android 17 must be configured to enable audit logging.

Control

Inspect the configuration on the managed Google Android 17 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 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 audit logging, this is a finding.

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_EXT1.1 #32

Related controls

CCI-000154

Fix

Configure the Google Android 17 device to enable audit logging. On the EMM console: COBO and COPE: 1. Open the "Device owner management" section. 2. Toggle "Enable security logging" to "ON". Configuration API: setSecurityLoggingEnabled