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

CAT II (Medium)

The Mainframe Product must maintain a separate execution domain for each executing process.

Rule ID

SV-205586r1137804_rule

STIG

Mainframe Product Security Requirements Guide

Version

V3R4

CCIs

CCI-002530

Discussion

Applications can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. An example is a web browser with process isolation that provides tabs that are separate processes using separate address spaces to prevent one tab crashing the entire browser. This requirement also applies to Zero Trust initiatives.

Check Content

If the Mainframe Product has no function or capability for multi-session operation, this is not applicable.

If the Mainframe Product is not configured to uniquely define and engineer each session to execute independently of any other session, this is a finding.

Fix Text

Configure the Mainframe Product to uniquely define and engineer each session to execute independently of any other session.