STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Motorola Solutions Android 13 COPE Security Technical Implementation Guide

V-272349

CAT II (Medium)

Motorola Solutions Android 13 must be configured to enable audit logging.

Rule ID

SV-272349r1093476_rule

STIG

Motorola Solutions Android 13 COPE Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000154

Discussion

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

Check Content

Inspect the configuration on the managed Motorola Solutions Android 13 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 Motorola Solutions Android 13 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".