Free DISA STIG and SRG Library | Vaulted

V-56843

The operating system must isolate security functions from nonsecurity functions.

Finding ID
SRG-OS-000134-GPOS-00068
Rule ID
SV-71103r1_rule
Severity
Cat II
CCE
(None)
Group Title
SRG-OS-000134-GPOS-00068
CCI
CCI-001084
Target Key
(None)
Documentable
No
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. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code. 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. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.

Fix Text

Configure the operating system to isolate security functions from nonsecurity functions.

Check Content

Verify the operating system isolates security functions from nonsecurity functions. If it does not, this is a finding.