SC-32 System Partitioning
Guidance: nonePolicy clause: noneWhat these mean
sc32ctl| Baselines | Implementation level | Enhancements |
|---|---|---|
| Not in a baseline | Organization | 1 (0 in a baseline) |
Related controls: AC-4, AC-6, SA-8, SC-2, SC-3, SC-7, SC-36
Control statement
Section titled “Control statement”Partition the system into [Assignment: organization-defined system components] residing in separate [Selection: physical; logical] domains or environments based on [Assignment: organization-defined circumstances for the physical or logical separation of components].
NIST discussion
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.
Control enhancements
Section titled “Control enhancements”SC-32(1) Separate Physical Domains for Privileged Functions
Section titled “SC-32(1) Separate Physical Domains for Privileged Functions”Baselines: Not in a baseline
Partition privileged functions into separate physical domains.
Discussion and assessment objectives for SC-32(1)
Privileged functions that operate in a single physical domain may represent a single point of failure if that domain becomes compromised or experiences a denial of service.
Determine if privileged functions are partitioned into separate physical domains.
Examine: System and communications protection policy; procedures addressing system partitioning; system design documentation; system configuration settings and associated documentation; system architecture; list of system physical domains (or environments); system facility diagrams; system network diagrams; system security plan; other relevant documents or records.
Interview: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system; system developers/integrators.
Test: Mechanisms supporting and/or implementing the physical separation of system components.
Assessment objectives (SP 800-53A)
Section titled “Assessment objectives (SP 800-53A)”Objectives and methods for SC-32
Determine if the system is partitioned into [Assignment: organization-defined system components] residing in separate [Selection: physical; logical] domains or environments based on [Assignment: organization-defined circumstances for the physical or logical separation of components].
Examine: System and communications protection policy; procedures addressing system partitioning; system design documentation; system configuration settings and associated documentation; system architecture; list of system physical domains (or environments); system facility diagrams; system network diagrams; system security plan; other relevant documents or records.
Interview: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system; system developers/integrators.
Test: Mechanisms supporting and/or implementing the physical separation of system components.
Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.