Requirement text: CM.2.061: Establish and maintain baseline configurations and inventories of
organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2
This requirement establishes and maintains baseline configurations for systems and system
components including for system communications and connectivity. Baseline configurations
are documented, formally reviewed, and agreed-upon sets of specifications for systems or
configuration items within those systems. Baseline configurations serve as a basis for future
builds, releases, and changes to systems. Baseline configurations include information about
system components (e.g., standard software packages installed on workstations, notebook
computers, servers, network components, or mobile devices; current version numbers and
update and patch information on operating systems and applications; and configuration
settings and parameters), network topology, and the logical placement of those components
within the system architecture. Baseline configurations of systems also reflect the current
enterprise architecture. Maintaining effective baseline configurations requires creating new
baselines as organizational systems change over time. Baseline configuration maintenance
includes reviewing and updating the baseline configuration when changes are made based
on security risks and deviations from the established baseline configuration.
Organizations can implement centralized system component inventories that include
components from multiple organizational systems. In such situations, organizations ensure
that the resulting inventories include system-specific information required for proper
component accountability (e.g., system association, system owner). Information deemed
necessary for effective accountability of system components includes hardware inventory
specifications, software license information, software version numbers, component owners,
and for networked components or devices, machine names and network addresses.
Inventory specifications include manufacturer, device type, model, serial number, and
physical location.
NIST SP 800-128 provides guidance on security-focused configuration management.
CMMC CLARIFICATION
Build and configure systems from a known, secure, and approved configuration baseline.
This includes:
• documenting the software and configuration settings of a system;
• placement within the network; and
• other specifications as required by the organization.
An effective cybersecurity program depends on system and component configuration and
management.
Example
You are in charge of upgrading the computer operating systems of your office’s 10 machines.
You research how to setup and configure a machine with the least functionality and highest
security. The setup must allow users to do their tasks. You document this configuration.
Then, you apply it to the other nine machines. You understand the baseline configuration of
every machine. This helps when you need to install new patches, software, or make changes.
References
• NIST SP 800-171 Rev 1 3.4.1
• CIS Controls v7.1 1.4, 1.5, 2.1, 2.4, 5.1
• NIST CSF v1.1 ID.AM-1, ID.AM-2, PR.DS-3, PR.DS-7, PR.IP-1, DE.AE-1
• CERT RMM v1.2 KIM:SG5.SP2
• NIST SP 800-53 Rev 4 CM-2, CM-6, CM-8, CM-8(1)
• UK NCSC Cyber Essentials