The Mainframe Product must isolate security functions from nonsecurity functions.

From Mainframe Product Security Requirements Guide

Associated with: CCI-001084

SV-82959r1_rule The Mainframe Product must isolate security functions from nonsecurity functions.

Vulnerability discussion

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.

Check content

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

Configure the Mainframe Product to load security modules into a separate dataset than nonsecurity modules.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.