| name | CM-8_system-component-inventory |
| description | Develop and document an inventory of system components that: Accurately reflects the system; Includes all components within the system; Does not inclu |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","cm-8","cm"] |
| tech_stack | ["aws","azure","gcp","linux","windows"] |
| cwe_ids | ["CWE-16"] |
| chains_with | ["CM-2","CM-7","CM-9","CM-10","CM-11","CM-13","CP-2","CP-9","MA-2","MA-6"] |
| prerequisites | [] |
| severity_boost | {"CM-2":"Chain with CM-2 for comprehensive security coverage","CM-7":"Chain with CM-7 for comprehensive security coverage","CM-9":"Chain with CM-9 for comprehensive security coverage"} |
CM-8 System Component Inventory
High-Level Description
Family: Configuration Management (CM)
Framework: NIST SP 800-53 Rev 5
System components are discrete, identifiable information technology assets that include hardware, software, and firmware. Organizations may choose to implement centralized system component inventories that include components from all organizational systems. In such situations, organizations ensure that the inventories include system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, hardware inventory specifications, software license information, and for networked components, the machine names and network addresses across all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include date of receipt, cost, model, serial number, manufacturer, supplier information, component type, and physical location.
Preventing duplicate accounting of system components addresses the lack of accountability that occurs when component ownership and system association is not known, especially in large or complex connected systems. Effective prevention of duplicate accounting of system components necessitates use of a unique identifier for each component. For software inventory, centrally managed software that is accessed via other systems is addressed as a component of the system on which it is installed and managed. Software installed on multiple organizational systems and managed at the system level is addressed for each individual system and may appear more than once in a centralized component inventory, necessitating a system association for each software instance in the centralized inventory to avoid duplicate accounting of components. Scanning systems implementing multiple network protocols (e.g., IPv4 and IPv6) can result in duplicate components being identified in different address spaces. The implementation of CM-8(7) can help to eliminate duplicate accounting of components.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CM-8 implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
