SC-32 System Partitioning
System and Communications Protection
Description
Partition the system into [Assignment: organization-defined system components] residing in separate [Selection (one): physical; logical] domains or environments based on [Assignment: organization-defined circumstances for physical or logical separation of components].
Supplemental Guidance
System partitioning is part of a defense-in-depth protection strategy. Organizations determine the degree of physical separation of system components. Physical separation options include physically distinct components in separate racks in the same room, critical components in separate rooms, and geographical separation of critical components. Security categorization can guide the selection of candidates for domain partitioning. Managed interfaces restrict or prohibit network access and information flow among partitioned system components.
Changes from Rev 4
No significant changes from Rev 4.
Enhancements (1)
What NIST adds to this control. Select one to read its statement.
SC-32(01) Separate Physical Domains for Privileged Functions
Partition privileged functions into separate physical domains.
Patterns that use this control (3)
Grouped by the emphasis each pattern gives it.
MITRE ATT&CK Techniques (1)
ATT&CK v16.1Techniques mitigated by this control, mapped via CTID.