Join our Newsletter — 33% off our NHI Course
Home› Guides› NIST SP 800-53 CM Configuration Management: Key Controls,…
Guide Endpoint Security

NIST SP 800-53 CM Configuration Management: Key Controls, Enhancements and How to Evidence Them

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 16 min read
On this page

Configuration Management (CM) findings rarely come from a missing tool; they come from baselines that exist only as a hardening document, change records that cannot be matched to what actually changed, and inventories that disagree with the network. The CM family in NIST SP 800-53 Rev. 5 has 14 base controls, and together they decide whether you can prove what a system should look like, who changed it and whether anything unauthorised is running. This guide works through the family control by control: what each requires, which baselines select it and its enhancements, the parameters you must set and the evidence an assessor expects. It is written for control owners, platform and endpoint teams, system security plan authors and assessors. For the configuration management process itself (planning, baselines, change control and monitoring as a workflow), see the NIST SP 800-128 Security-Focused Configuration Management Guide; for the catalogue as a whole, see the NIST SP 800-53 Guide.

Key takeaways

  • Low already asks a lot. The Low baseline selects nine CM base controls (CM-1, CM-2, CM-4, CM-5, CM-6, CM-7, CM-8, CM-10 and CM-11). Formal change control (CM-3) and a configuration management plan (CM-9) start at Moderate.
  • Moderate is where automation begins. CM-2(2), CM-7(2), CM-7(5) and CM-8(3) at Moderate expect automated baseline maintenance, prevention of unauthorised program execution, an allow-list of software and automated detection of unauthorised components.
  • Evidence is a comparison, not a document. Assessors test CM by comparing the documented baseline, the change records and the inventory with the live system. A hardening standard without a drift report proves only intent.
  • Parameters carry the control. Review frequencies in CM-2, record retention in CM-3, the number of retained baselines in CM-2(3) and the review period in CM-7(1) are yours to set and are tested against the value you wrote down.
  • Who can change matters as much as what changes. CM-5 restricts access for change. Pipeline service accounts, configuration management agents and infrastructure-as-code deploy roles are the identities that make most production changes and must be inside that boundary.

The CM family at a glance

Baseline allocation is from NIST's OSCAL Release 5.2.0 baseline profiles (L = Low, M = Moderate, H = High). CM-13 Data Action Mapping and CM-14 Signed Components are not in the Low, Moderate or High baselines; the privacy baseline selects CM-1 and CM-4.

ControlTitleBaselinesEnhancements selected in baselines
CM-1Policy and ProceduresL, M, HNone
CM-2Baseline ConfigurationL, M, H(2), (3), (7) at M, H
CM-3Configuration Change ControlM, H(2), (4) at M, H; (1), (6) at H
CM-4Impact AnalysesL, M, H(2) at M, H; (1) at H
CM-5Access Restrictions for ChangeL, M, H(1) at H
CM-6Configuration SettingsL, M, H(1), (2) at H
CM-7Least FunctionalityL, M, H(1), (2), (5) at M, H
CM-8System Component InventoryL, M, H(1), (3) at M, H; (2), (4) at H
CM-9Configuration Management PlanM, HNone
CM-10Software Usage RestrictionsL, M, HNone
CM-11User-installed SoftwareL, M, HNone
CM-12Information LocationM, H(1) at M, H
CM-13Data Action MappingNoneNone
CM-14Signed ComponentsNoneNone

Several Rev. 4 enhancements are withdrawn in Rev. 5 and should not appear in a new system security plan: CM-2(1), CM-2(4), CM-2(5), CM-5(2), CM-5(3), CM-5(7), CM-6(3), CM-6(4), CM-8(5) and CM-11(1). Their intent moved into other controls, for example CM-2(1) into CM-2 itself. To choose or tailor a baseline, see the NIST SP 800-53B Control Baselines and Tailoring Guide.

CM-2 and CM-6: baselines and configuration settings

CM-2 Baseline Configuration asks you to develop, document and maintain under configuration control a current baseline configuration of the system, and to review and update it at a frequency you set, when circumstances you define require it, and when components are installed or upgraded. The baseline is the approved state: operating system builds, installed software and versions, network topology, and the settings applied to each component type.

CM-6 Configuration Settings is the detail inside the baseline. It requires settings that "reflect the most restrictive mode consistent with operational requirements" using common secure configurations you name, implementation of those settings, documented and approved deviations, and monitoring and control of changes to settings. In practice the named secure configurations are CIS Benchmarks, DISA STIGs or vendor security baselines. See the CIS Benchmarks vs DISA STIGs comparison.

