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

CAT II (Medium)

The Mainframe Product must produce audit records containing information to establish what type of events occurred.

Rule ID

SV-205464r960891_rule

STIG

Mainframe Product Security Requirements Guide

Version

V3R4

CCIs

CCI-000130

Discussion

Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the application and audit logs 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 what type of 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 what type of events occurred.