How many SPRS points can the Configuration Management family cost?

Up to 33 of the 313 points a score can lose: 6 worth 5 points and 3 worth 1.

Which Configuration Management requirements can go on a CMMC POA&M?

3 of the 9: 3.4.3, 3.4.4 and 3.4.9, worth 1 point each. The others are worth more than 1 point, which 32 CFR 170.21(a)(2)(ii) does not admit. The score must also be at least 88.

NIST 800-171 3.4 Configuration Management

Configuration Management keeps the system in a known state: documented baselines and inventories, enforced security settings, changes reviewed before they happen, and only the software and services the mission needs.

9 requirementsup to 33 SPRS points3 can go on a CMMC POA&MPublished 2026-11-11

The 9 Configuration Management requirements

3.4.1 Baseline and InventoryCM.L2-3.4.1Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.5 points
3.4.2 Security SettingsCM.L2-3.4.2Establish and enforce security configuration settings for information technology products employed in organizational systems.5 points
3.4.3 Change ControlCM.L2-3.4.3Track, review, approve or disapprove, and log changes to organizational systems.1 point
3.4.4 Security Impact AnalysisCM.L2-3.4.4Analyze the security impact of changes prior to implementation.1 point
3.4.5 Change Access LimitsCM.L2-3.4.5Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.5 points
3.4.6 Least FunctionalityCM.L2-3.4.6Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.5 points
3.4.7 Nonessential ServicesCM.L2-3.4.7Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.5 points
3.4.8 Application ExecutionCM.L2-3.4.8Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.5 points
3.4.9 User-Installed SoftwareCM.L2-3.4.9Control and monitor user-installed software.1 point

Configuration Management: points and the CMMC POA&M

Q-01
How many SPRS points can the Configuration Management family cost?
Up to 33 of the 313 points a score can lose: 6 worth 5 points and 3 worth 1.
Q-02
Which Configuration Management requirements can go on a CMMC POA&M?
3 of the 9: 3.4.3, 3.4.4 and 3.4.9, worth 1 point each. The others are worth more than 1 point, which 32 CFR 170.21(a)(2)(ii) does not admit. The score must also be at least 88.

Related pages

Calculator: SPRS score calculator: mark the Configuration Management requirements and see what they cost.
Sample package: Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.
Previous family: 3.3 Audit and Accountability
Next family: 3.5 Identification and Authentication
All requirements: All 110 NIST SP 800-171 requirements, by family.

Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages, the architecture page, and the two pages on authorization.

proof.state: Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
proof.change: Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
proof.agency: Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
architecture: Architecture. How the chain is built and where the evidence is stored in each delivery mode.
authorization: Continuous ATO. How an authorizing official's decision is recorded with its package, and how the authorized system is checked against it every hour.
baseline: NIST SP 800-53. The Low, Moderate and High baselines as evidence, with the SSP, SAR and POA&M generated from one record.