BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

SC-07(29) Separate Subnets to Isolate Functions

NIST SP 800-53 (controls) 5.2.0 against 5.2.0
All changes in this version
unchanged SC part of SC-7

Title

Separate Subnets to Isolate Functions

Control

Implement [Selection: physically; logically] separate subnetworks to isolate the following critical system components and functions: [Assignment: critical system components and functions].

Discussion

Separating critical system components and functions from other noncritical system components and functions through separate subnetworks may be necessary to reduce susceptibility to a catastrophic or debilitating breach or compromise that results in system failure. For example, physically separating the command and control function from the in-flight entertainment function through separate subnetworks in a commercial aircraft provides an increased level of assurance in the trustworthiness of critical system functions.

Parameters

sc-07.29_odp.01: [physically; logically]
sc-07.29_odp.02: critical system components and functions

Assessment objective

SC-07(29) subnetworks are separated [Selection: physically; logically] to isolate [Assignment: critical system components and functions].

STIG rules that implement this control 0

No followed STIG rule cites a CCI indexed to this control (CCI list 2026-07-14).