CM-3: Configuration Change Control
Control Family:
Threats Addressed:
Next Version:
- NIST Special Publication 800-53 Revision 5:
- CM-3: Configuration Change Control
Control Statement
The organization:
- Determines the types of changes to the information system that are configuration-controlled;
- Reviews proposed configuration-controlled changes to the information system and approves or disapproves such changes with explicit consideration for security impact analyses;
- Documents configuration change decisions associated with the information system;
- Implements approved configuration-controlled changes to the information system;
- Retains records of configuration-controlled changes to the information system for [Assignment: organization-defined time period];
- Audits and reviews activities associated with configuration-controlled changes to the information system; and
- Coordinates and provides oversight for configuration change control activities through [Assignment: organization-defined configuration change control element (e.g., committee, board)] that convenes [Selection (one or more): [Assignment: organization-defined frequency]; [Assignment: organization-defined configuration change conditions]].
Supplemental Guidance
Configuration change controls for organizational information systems involve the systematic proposal, justification, implementation, testing, review, and disposition of changes to the systems, including system upgrades and modifications. Configuration change control includes changes to baseline configurations for components and configuration items of information systems, changes to configuration settings for information technology products (e.g., operating systems, applications, firewalls, routers, and mobile devices), unscheduled/unauthorized changes, and changes to remediate vulnerabilities. Typical processes for managing configuration changes to information systems include, for example, Configuration Control Boards that approve proposed changes to systems. For new development information systems or systems undergoing major upgrades, organizations consider including representatives from development organizations on the Configuration Control Boards. Auditing of changes includes activities before and after changes are made to organizational information systems and the auditing activities required to implement such changes.
Control Enhancements
CM-3(1): Automated Document / Notification / Prohibition Of Changes
Baseline(s):
- High
The organization employs automated mechanisms to: Document proposed changes to the information system; Notify [Assignment: organized-defined approval authorities] of proposed changes to the information system and request change approval; Highlight proposed changes to the information system that have not been approved or disapproved by [Assignment: organization-defined time period]; Prohibit changes to the information system until…
CM-3(2): Test / Validate / Document Changes
Baseline(s):
- Moderate
- High
The organization tests, validates, and documents changes to the information system before implementing the changes on the operational system.
CM-3(3): Automated Change Implementation
Baseline(s):
The organization employs automated mechanisms to implement changes to the current information system baseline and deploys the updated baseline across the installed base.
CM-3(4): Security Representative
Baseline(s):
The organization requires an information security representative to be a member of the [Assignment: organization-defined configuration change control element].
CM-3(5): Automated Security Response
Baseline(s):
The information system implements [Assignment: organization-defined security responses] automatically if baseline configurations are changed in an unauthorized manner.
CM-3(6): Cryptography Management
Baseline(s):
The organization ensures that cryptographic mechanisms used to provide [Assignment: organization-defined security safeguards] are under configuration management.