Skip to main content

AST-07: Stakeholder Identification & Involvement

AST 5 — Medium Identify

Mechanisms exist to identify and involve pertinent stakeholders of critical Technology Assets, Applications, Services and/or Data (TAASD) to support the ongoing secure management of those assets.

Renumbered: Formerly AST-01.2 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, AST-07 was Kiosks & Point of Interaction (PoI) Devices. That control is now AST-21.

Control Question: Does the organization identify and involve pertinent stakeholders of critical Technology Assets, Applications, Services and/or Data (TAASD) to support the ongoing secure management of those assets?

General (17)
Framework Mapping Values
COBIT 2019 EDM05.01 EDM05.02 EDM05.03 BAI01.03
ISO 27001 2022 (source) 4.2 4.2(a)
ISO 27002 2022 5.9
ISO 27017 2015 8.1.1
ISO 27018 2025 5.9
ISO 27701 2025 4.2
ISO 42001 2023 9.3.2(c) A.4.6 A.8 A.8.2 A.8.3 A.8.4 A.8.5
NIST AI 100-1 (AI RMF) 1.0 GOVERN 1.1 GOVERN 2.0 GOVERN 5.0
NIST 800-37 R2 TASK P-9
NIST CSF 2.0 (source) GV.OC GV.OC-02 ID.AM ID.AM-08
NIST Privacy Framework 1.0 ID.IM-P8
PCI DSS 4.0.1 (source) 6.5.2
PCI DSS 4.0.1 SAQ A-EP (source) 6.5.2
PCI DSS 4.0.1 SAQ C (source) 6.5.2
PCI DSS 4.0.1 SAQ D Merchant (source) 6.5.2
PCI DSS 4.0.1 SAQ D Service Provider (source) 6.5.2
TISAX ISA 6.0.3 1.2.2 1.3.1
US (3)
Framework Mapping Values
USA Federal CERT RMM 1.2 ADM:GG2.GP7 AM:GG2.GP7 COMM:GG2.GP7 COMP:GG2.GP7 CTRL:GG2.GP7 EC:GG2.GP7 EF:GG2.GP7 EXD:GG2.GP7 FRM:GG2.GP7 HRM:GG2.GP7 ID:GG2.GP7 IMC:GG2.GP7 KIM:GG2.GP7 MA:GG2.GP7 MON:GG2.GP7 OPD:GG2.GP7 OPF:GG2.GP7 OTA:GG2.GP7 PM:GG2.GP7 RISK:GG2.GP7 RRD:GG2.GP7 RRM:GG2.GP7 RTSE:GG2.GP7 SC:GG2.GP7 TM:GG2.GP7 VAR:GG2.GP7 GG2.GP7
USA Federal NERC CIP 2024 CIP-003-8 R3
USA Federal TSA / DHS 1580/82-2022-01 III.A
EMEA (7)
Framework Mapping Values
EMEA Spain CCN-STIC 825 op.pl.2 op.exp.1
EMEA Spain Royal Decree 311 2022 Article 11(1) Article 11(2)
EMEA EU EBA GL/2019/04 3.5.54
EMEA UK CAF 4.0 A3.a (point 4)
EMEA Qatar PDPPL 2020 3.11.2
EMEA Saudi Arabia CSCC-1 2019 2-1-1-2
EMEA Saudi Arabia OTCC-1 2022 2-1-1-4
APAC (4)

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

Asset Management (AST) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). 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. ▪ Standardized Operating Procedures (SOP) associated with AST domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with AST domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Asset management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The IT department establishes, maintains and updates an inventory that contains a listing of all organizational-owned TAASD, at a minimum covering common devices (e.g., laptops, workstations and servers). ▪ Inventories may be manual (e.g., spreadsheets) or automated. ▪ Data/process owners for business-critical assets are documented and are reviewed as part of the annual asset inventories. ▪ Annual IT asset inventories validate or update stakeholders /owners.

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 identify and involve pertinent stakeholders of critical TAASD to support the ongoing secure management of those assets.

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

  1. AST-07_A01 pertinent stakeholders of critical systems, applications and services are identified and documented.
  2. AST-07_A02 pertinent stakeholders of critical systems, applications and services are involved in supporting the ongoing secure management of those assets.

Evidence Requirements

E-CPL-03 Shared Responsibility Matrix (SRM) / Controls Responsibility Matrix (CRM)

Documented evidence of a Controls Responsibility Matrix (CRM), or similar documentation, that identifies the stakeholder involved in executing assigned controls (e.g., Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix).

Compliance

Technology Recommendations

Micro/Small

  • System Security & Privacy Plan (SSPP)

Small

  • System Security & Privacy Plan (SSPP)

Medium

  • System Security & Privacy Plan (SSPP)

Large

  • System Security & Privacy Plan (SSPP)

Enterprise

  • System Security & Privacy Plan (SSPP)

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.