UCF STIG Viewer Logo

The mobile operating system must include the software component (e.g., user application, or operating system security module) that generated each event in audit logs.


Overview

Finding ID Version Rule ID IA Controls Severity
V-32955 SRG-OS-000039-MOS-000015 SV-43353r1_rule Low
Description
Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. Without sufficient information establishing where the audit events occurred, investigation into the cause of events is severely hindered. The inclusion of software component generating each event in the audit logs enables system administrators and IA personnel to identify where the audit events occurred.
STIG Date
Mobile Operating System Security Requirements Guide 2013-07-03

Details

Check Text ( C-41256r1_chk )
Review the audit logs to determine if the entries include the software component that generated the event. If an entry does not provide information regarding the source of the event, this is a finding.
Fix Text (F-36870r1_fix)
Modify the audit configuration to include the software component that generated the event for each entry in the audit logs.