AST-08.1: Configuration Management Database (CMDB)
Mechanisms exist to implement and manage a Configuration Management Database (CMDB), or similar technology, to monitor and govern technology asset-specific information.
Renumbered: Formerly AST-02.9 in SCF 2025.4.
Control Question: Does the organization implement and manage a Configuration Management Database (CMDB), or similar technology, to monitor and govern technology asset-specific information?
General (24)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 2.1 2.4 |
| CIS CSC 8.1 IG1 | 2.1 |
| CIS CSC 8.1 IG2 | 2.1 2.4 |
| CIS CSC 8.1 IG3 | 2.1 2.4 |
| COBIT 2019 | EDM05.02 EDM05.03 BAI10.02 BAI10.03 |
| CSA IoT SCF 2 | SNT-04 |
| GovRAMP | CM-08(02) |
| GovRAMP High | CM-08(02) |
| ISO 27002 2022 | 8.9 |
| ISO 27018 2025 | 8.9 |
| MPA Content Security Program 5.3.1 | TS-5.0 |
| NIST 800-53 R4 | CM-8(2) |
| NIST 800-53 R5.2 | CM-08(02) CM-08(07) |
| NIST 800-53B R5 (high) (source) | CM-08(02) |
| NIST SP 800-66 R2 | 164.310(d) |
| NIST 800-82 R3 | CM-08(02) CM-08(07) |
| NIST 800-82 R3 HIGH OT Overlay | CM-08(02) |
| NIST 800-161 R1 | CM-8(2) CM-8(7) |
| NIST 800-161 R1 Level 3 | CM-8(2) CM-8(7) |
| NIST 800-171 R3 (source) | 03.04.08.a 03.04.10.a 03.04.10.b |
| NIST 800-171A R3 (source) | A.03.04.08.a A.03.04.10.a A.03.04.10.b[02] |
| NIST 800-172 R3 | 03.04.03E 03.04.08E |
| NIST 800-172A R3 | DS-A.03.04.03E[01] A.03.04.03E.ODP[01] DS-A.03.04.03E[02] A.03.04.03E.ODP[02] DS-A.03.04.03E[03] A.03.04.03E.ODP[03] DS-A.03.04.04E[01] DS-A.03.04.04E[02] DS-A.03.04.04E[03] DS-A.03.04.08E |
| NIST 800-207 | NIST Tenet 1 NIST Tenet 6 NIST Tenet 7 |
US (8)
| Framework | Mapping Values |
|---|---|
| USA Federal C2M2 2.1 | ASSET-1d ASSET-2e ASSET-2g |
| USA Federal CERT RMM 1.2 | ADM:SG3.SP1 ADM:SG3.SP2 |
| USA Federal CMMC 2.0 Level 3 | CM.L3-3.4.1E CM.L3-3.4.3E |
| USA Federal DoD Zero Trust Reference Architecture 2.0 | 2.2.1 |
| USA Federal DoD Zero Trust Execution Roadmap v1.1 | 2.1.1 |
| USA Federal FedRAMP R5 (high) | CM-08(02) |
| USA Federal HIPAA Security Rule NIST SP 800-66 R2 | § 164.310(d)(2)(iii) |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.310(d)(2)(iii) |
EMEA (11)
| Framework | Mapping Values |
|---|---|
| EMEA CHE FINMA Circular 2023/1 | IV.B.c-54 |
| EMEA Spain CCN-STIC 825 | op.exp.2 op.exp.3 |
| EMEA EU EBA GL/2019/04 | 3.5.54 |
| EMEA UK DEFSTAN 05-138 2024 | 1301 2423 |
| EMEA UK DEFSTAN 05-138 - L1 2024 | 2423 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 1301 2423 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 1301 2423 |
| EMEA LUX CCSF 20/750 2020 | 3.5-53 |
| EMEA Saudi Arabia IoT CGIoT-1 2024 | 2-1-2 |
| EMEA Saudi Arabia OTCC-1 2022 | 2-1-1-2 |
| EMEA Saudi Arabia SAMA CSF 1.0 2017 | 3.3.3.3 3.3.3.3.a 3.3.3.3.b 3.3.3.3.c 3.3.3.3.d 3.3.3.3.e |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1493 |
| APAC Malaysia RMiT 2025 | 11.3(h) |
| APAC New Zealand NZISM 3.9 | 20.2.15.C.07 |
Americas (3)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.04.08.A 03.04.10.A 03.04.10.B |
| Americas Canada OSFI B-13 2022 | 2.2.3 |
| Americas Canada OSFI Self-Assessment Guidance | 2.2.2 2.2.3 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).
Level 3 — Well Defined
Asset Management (AST) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with AST domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with AST domain capabilities are well-documented and kept current by process owners. ▪ An IT Asset Management (ITAM) team, or similar function, is appropriately staffed and supported to implement and maintain AST domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of ITAM operations (e.g., ITAM platform, (e.g., Configuration Management Database (CMBD) Asset Management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with AST domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to implement and manage a Configuration Management Database (CMDB), or similar technology, to monitor and govern technology asset-specific information.
Level 4 — Quantitatively Controlled
Asset Management (AST) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- AST-08.1_A01 a centralized repository for the system and system component inventory is provided.
- AST-08.1_A02 automated mechanisms used to maintain the currency of the system component inventory are defined.
- AST-08.1_A03 automated mechanisms used to maintain the completeness of the system component inventory are defined.
- AST-08.1_A04 automated mechanisms used to maintain the accuracy of the system component inventory are defined.
- AST-08.1_A05 automated mechanisms used to maintain the availability of the system component inventory are defined.
Technology Recommendations
Micro/Small
- Configuration Management Database (CMDB)
Small
- Configuration Management Database (CMDB)
Medium
- Configuration Management Database (CMDB)
Large
- Configuration Management Database (CMDB)
Enterprise
- Configuration Management Database (CMDB)