sc-7-20-dynamic-isolation-and-segregation

name	SC-7(20)_dynamic-isolation-and-segregation
description	Provide the capability to dynamically isolate [organization-defined] from other system components.
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","sc-7-20","sc","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows","network"]
cwe_ids	["CWE-311"]
chains_with	[]
prerequisites	["SC-7"]
severity_boost	{}

SC-7(20) Dynamic Isolation and Segregation

Enhancement of: SC-7

High-Level Description

Family: System and Communications Protection (SC) Framework: NIST SP 800-53 Rev 5

The capability to dynamically isolate certain internal system components is useful when it is necessary to partition or separate system components of questionable origin from components that possess greater trustworthiness. Component isolation reduces the attack surface of organizational systems. Isolating selected system components can also limit the damage from successful attacks when such attacks occur.

What to Check

• Verify SC-7(20) Dynamic Isolation and Segregation is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for SC-7(20)
• Verify enhancement builds upon base control SC-7

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for SC-7(20) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
cloud-audit-mcp	Check encryption and network controls	cloud_audit_encryption
nmap	Network scanning	nmap -sV --script ssl-enum-ciphers

Remediation Guide

Control Statement

Provide the capability to dynamically isolate [organization-defined] from other system components.

Implementation Guidance

The capability to dynamically isolate certain internal system components is useful when it is necessary to partition or separate system components of questionable origin from components that possess greater trustworthiness. Component isolation reduces the attack surface of organizational systems. Isolating selected system components can also limit the damage from successful attacks when such attacks occur.