# SC-48 Sensor Relocation

NIST SP 800-53 control. Family: SC System and Communications Protection. Function: preventative. In no baseline. Mapping licence: CC BY-SA 4.0.

Statement: Relocate [Assignment: organization-defined sensors and monitoring capabilities] to [Assignment: organization-defined locations] under the following conditions or circumstances: [Assignment: organization-defined conditions or circumstances].
Guidance: Adversaries may take various paths and use different approaches as they move laterally through an organization (including its systems) to reach their target or as they attempt to exfiltrate information from the organization. The organization often only has a limited set of monitoring and detection capabilities, and they may be focused on the critical or likely infiltration or exfiltration paths. By using communications paths that the organization typically does not monitor, the adversary can increase its chances of achieving its desired goals. By relocating its sensors or monitoring capabilities to new locations, the organization can impede the adversary’s ability to achieve its goals. The relocation of the sensors or monitoring capabilities might be done based on threat information that the organization has acquired or randomly to confuse the adversary and make its lateral transition through the system or organization more challenging.

## Enhancements (1)
- SC-48(01) Dynamic Relocation of Sensors or Monitoring Capabilities
Each enhancement's statement: /api/v1/controls/SC-48?fields=enhancements

## Clauses by framework (13 frameworks)
- finos_ccc: CCC-C08
- iec_62443: 3-3 SR 6.2
- bsi_grundschutz: DER.1
- anssi: Hygiene.39
- finma_circular: IV.B.d(59), IV.C(62), IV.C(66), IV.C(67), IV.C(68), IV.C(69)
- fisc: FISC.O2
- nerc_cip: CIP-015-1. OSA's own, not in NIST and NERC Security Working Group's crosswalk: CIP-015-1
- tsa_psd: SD-2 Sec C
- ferc_cip: Order 881
- doe_c2m2: SITUATION
- api_1164: Sec 9
- awia: AWWA Sec 5
- iaea_nss: Sec 5.5
OSA's mapping for nerc_cip takes NIST and NERC Security Working Group's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance: /api/v1/controls/SC-48
- Clauses only: /api/v1/controls/SC-48?fields=mappings
- Page for people: /controls/sc-48/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.