Item or enhancementParameter you must setValue NHI Mgmt Group recommends
CM-2 b.1 reviewBaseline review frequencyAnnually for the full baseline; quarterly for internet-facing component types
CM-2 b.2 triggersCircumstances that require an updateNew benchmark release, significant incident, platform end of support, major architecture change
CM-2(2) automation (M, H)Automated mechanisms that keep the baseline currentVersion-controlled build definitions (golden images, configuration management code) with the repository as the record
CM-2(3) retention (M, H)Number of previous baselines kept for rollbackAt least the last three, and every version deployed in the last 12 months
CM-2(7) high-risk travel (M, H)Systems, configurations and controls on returnLoaner devices with a reduced build; reimage on return
CM-6 a. secure configurationsNamed common secure configurationsOne named benchmark and level per component type, with version
CM-6 c. deviationsComponents and operational requirements that justify deviationsPer-setting exception register with owner, reason and expiry
CM-6(1) automation (H)Components and mechanisms for managing and verifying settingsEndpoint management or configuration management tooling plus a compliance scanner
CM-6(2) response (H)Settings and actions on unauthorised changeAutomatic revert for critical settings and an alert to the security operations queue

The values are our recommendations, not NIST text; set your own and record them in the system security plan. Detecting and correcting drift is covered in the Configuration Drift and Baseline Enforcement Guide.

CM-3, CM-4 and CM-5: change control, impact analysis and who may change

CM-3 Configuration Change Control (M, H) has seven parts: decide which changes are configuration-controlled, review and approve or disapprove them "with explicit consideration for security and privacy impact analyses", document decisions, implement approved changes, retain records for a period you set, monitor change activity, and coordinate through a configuration change control element (a board or equivalent) that meets at a frequency or on conditions you define.

  • CM-3(2) Testing, Validation, and Documentation of Changes (M, H): test, validate and document changes before finalising them.
  • CM-3(4) Security and Privacy Representatives (M, H): named security and privacy representatives sit on the change control element.
  • CM-3(1) Automated Documentation, Notification, and Prohibition of Changes (H): automated mechanisms document proposed changes, notify approvers, highlight changes not decided within a set period, prohibit changes until approved, document all changes and notify people when changes complete. A protected branch with required reviewers and a deployment gate meets most of this in a pipeline.
  • CM-3(6) Cryptography Management (H): the cryptographic mechanisms behind named controls are under configuration management, which includes certificate and key configuration.

CM-4 Impact Analyses (L, M, H) requires analysis of the potential security and privacy impact of changes before implementation. CM-4(2) Verification of Controls (M, H) adds the step most often skipped: after the change, verify that the affected controls are still implemented correctly, operating as intended and producing the desired outcome. CM-4(1) Separate Test Environments (H) requires the analysis to happen in a separate test environment; see the Environment Separation guide.

CM-5 Access Restrictions for Change (L, M, H) requires you to define, document, approve and enforce physical and logical access restrictions associated with changes. CM-5(1) (H) adds automated enforcement and automatic audit records of enforcement actions. Optional enhancements worth considering by tailoring are CM-5(4) Dual Authorization and CM-5(5) Privilege Limitation for Production and Operation, which limits and periodically re-evaluates privileges to change production.

Where identity fits

CM-5 is an access control applied to change. In most estates the identities with change rights are no longer only administrators: they include CI/CD service accounts, infrastructure-as-code deploy roles, configuration management agents running as root or SYSTEM, and API keys held by automation platforms. Each needs an owner, a documented scope that matches CM-5, and a place in the account reviews required by AC-2. A pipeline role that can deploy to production without the approvals in CM-3 is a CM-5 finding, however good the change process looks on paper. See the Service Account Security Guide and the Segregation of Duties Guide.

CM-7, CM-10, CM-11 and CM-14: least functionality and software control

CM-7 Least Functionality (L, M, H) requires the system to provide only mission-essential capabilities and to prohibit or restrict the functions, ports, protocols, software and services you list. Moderate adds three enhancements:

  • CM-7(1) Periodic Review: review the system at a frequency you set to find unnecessary or non-secure functions, ports, protocols, software and services, and disable or remove them.
  • CM-7(2) Prevent Program Execution: prevent program execution according to your policies or to the rules authorising software usage.
  • CM-7(5) Authorized Software, Allow-by-exception: identify authorised software, apply a deny-all, permit-by-exception policy and review the list at a frequency you set. CM-7(4) is the weaker deny-by-exception alternative and is not selected in any baseline.

