SC-3: Security Function Isolation
Control Family:
Threats Addressed:
Baselines:
- Low
N/A
- Moderate
N/A
- High
- SC-3
Next Version:
- NIST Special Publication 800-53 Revision 5:
- SC-3: Security Function Isolation
Control Statement
The information system isolates security functions from nonsecurity functions.
Supplemental Guidance
The information system isolates security functions from nonsecurity functions by means of an isolation boundary (implemented via partitions and domains). Such isolation controls access to and protects the integrity of the hardware, software, and firmware that perform those security functions. Information systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including, for example, 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. Information systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities. While the ideal is for all of the code within the security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions within the isolation boundary as an exception.
Control Enhancements
SC-3(1): Hardware Separation
Baseline(s):
The information system utilizes underlying hardware separation mechanisms to implement security function isolation.
SC-3(2): Access / Flow Control Functions
Baseline(s):
The information system isolates security functions enforcing access and information flow control from nonsecurity functions and from other security functions.
SC-3(3): Minimize Nonsecurity Functionality
Baseline(s):
The organization minimizes the number of nonsecurity functions included within the isolation boundary containing security functions.
SC-3(4): Module Coupling And Cohesiveness
Baseline(s):
The organization implements security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.
SC-3(5): Layered Structures
Baseline(s):
The organization implements security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.