STIGViewer Support

The Mainframe Product must initiate session auditing upon startup.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-205462SRG-APP-000092-MFP-000137SV-205462r960888_ruleCCI-001464medium
Description
If auditing is enabled late in the start-up process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.
STIGDate
Mainframe Product Security Requirements Guide2026-05-23

Related Frameworks

1 mapping across 2 frameworks
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (29) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-12(3)Changes by Authorized Individuals
1.00
AU-14(1)System Start-up
1.00
AU-14(2)Capture and Record Content
1.00
AU-3Content of Audit Records
1.00

+19 more (top 10 by confidence shown)

CCI1 mapping

Details

Check Text (C-205462r960888_chk)

If the Mainframe Product has no function or capability for session operations, this is not applicable. Examine installation and configuration settings. Verify that session auditing is initiated at session startup. If it is not, this is a finding.

Fix Text (F-5728r299620_fix)

Configure the Mainframe Product to initiate session auditing upon startup.