STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-205586SRG-APP-000431-MFP-000312SV-205586r1137804_ruleCCI-002530medium
Description
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.
STIGDate
Mainframe Product Security Requirements Guide2026-05-23

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (11) 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.

BCD-01Business Continuity Management System (BCMS)
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
SEA-01Secure Engineering Principles
1.00
SEA-01.2Achieving Resilience Requirements
1.00
SEA-02Alignment With Enterprise Architecture
1.00

+1 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (7) 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-6(8)Privilege Levels for Code Execution
1.00
CM-7Least Functionality
1.00
SC-18(3)Prevent Downloading and Execution
1.00
SC-2Separation of System and User Functionality
1.00
SC-39Process Isolation
1.00
SC-4Information in Shared System Resources
1.00
SI-16Memory Protection
1.00
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) 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.

Who does this work

13 NICE work roles and 8 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-205586r1137804_chk)

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 (F-5852r299986_fix)

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