03.04.01 Baseline configuration
Developing and keeping a current baseline configuration of the system under configuration control, reviewed at a defined frequency and whenever components are installed or modified.

Rev. 3 configuration management requirements: baselines, hardening settings, change control and impact analysis, least functionality, software allowlisting, component inventory, CUI location and devices for high-risk travel.
Developing and keeping a current baseline configuration of the system under configuration control, reviewed at a defined frequency and whenever components are installed or modified.
Establishing, documenting and implementing the most restrictive configuration settings consistent with operations (hardening baselines), and identifying, documenting and approving any deviations.
Defining which changes are configuration-controlled, reviewing and approving them with security impacts considered, implementing and documenting approved changes, and monitoring change activity.
Analyzing the security impact of system changes before they are implemented and verifying afterwards that the security requirements are still satisfied.
Defining, documenting, approving and enforcing the physical and logical access restrictions that limit who can make changes to the system.
Configuring the system for mission-essential capabilities only, prohibiting or restricting defined functions, ports, protocols, connections and services, and reviewing for and removing unnecessary or nonsecure ones. Rev. 3 folded Rev. 2's 3.4.7 into it.
Application allowlisting: identifying the software authorized to run, enforcing a deny-all, allow-by-exception execution policy and reviewing the authorized list at a defined frequency.
Developing and maintaining an inventory of system components, reviewed at a defined frequency and updated with installations, removals and system updates; a separate requirement for the first time in Rev. 3.
Identifying and documenting where CUI is processed and stored and on which system components, and documenting changes to those locations; new in Rev. 3.
Issuing specially configured systems or components to people traveling to high-risk locations and applying defined security measures to those devices when the travelers return; new in Rev. 3.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.