# CM-08 System Component Inventory

NIST SP 800-53 control. Family: CM Configuration Management. Function: preventative. Baselines: low, moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: a. Develop and document an inventory of system components that: 1. Accurately reflects the system; 2. Includes all components within the system; 3. Does not include duplicate accounting of components or components assigned to any other system; 4. Is at the level of granularity deemed necessary for tracking and reporting; and 5. Includes the following information to achieve system component accountability: [Assignment: organization-defined information deemed necessary to achieve effective system component accountability]; and b. Review and update the system component inventory [Assignment: organization-defined frequency].
Guidance: 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-08(07) can help to eliminate duplicate accounting of components.

## Enhancements (8)
- CM-08(01) Updates During Installation and Removal. Baselines: moderate, high
- CM-08(02) Automated Maintenance. Baselines: high
- CM-08(03) Automated Unauthorized Component Detection. Baselines: moderate, high
- CM-08(04) Accountability Information. Baselines: high
- CM-08(06) Assessed Configurations and Approved Deviations
- CM-08(07) Centralized Repository
- CM-08(08) Automated Location Tracking
- CM-08(09) Assignment of Components to Systems
Withdrawn by NIST: CM-08(05) (now in CM-08).
Each enhancement's statement: /api/v1/controls/CM-08?fields=enhancements

## Patterns that use it (17)
- Critical (4): SP-030 API Security; SP-038 Vulnerability Management and Patching; SP-040 Post-Quantum Cryptography and Quantum Readiness; SP-046 External Attack Surface Management
- Important (13): SP-001 Client Module; SP-002 Server Module; SP-015 Secure Remote Working; SP-017 Secure Network Zone Module; SP-026 PCI Full Environment; SP-029 Zero Trust Architecture; SP-044 SaaS Identity Lifecycle Management; SP-047 Secure Agentic AI Frameworks; SP-049 AI in Security Operations (draft); SP-050 Mobile Security Architecture (draft); SP-051 Tokenised Asset Security Architecture (draft); SP-053 Zero-Knowledge Proof Architecture (draft); SP-054 CBDC and Digital Currency Infrastructure (draft)

## Clauses by framework (75 frameworks)
- iso_27001_2022: A.5.9, A.8.9
- iso_27002_2022: 5.9, 5.37, 8.1, 8.9
- cobit_2019: BAI09, BAI10
- pci_dss_v4: 11.2, 12.5
- nist_csf_2: ID.AM-01, ID.AM-02, ID.AM-07, ID.AM-08, PR.PS-01, PR.PS-03. OSA's own, not in NIST's crosswalk: ID.AM-07, ID.AM-08, PR.PS-03
- cis_controls_v8: CIS 1, CIS 1.1, CIS 1.2, CIS 1.3, CIS 1.5, CIS 2, CIS 2.1, CIS 2.4, CIS 3.2, CIS 16.4
- soc2_tsc: CC6.1-POF1
- finos_ccc: CCC-C06
- iso_42001_2023: A.4.2, A.4.4
- asd_e8: E8-2 ML3, E8-6 ML3
- nis2: Art. 21(2)(i)
- apra_cps_234: Para 21
- pra_op_resilience: SS1/21-5.2, SS2/21-13.1
- anssi: Hygiene.5, Hygiene.8, SecNumCloud.9.1
- osfi_b13: B-13.2.1, B-13.3.1
- finma_circular: IV.A(28), IV.A(29), IV.A(30), IV.B.c(54), IV.B.c(55)
- gdpr: Art.30(1), Art.35(7)(a)
- dora: Art.8(1), Art.8(4), Art.28(4)
- bio2: 5.9, 5.37, 8.1, 8.9
- rbi_csf: Annex1.1, ITGRCA.9
- fisc: FISC.O9, FISC.O13, FISC.T7
- lgpd_bcb: BCB.Art.20
- mlps_2: 8.1.10.1, 8.1.10.6, 8.2, 8.3
- dnb_good_practice: DNB.6.1, DNB.13.1, DNB.13.2, DNB.19.3
- cra: CRA.II.1, CRA.Info.3
- swift_cscf: SWIFT.2.7
- cbuae: CR-7
- nca_ecc: 2-1, 2-6
- qatar_nia: AM, OS
- sama_csf: 2.1
- uae_ia: T4, T7
- bog_cisd: CISD-V
- bom_ctrm: 2.1, 3.2, 3.7
- cbe_csf: CRM-2
- cbn_csf: Part3.1
- popia: s17
- sa_js2: JS2-6.1, JS2-7.2
- bcbs_239: Principle 2, Principle 4
- bot_cyber: Ch2.1
- cpmi_pfmi: CG.ID, PFMI.P17
- eba_ict: 3.3.2, 3.4.4, 3.5(a), 3.5(b)
- ecb_croe: CROE.2.2.2
- ffiec_is: II.C.5, II.C.11, II.C.13(e)
- hipaa_sr: §164.310(d)(2)(iii)
- iosco_cyber: ID-1, ID-2, ID-4
- nydfs_500: 500.13
- sebi_cscrf: ID.AM
- cmmc_2: CM
- nerc_cip: CIP-010-4
- nrc_73_54: RG5.71-B-CM
- ieee_1686: 5.4
- doe_c2m2: ASSET
- awia: AWWA Sec 2
- pci_pts: K
- cbest: CBEST.3
- pci_hsm: 2
- isae_3402: Clause 9
- fca_sysc_13: SYSC 13.7.1, SYSC 13.7.2
- fda_21_cfr_11: §11.10(h)
- fda_cyber: 524B-1, SBOM-1, SBOM-2, SBOM-3, ST-4
- hitrust_csf: 05.c, 07.a, 10.e
- iso_27799: 8.1, 11.2, H.3
- lloyds_ms: MS1.1, MS8.4, MS9.3
- naic_ds: 3, 4-asset
- nhs_dspt: NDG-5.3, NDG-8.1, NDG-8.3, NDG-9.7
- pra_ss1_23: P1.1, P1.3, P5.5, P-IT.3
- solvency_ii: DR.266-DataSec, EIOPA-ICT-4.3
- owasp_masvs_v2: MASVS-CODE-3
- csa_ccm_v4: CEK-21, DCS-05, DCS-06, DCS-08, DSP-03, STA-07, UEM-04, UEM-12
- csa_aicm: CEK-21, DCS-05, DCS-06, DCS-08, DSP-03, MDS-02, STA-07, STA-15, UEM-04, UEM-12
- ccss_v9: 1.02.3, 1.04.5
- mica: Art.40(1), Art.63(2), Art.82(1)
- basel_sco60: SCO60.14, SCO60.51, SCO60.65
- bssc: GSP-14, NOS-03
- sec_custody_digital: SEC-CD-04, SEC-CD-09, SEC-CD-18
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/CM-08
- Clauses only: /api/v1/controls/CM-08?fields=mappings
- Page for people: /controls/cm-08/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.