STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Mainframe Product Security Requirements Guide

V-205517

CAT II (Medium)

The Mainframe Product must separate user functionality (including user interface services) from information system management functionality.

Rule ID

SV-205517r1137803_rule

STIG

Mainframe Product Security Requirements Guide

Version

V3R4

CCIs

CCI-001082

Discussion

Application management functionality includes functions necessary for administration and requires privileged user access. Allowing nonprivileged users to access application management functionality capabilities increases the risk that nonprivileged users may obtain elevated privileges. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, different TCP/UDP ports, virtualization techniques, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different security domain and with additional access controls. This requirement also applies to Zero Trust initiatives.

Check Content

Examine installation and configuration settings.

User module should be loaded into a separate dataset than system management modules.

If the Mainframe Product does not differentiate user functionality from product management functionality, this is a finding.

Fix Text

Configure the Mainframe Product to load user modules into a separate dataset than system management modules.