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-205466

CAT II (Medium)

The Mainframe Product must produce audit records containing information to establish where the events occurred.

Rule ID

SV-205466r960897_rule

STIG

Mainframe Product Security Requirements Guide

Version

V3R4

CCIs

CCI-000132

Discussion

Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred 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 where events occurred. 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 that details where the events occurred.