← Controls / CM

CM-02 Baseline Configuration

Configuration Management

Low Moderate High

Description

a. Develop, document, and maintain under configuration control, a current baseline configuration of the system; and b. Review and update the baseline configuration of the system: 1. [Assignment: organization-defined frequency]; 2. When required due to [Assignment: organization-defined circumstances]; and 3. When system components are installed or upgraded.

Supplemental Guidance

Baseline configurations for systems and system components include connectivity, operational, and communications aspects of systems. Baseline configurations are documented, formally reviewed, and agreed-upon specifications for systems or configuration items within those systems. Baseline configurations serve as a basis for future builds, releases, or changes to systems and include security and privacy control implementations, operational procedures, information about system components, network topology, and logical placement of components in the system architecture. Maintaining baseline configurations requires creating new baselines as organizational systems change over time. Baseline configurations of systems reflect the current enterprise architecture.

Changes from Rev 4

Adds requirement to update baseline configuration document at organizationally-defined frequencies and for organizationally-defined circumstances (in addition to when changes are made) Incorporates withdrawn control CM-02(1)

Enhancements (4)

What NIST adds to this control. Select one to read its statement.

CM-02(02) Automation Support for Accuracy and Currency ModerateHigh

Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using [Assignment: organization-defined automated mechanisms].

CM-02(03) Retention of Previous Configurations ModerateHigh

Retain [Assignment: organization-defined number] of previous versions of baseline configurations of the system to support rollback.

CM-02(06) Development and Test Environments

Maintain a baseline configuration for system development and test environments that is managed separately from the operational baseline configuration.

CM-02(07) Configure Systems and Components for High-risk Areas ModerateHigh

a. Issue [Assignment: organization-defined systems or system components] with [Assignment: organization-defined configurations] to individuals traveling to locations that the organization deems to be of significant risk; and b. Apply the following controls to the systems or components when the individuals return from travel: [Assignment: organization-defined controls].

Withdrawn by NIST:

  • CM-02(01) Reviews and Updates, now in CM-02
  • CM-02(04) Unauthorized Software, now in CM-07(04)
  • CM-02(05) Authorized Software, now in CM-07(05)

MITRE ATT&CK Techniques (285)

ATT&CK v20.0

Techniques this control mitigates in the CTID mapping of SP 800-53, made for ATT&CK 16.1 and carried to v20.0. See them all in the ATT&CK matrix.

Reconnaissance 3 Initial Access 8 Execution 40 Persistence 53 Privilege Escalation 35 Stealth 53 Defense Impairment 26 Credential Access 39 Discovery 4 Lateral Movement 17 Collection 19 Command and Control 31 Exfiltration 10 Impact 13
Show all 285 techniques grouped by tactic

Execution

Persistence

Privilege Escalation

Stealth

T1027 T1036 T1036.001 T1036.003 T1036.005 T1036.007 T1070 T1070.003 T1070.007 T1070.008 T1070.009 T1127 T1127.001 T1127.002 T1134.005 T1205 T1211 T1216 T1216.001 T1216.002 T1218 T1218.001 T1218.002 T1218.003 T1218.004 T1218.005 T1218.007 T1218.008 T1218.009 T1218.012 T1218.013 T1218.014 T1218.015 T1220 T1221 T1542 T1542.003 T1542.004 T1542.005 T1564.006 T1564.007 T1564.009 T1574 T1574.001 T1574.004 T1574.005 T1574.007 T1574.008 T1574.009 T1574.010 T1574.013 T1612 T1622

Defense Impairment

Credential Access

Command and Control

Compliance Mappings

ISO 27001:2022

A.8.9

ISO 27002:2022

5.378.98.31

COBIT 2019

BAI10

CIS Controls v8

CIS 4CIS 4.1CIS 12CIS 16.7

NIST CSF 2.0

PR.PS-01

SOC 2 TSC

CC6.1-POF7CC6.7-POF1CC7.1CC7.1-POF1CC8.1

PCI DSS v4.0.1

1.21.2.12.12.2

CSA CCM v4

AIS-06CCC-06CCC-07IVS-04IVS-05UEM-03UEM-05UEM-07

CSA AICM v1

AIS-06CCC-06CCC-07I&S-04I&S-05UEM-03UEM-05UEM-07

FINOS CCC

CCC-C14

ISO 42001:2023

A.4.2A.6.2.3

IEC 62443

3-3 SR 7.6

NIS2 Directive

Art. 21(2)(g)

MAS TRM

11

BSI IT-Grundschutz

NET.1.2NET.3.1SYS.1.1SYS.2.1

ANSSI

Hygiene.5Hygiene.18SecNumCloud.13.1

FINMA Circular 2023/1

IV.A(28)IV.A(29)IV.A(30)IV.A(31)

OSFI B-13

B-13.2.2

EU GDPR

Art.25(1)Art.32(1)(b)

EU DORA

Art.7(1)Art.9(1)

BIO2

5.378.98.31

RBI CSF

Annex1.5

FISC Security Guidelines

FISC.O3FISC.O13FISC.T7FISC.T14

HKMA TM-E-1

TME1.4.1TME1.4.3

MLPS 2.0

8.1.9.58.1.10.48.1.10.6

DNB Good Practice

DNB.3.2DNB.10.3DNB.10.5DNB.13.1DNB.13.2

EU CRA

CRA.I.2bCRA.Info.3

SWIFT CSCF

SWIFT.2.3

SAMA CSF

3.33.53.84.3

NCA ECC

2-35-1

UAE IA

T7

CBB TM

TM-5

Qatar NIA

OSSD

CBUAE

CR-7

CBE CSF

CTO-7CTO-12

SA JS2

JS2-7.2

CBN CSF

Part3.3

BoG CISD

CISD-VI

POPIA

s19

BoM CTRM

3.13.2

IOSCO Cyber Resilience

ID-4

BCBS 239

Principle 2

CPMI-IOSCO PFMI

CG.PRPFMI.P17

FFIEC IS

II.C.2II.C.10

NYDFS 500

500.8

ECB CROE

CROE.2.3.4

EBA ICT Guidelines

3.4.43.5(a)

SEBI CSCRF

PR.IP

BOT Cyber Resilience

Ch2.1

CMMC 2.0

CM

NERC CIP

CIP-010-4

10 CFR 73.54

RG5.71-B-CM

IEEE 1686-2022

5.4

FERC CIP Orders

Order 887

DOE C2M2 v2.1

ASSET

API 1164

Sec 7

AWIA

AWWA Sec 2

IAEA NSS 17-T

Sec 5.4

PCI PTS v6

K

FIPS 140-3

FIPS 140-3 §7.6

PCI HSM

8

ISAE 3402

Clause 4Clause 9

Solvency II

DR.266EIOPA-ICT-4.8

Lloyd's Minimum Standards

MS8.4

NAIC Insurance Data Security

4-config4B

PRA SS1/23

P3.3P-IT.3

FCA SYSC 13

SYSC 13.7.1SYSC 13.7.2

HITRUST CSF v11

09.a

FDA 21 CFR Part 11

§11.10(f)

FDA Cybersecurity Guidance

PU-2SA-3

ISO 27799

12.1

NHS DSPT

NDG-8.3

OWASP MASVS v2.1

MASVS-CODE-1MASVS-CODE-2

MiCA

Art.62(5)

Basel SCO60

SCO60.14SCO60.51SCO60.65

BSSC Standards

GSP-14NOS-03

SEC Custody (Digital Assets)

SEC-CD-08

ISO 17799 (legacy)

7.1.115.1.2

COBIT 4.1 (legacy)

PO1.6PO2.1DS9.1