STIGhubSTIGhub
STIGsRMF ControlsCompare

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
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Mainframe Product Security Requirements Guide

V-205467

CAT II (Medium)

The Mainframe Product must produce audit records containing information to establish the source of the events.

Rule ID

SV-205467r960900_rule

STIG

Mainframe Product Security Requirements Guide

Version

V3R4

CCIs

CCI-000133

Discussion

Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In addition to logging where events occur within the application, the application must also produce audit records that identify the application itself as the source of the event. In the case of centralized logging, the source would be the application name accompanied by the host or client name. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know the source of the event, particularly in the case of centralized logging. Associating information about the source of the event within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.

Check Content

Examine installation and configuration settings.

Verify data written to external security manager audit files and/or SMF records contain information that details the source of events. If it does not, this is a finding.

Fix Text

Configure the Mainframe Product audit records written to external security manager audit files and/or SMF records to contain information to establish the source of the events.