NIST 800-53 REV 5 • CONFIGURATION MANAGEMENT
CM-3(2) — Testing, Validation, and Documentation of Changes
Test, validate, and document changes to the system before finalizing the implementation of the changes.
CMMC Practice Mapping
NIST 800-171 Mapping
Related Controls
No related controls listed
Supplemental Guidance
Changes to systems include modifications to hardware, software, or firmware components and configuration settings defined in [CM-6](#cm-6) . Organizations ensure that testing does not interfere with system operations that support organizational mission and business functions. Individuals or groups conducting tests understand security and privacy policies and procedures, system security and privacy policies and procedures, and the health, safety, and environmental risks associated with specific facilities or processes. Operational systems may need to be taken offline, or replicated to the extent feasible, before testing can be conducted. If systems must be taken offline for testing, the tests are scheduled to occur during planned system outages whenever possible. If the testing cannot be conducted on operational systems, organizations employ compensating controls.
Practitioner Notes
This enhancement requires you to test changes in a non-production environment, validate they work correctly, and document the results before deploying to production.
Example 1: Before applying a Windows update to production servers, deploy it first to your test environment in WSUS or SCCM and verify no application compatibility issues arise during a 48-hour observation period.
Example 2: Require all firewall rule changes to be tested in a lab firewall and documented with before/after screenshots before being applied to production Palo Alto devices.