NIST 800-53 REV 5 • SYSTEM AND COMMUNICATIONS PROTECTION
SC-30(3) — Change Processing and Storage Locations
Change the location of {{ insert: param, sc-30.03_odp.01 }} {{ insert: param, sc-30.03_odp.02 }}].
CMMC Practice Mapping
No direct CMMC mapping
NIST 800-171 Mapping
No direct NIST 800-171 mapping
Related Controls
No related controls listed
Supplemental Guidance
Adversaries target critical mission and business functions and the systems that support those mission and business functions while also trying to minimize the exposure of their existence and tradecraft. The static, homogeneous, and deterministic nature of organizational systems targeted by adversaries make such systems more susceptible to attacks with less adversary cost and effort to be successful. Changing processing and storage locations (also referred to as moving target defense) addresses the advanced persistent threat using techniques such as virtualization, distributed processing, and replication. This enables organizations to relocate the system components (i.e., processing, storage) that support critical mission and business functions. Changing the locations of processing activities and/or storage sites introduces a degree of uncertainty into the targeting activities of adversaries. The targeting uncertainty increases the work factor of adversaries and makes compromises or breaches of the organizational systems more difficult and time-consuming. It also increases the chances that adversaries may inadvertently disclose certain aspects of their tradecraft while attempting to locate critical organizational resources.
Practitioner Notes
Periodically change where data is processed and stored so attackers cannot rely on static locations to find their targets.
Example 1: In a cloud environment, periodically migrate workloads between regions or availability zones. An attacker who has identified the specific physical infrastructure hosting your data finds it has moved.
Example 2: Rotate which servers handle specific functions. Instead of always processing CUI on Server-A, cycle the function between multiple prepared servers. Use load balancers and automation to make this transparent to users while confusing attackers.