Google Android 16 must be configured to generate audit records for the following auditable events: Detected integrity violations.

Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. They help identify attacks so that breaches can be prevented or limited in their scope. They facilitate analysis to improve performance and security. The Rule Title lists key events for which the system must generate an audit record.

Note: This requirement applies only to integrity violation detections that can be logged by the audit logging component.

SFR ID: FMT_SMF.1.1 #37

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.

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