CM-7(5) is the control that turns application allowlisting from good practice into a Moderate requirement. See the Application Allowlisting Guide.

CM-10 Software Usage Restrictions covers licence compliance, tracking quantity-licensed software and controlling peer-to-peer file sharing. CM-11 User-installed Software requires a policy on user installation, enforcement methods you name, and compliance monitoring at a set frequency; removing local administrator rights is the usual enforcement method. CM-14 Signed Components, outside the baselines, prevents installation of named software and firmware unless it is signed with an approved certificate, and is a sensible tailoring addition for firmware and driver control.

CM-8, CM-9 and CM-12: inventory, plan and information location

CM-8 System Component Inventory (L, M, H) requires an inventory that accurately reflects the system, includes all components, avoids duplicate accounting across systems, is at a useful level of granularity, and holds the accountability information you specify, reviewed at a frequency you set. CM-8(1) (M, H) updates it during installation and removal. CM-8(3) (M, H) detects unauthorised hardware, software and firmware with automated mechanisms at a set frequency and takes a defined action: disable network access, isolate, or notify named people. High adds CM-8(2) automated maintenance and CM-8(4) accountability information naming who administers each component.

CM-9 Configuration Management Plan (M, H) must address roles and processes, define how configuration items are identified across the life cycle, define the configuration items and place them under configuration management, be reviewed and approved by named roles, and be protected from unauthorised disclosure and modification. SP 800-128 supplies the structure for this plan.

CM-12 Information Location (M, H) requires you to document where named information is processed and stored, who has access to those components, and changes of location. CM-12(1) (M, H) uses automated tools to find information by type, which in practice means data discovery or classification scanning.

For running the inventory itself, see the Asset Inventory and CMDB Security Guide.

How to evidence the CM family

SP 800-53A assessment procedures use three methods: examine (documents, records, configurations), interview (people) and test (exercise the mechanism). The table lists the evidence that usually satisfies each, and the test an assessor is most likely to run.

ControlExamineLikely test
CM-1CM policy and procedures with approval dates and named officialCheck review date against the frequency you set
CM-2, CM-2(2), (3)Baseline definitions in version control, history of previous baselinesPick a component and compare its build to the current baseline version
CM-3, CM-3(2), (4)Change records, board minutes, test results, list of controlled change typesTake a sample of changes from system logs and trace each to an approved record
CM-4, CM-4(2)Impact analysis entries and post-change verification recordsFor a sampled change, confirm the verification step happened and was recorded
CM-5, CM-5(1)List of identities with change rights, including service accounts; access approval recordsCompare the list with actual role assignments in the platform and pipeline
CM-6, CM-6(1)Named benchmark per component type, exception register, compliance scan reportsRun or review a compliance scan and match failures to approved exceptions
CM-7, CM-7(1), (2), (5)Prohibited ports and services list, review records, allowlist policyPort scan or service listing; attempt to run an unapproved binary on a test host
CM-8, CM-8(1), (3)Inventory export, discovery tool reports, unauthorised component alertsCompare a network discovery result with the inventory; check one alert was actioned
CM-9Approved CM plan listing configuration itemsCheck that the items in the plan match those in the repository and inventory
CM-10, CM-11Licence records, user installation policy, endpoint privilege settingsAttempt a standard-user installation on a test endpoint
CM-12, CM-12(1)Data location records, discovery scan resultsCompare a discovery scan with the documented locations

Implementing the family in order

  1. Start with the inventory (CM-8): no baseline, change or allowlist control works without knowing what is in the system boundary. Reconcile discovery data with the CMDB before setting any other parameter.
  2. Write the baseline as code (CM-2, CM-6): pick one benchmark per component type, record deviations, and keep build definitions in version control so CM-2(2) and CM-2(3) come from the repository history.
  3. Measure before enforcing: run compliance scans in report-only mode for one cycle and fix or register every failure before turning on automatic remediation.
  4. Bind change control to the tooling (CM-3, CM-4, CM-5): require approvals in the pipeline, restrict production change rights to the pipeline and a small break-glass group, and record post-change verification.
  5. Close down functionality (CM-7): remove unneeded services, then introduce allowlisting in audit mode on a pilot ring, expand ring by ring and enforce. Keep a documented rollback (switch the policy back to audit) for each ring.
  6. Write the CM plan last (CM-9): describe what you built, not what you hope to build, so the plan matches the evidence.

