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 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Database Security Requirements Guide

V-206606

CAT II (Medium)

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

Rule ID

SV-206606r1137659_rule

STIG

Database Security Requirements Guide

Version

V4R5

CCIs

CCI-002530

Discussion

Database management systems 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 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. This requirement also applies to Zero Trust initiatives.

Check Content

Review the DBMS architecture to find out if and how it protects the private resources of one process (such as working memory, temporary tables, uncommitted data and, especially, executable code) from unauthorized access or modification by another user or process.

If it is not capable of maintaining a separate execution domain for each executing process, this is a finding.

If the DBMS is capable of maintaining a separate execution domain for each executing process, but is configured not to do so, this is a finding.

Fix Text

Deploy a DBMS capable of maintaining a separate execution domain for each executing process.

If this is a configurable feature, configure the DBMS to implement it.