# CM-04 Impact Analyses

NIST SP 800-53 control. Family: CM Configuration Management. Function: preventative. Baselines: low, moderate, high, privacy. Mapping licence: CC BY-SA 4.0.

Statement: Analyze changes to the system to determine potential security and privacy impacts prior to change implementation.
Guidance: Organizational personnel with security or privacy responsibilities conduct impact analyses. Individuals conducting impact analyses possess the necessary skills and technical expertise to analyze the changes to systems as well as the security or privacy ramifications. Impact analyses include reviewing security and privacy plans, policies, and procedures to understand control requirements; reviewing system design documentation and operational procedures to understand control implementation and how specific system changes might affect the controls; reviewing the impact of changes on organizational supply chain partners with stakeholders; and determining how potential changes to a system create new risks to the privacy of individuals and the ability of implemented controls to mitigate those risks. Impact analyses also include risk assessments to understand the impact of the changes and determine if additional controls are required.

## Enhancements (2)
- CM-04(01) Separate Test Environments. Baselines: high
- CM-04(02) Verification of Controls. Baselines: moderate, high
Each enhancement's statement: /api/v1/controls/CM-04?fields=enhancements

## Patterns that use it (11)
- Important (9): SP-001 Client Module; SP-002 Server Module; SP-011 Cloud Computing Pattern; SP-012 Secure Software Development Lifecycle; SP-028 Secure DevOps Pipeline Pattern; SP-038 Vulnerability Management and Patching; SP-045 AI Governance and Responsible AI; SP-047 Secure Agentic AI Frameworks; SP-049 AI in Security Operations (draft)
- Standard (2): SP-035 Offensive Security Testing; SP-051 Tokenised Asset Security Architecture (draft)

## Clauses by framework (60 frameworks)
- iso_27001_2022: 6.3, A.5.36, A.8.9, A.8.31, A.8.32. OSA's own, not in NIST's crosswalk: 6.3, A.5.36, A.8.31, A.8.32
- iso_27002_2022: 5.37, 8.9, 8.31, 8.32
- cobit_2019: APO11, BAI05, BAI06, BAI07, BAI10
- pci_dss_v4: 6.5
- nist_csf_2: ID.RA-07, PR.PS-01
- cis_controls_v8: CIS 16.8
- soc2_tsc: CC3.4
- finos_ccc: CCC-C07
- iso_42001_2023: A.6.2.6
- pra_op_resilience: SS1/21-11.1
- bsi_grundschutz: OPS.1.1.3, OPS.1.1.6
- anssi: Hygiene.34, SecNumCloud.13.2
- osfi_b13: B-13.2.3, B-13.3.3
- finma_circular: IV.A(36), IV.A(37), IV.A(38), IV.C(66)
- gdpr: Art.32(1)(d), Art.35(1)
- dora: Art.9(4)(e), Art.25(1)
- bio2: 5.37, 8.9, 8.31, 8.32
- rbi_csf: Annex1.7, ITGRCA.13
- fisc: FISC.O3
- hkma_tme1: TME1.3.2, TME1.3.3, TME1.4.1, TME1.4.3
- mlps_2: 8.1.9.4, 8.1.10.8
- dnb_good_practice: DNB.10.1, DNB.10.2, DNB.10.3, DNB.10.4
- cra: CRA.II.2, CRA.Info.8b
- cbb_tm: TM-5, TM-7, TM-11
- nca_ecc: 2-3
- qatar_nia: OS, SD
- sama_csf: 3.2, 3.5
- uae_ia: T7, T10
- bom_ctrm: 3.6
- cbe_csf: CTO-9, CTO-12
- sa_js2: JS2-8.5
- bcbs_239: Principle 6
- bot_cyber: Ch10.1
- eba_ict: 3.4.6, 3.5(b), 3.6.3
- ecb_croe: CROE.2.3.4
- ffiec_is: II.A.2, II.C.10, II.C.17
- iosco_cyber: PROT-6, TEST-3
- nydfs_500: 500.5, 500.8
- sebi_cscrf: PR.IP
- cmmc_2: CM
- nerc_cip: CIP-010-4
- nrc_73_54: RG5.71-B-CM
- tsa_psd: SD-2 Sec D
- api_1164: Sec 7
- isae_3402: Clause 4
- fca_sysc_13: SYSC 13.7.4, SYSC 13.8.4
- fda_21_cfr_11: §11.10(a)
- fda_cyber: PU-1
- hitrust_csf: 09.a, 10.d
- iso_27799: 12.5, 14.2
- lloyds_ms: MS8.4
- naic_ds: 4-config, 4E
- nhs_dspt: NDG-8.2
- pra_ss1_23: P3.3, P3.4
- solvency_ii: EIOPA-ICT-4.8, EIOPA-ICT-4.11
- csa_ccm_v4: CCC-02, DSP-15, IVS-05
- csa_aicm: CCC-02, DSP-15, I&S-05
- basel_sco60: SCO60.52
- bssc: NOS-10
- dpdpa: Rules.13(3)
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST'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 and ATT&CK techniques: /api/v1/controls/CM-04
- Clauses only: /api/v1/controls/CM-04?fields=mappings
- Page for people: /controls/cm-04/
- 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.