Skip to main content

AST-16.1: Compliance-Specific Asset Identification

AST 6 — Medium Identify

Mechanisms exist to create and maintain a current inventory of Technology Assets, Applications, Services and/or Data (TAASD) that are in scope for statutory, regulatory and/or contractual compliance obligations providing sufficient detail to determine control applicability, based on asset scope categorization.

Renumbered: Formerly AST-04.3 in SCF 2025.4.

Control Question: Does the organization create and maintain a current inventory of Technology Assets, Applications, Services and/or Data (TAASD) that are in scope for statutory, regulatory and/or contractual compliance obligations that provides sufficient detail to determine control applicability, based on asset scope categorization?

General (6)
Framework Mapping Values
NIST 800-171 R3 (source) 03.01.03
NIST 800-171A R3 (source) A.03.01.03[02]
PCI DSS 4.0.1 (source) 6.3.2 12.5.1 12.5.2.1 A3.2.5
PCI DSS 4.0.1 SAQ A-EP (source) 6.3.2
PCI DSS 4.0.1 SAQ D Merchant (source) 6.3.2 12.5.1
PCI DSS 4.0.1 SAQ D Service Provider (source) 6.3.2 12.5.1 12.5.2.1
EMEA (1)
Framework Mapping Values
EMEA EU NIS2 Annex 2024 12.4.2(a) 12.4.2(b)
APAC (1)
Framework Mapping Values
APAC India RBI PA 2025 Annex 1.1.5
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.01.03

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

Asset Management (AST) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with AST domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Asset management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Asset management is informally assigned as an additional duty to existing IT/cybersecurity personnel.

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 create and maintain a current inventory of TAASD that are in scope for statutory, regulatory and/or contractual compliance obligations that provides sufficient detail to determine control applicability, based on asset scope categorization.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

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

  1. AST-16.1_A01 an inventory of systems, applications and services exists for each statutory, regulatory and/or contractual compliance obligation and provides sufficient detail to determine control applicability, based on asset scope categorization.
  2. AST-16.1_A02 inventories of systems, applications and services are reviewed and updated per an organization-defined frequency for each statutory, regulatory and/or contractual compliance obligation, providing sufficient detail to determine control applicability, based on asset scope categorization.

Evidence Requirements

E-AST-02 Asset Scoping Guidance

Documented evidence of an asset scoping guidance. This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on defining in-scope Technology Assets, Applications, Services and/or Data (TAASD) (including third-parties).

Asset Management
E-CPL-02 Defined Compliance Scope (DCS)

Documented evidence of a formal scoping document that identifies applicable statutory, regulatory and/or contractual obligations for the organization. Defines the affected Lines of Business (LOB), internal / external stakeholders and facilities for the specific scope of compliance obligations.

Compliance

Technology Recommendations

Micro/Small

  • Unified Scoping Guide (https://unified-scoping-guide.com)

Small

  • Unified Scoping Guide (https://unified-scoping-guide.com)

Medium

  • Unified Scoping Guide (https://unified-scoping-guide.com)

Large

  • Unified Scoping Guide (https://unified-scoping-guide.com)

Enterprise

  • Unified Scoping Guide (https://unified-scoping-guide.com)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.