Decision guidance

  • Low systems: CM-3 is not selected, but CM-4 and CM-5 are, so you still need impact analysis and restricted change access. A lightweight change log with approvals usually satisfies both.
  • Moderate systems: CM-7(5) allowlisting and CM-8(3) unauthorised component detection are the costly items. Budget for them early; they are frequent plan of action items.
  • High systems: CM-3(1), CM-5(1), CM-6(1) and CM-6(2) assume automated enforcement. Manual processes will not meet them at scale.
  • Cloud and containers: treat images, templates and policy-as-code as the baseline, and the deployment pipeline as the CM-3 mechanism. See the Infrastructure as Code Security Guide.

Detection and metrics

  • Baseline compliance rate: percentage of components passing their named benchmark, excluding approved exceptions.
  • Unauthorised change rate: changes detected in logs or drift reports with no matching approved record, per month. Target zero for production.
  • Mean time to revert drift: time from detection of an unauthorised setting change to correction.
  • Inventory accuracy: percentage of discovered components that exist in the inventory, and the reverse.
  • Allowlist coverage: percentage of in-scope endpoints and servers in enforce mode under CM-7(5).
  • Change identities reviewed: percentage of service accounts and pipeline roles with CM-5 change rights that passed their last access review.

Common failure patterns

  • Baseline is a PDF: the hardening standard exists, but no scan shows that systems match it, so CM-2 and CM-6 cannot be tested.
  • Change records cannot be traced from the system side: the assessor samples changes from logs and finds no ticket for automated or emergency changes.
  • Post-change verification missing: CM-4(2) is selected at Moderate but no record shows controls were rechecked after a change.
  • Pipeline identities outside CM-5: deploy roles hold standing administrator rights in production and are absent from the list of identities authorised to change.
  • Withdrawn enhancements in the plan: system security plans copied from Rev. 4 still list CM-2(1) or CM-5(2), signalling the plan was not maintained.
  • Exposed configuration: secrets left in configuration files or repositories reach the public internet when configuration is not controlled. The Twitch Breach 2021 followed a server configuration change that exposed internal repositories and the secrets in them.

Framework mapping

SP 800-53 Rev. 5SP 800-171 Rev. 3NIST CSF 2.0ISO/IEC 27001:2022 Annex ACIS Controls v8.1
CM-2, CM-603.04.01 Baseline Configuration; 03.04.02 Configuration SettingsPR.PS-018.9 Configuration managementControl 4
CM-3, CM-4, CM-503.04.03 Configuration Change Control; 03.04.04 Impact Analyses; 03.04.05 Access Restrictions for ChangePR.PS-018.32 Change managementControl 4
CM-7, CM-1103.04.06 Least Functionality; 03.04.08 Authorized Software, Allow by ExceptionPR.PS-028.19 Installation of software on operational systemsControl 2
CM-803.04.10 System Component InventoryID.AM-02; ID.AM-085.9 Inventory of information and other associated assetsControl 1
CM-1203.04.11 Information LocationID.AM-075.9Control 3
CM-2(7)03.04.12 System and Component Configuration for High-Risk AreasPR.PS-018.1 User endpoint devicesControl 4

For the relationship between the two NIST catalogues, see NIST 800-53 vs 800-171.

Practitioner checklist

  • Confirm which CM controls and enhancements your baseline selects, and remove withdrawn Rev. 4 enhancements from the plan.
  • Set and record every CM parameter, including review frequencies, retention periods and the number of retained baselines.
  • Name one secure configuration benchmark and version per component type, with a deviation register.
  • Keep baselines in version control and produce a drift or compliance report at least monthly.
  • Sample recent changes from system logs and confirm each traces to an approved record with post-change verification.
  • List every identity with change rights, including pipeline and automation accounts, and review it with AC-2.
  • Reconcile network discovery with the inventory and record the action taken on each unauthorised component.
  • Pilot and enforce software allowlisting where CM-7(5) applies.
  • Write or update the CM plan so it describes the mechanisms you actually run.

Standards and references

Related NHI Mgmt Group resources: NIST SP 800-53 Guide, NIST SP 800-128 Security-Focused Configuration Management Guide, NIST SP 800-53B Control Baselines and Tailoring Guide, CIS Control 4 Secure Configuration of Enterprise Assets, Firewall Rule Request Template.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.