UCF STIG Viewer Logo

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


Overview

Finding ID Version Rule ID IA Controls Severity
V-250431 GOOG-12-007800 SV-250431r802810_rule Medium
Description
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 Requirement Statement 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_EXT.1.1 #37
STIG Date
Google Android 12 COPE Security Technical Implementation Guide 2021-09-17

Details

Check Text ( C-53866r802657_chk )
Review managed Google Android 12 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 "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.
Fix Text (F-53820r802809_fix)
Configure the Google Android 12 device to generate audit records for the following auditable events: detected integrity violations.

On the EMM console:

COBO and COPE:

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