UCF STIG Viewer Logo

The Mainframe Product must isolate security functions from nonsecurity functions.


Overview

Finding ID Version Rule ID IA Controls Severity
V-205521 SRG-APP-000233-MFP-000305 SV-205521r397747_rule Medium
Description
An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Applications restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.
STIG Date
Mainframe Product Security Requirements Guide 2022-09-22

Details

Check Text ( C-5787r299796_chk )
Examine installation and configuration settings.

Security modules should be loaded into different datasets than nonsecurity modules.

If the Mainframe Product does not differentiate between security and nonsecurity functions and provide procedure to isolate the functions, this is a finding.
Fix Text (F-5787r299797_fix)
Configure the Mainframe Product to load security modules into a separate dataset than nonsecurity modules.