SC-32

Requirement

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 physical or logical separation of components].

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.

NIST 800-53A Assessment Guidance

Examine

[SELECT FROM: 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

[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system; system developers/integrators].

Test

[SELECT FROM: Mechanisms supporting and/or implementing the physical separation of system components].

ID	Assessment Objectives
SC-32	the system is partitioned into <SC-32_ODP[01] system components> residing in separate <SC-32_ODP[02] SELECTED PARAMETER VALUE> domains or environments based on <SC-32_ODP[03] circumstances for the physical or logical separation of components>.

Our CMMC Overview Course simplifies CMMC. Enroll so you can make informed decisions!