AST-17.2: Data Action Mapping
Mechanisms exist to create and maintain a map of Technology Assets, Applications and/or Services (TAAS) where sensitive and/or regulated data is stored, transmitted or processed.
Renumbered: Formerly AST-02.8 in SCF 2025.4.
Control Question: Does the organization create and maintain a map of Technology Assets, Applications and/or Services (TAAS) where sensitive and/or regulated data is stored, transmitted or processed?
General (16)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC2.1-POF5 CC2.1-POF9 |
| ISO 27002 2022 | 5.9 |
| ISO 27017 2015 | 8.1.1 |
| ISO 27018 2025 | 5.9 |
| NIST 800-53 R5.2 | CM-13 |
| NIST 800-82 R3 | CM-13 |
| NIST 800-161 R1 | CM-13 |
| NIST 800-161 R1 Level 2 | CM-13 |
| NIST 800-161 R1 Level 3 | CM-13 |
| NIST 800-171 R3 (source) | 03.04.11.a 03.04.11.b |
| NIST 800-171A R3 (source) | A.03.04.11.a[01] A.03.04.11.a[02] A.03.04.11.a[03] A.03.04.11.b[01] A.03.04.11.b[02] |
| NIST 800-172 R3 | 03.01.14E |
| NIST 800-172A R3 | A.03.01.14E.ODP[02] |
| NIST 800-207 | NIST Tenet 1 NIST Tenet 7 |
| NIST Privacy Framework 1.0 | ID.IM-P4 ID.IM-P5 ID.IM-P6 ID.IM-P8 |
| SCF DPMP 2026 | 5.2 |
US (6)
| Framework | Mapping Values |
|---|---|
| USA Federal DHS CISA TIC 3.0 | 3.PEP.DA.DAUTE |
| USA Federal CMMC 2.0 Level 3 | AC.L3-3.1.3E |
| USA Federal DoD Zero Trust Execution Roadmap v1.1 | 4.1.1 5.1 |
| USA Federal IRS 1075 2021 | 2.A.2 CM-13 |
| USA Federal NRC 10 CFR 73.54 2015 | 73.54(b)(1) |
| USA California CCPA 2025 | 7123(c)(4)(A) |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | COS-07.01B.4 SSO-07.01B.1 SSO-07.01AS.1 |
| EMEA Spain CCN-STIC 825 | op.pl.2 op.exp.1 |
APAC (1)
| Framework | Mapping Values |
|---|---|
| APAC India SEBI CSCRF 2024 | ID.AM.S2 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.04.11.A 03.04.11.B |
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). ▪ IT and/or cybersecurity personnel work with process owners to generate and maintain Data Flow Diagrams (DFDs) and network diagrams to document the flow of data to create and maintain a map of systems where sensitive/regulated data is stored, transmitted or processed.
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 map of Technology Assets, Applications and/or Services (TAAS) where sensitive/regulated data is stored, transmitted or processed.
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-17.2_A01 a map of system data actions is developed and documented.
- AST-17.2_A02 the location of sensitive / regulated data is identified and documented.
- AST-17.2_A03 the system components on which sensitive / regulated data is processed are identified and documented.
- AST-17.2_A04 the system components on which sensitive / regulated data is stored are identified and documented.
- AST-17.2_A05 changes to the system or system component location where sensitive / regulated data is processed are documented.
- AST-17.2_A06 changes to the system or system component location where sensitive / regulated data is stored are documented.
- AST-17.2_A07 the location of CUI is identified and documented.
- AST-17.2_A08 the system components on which CUI is processed are identified and documented.
- AST-17.2_A09 the system components on which CUI is stored are identified and documented.
- AST-17.2_A10 changes to the system or system component location where CUI is processed are documented.
- AST-17.2_A11 changes to the system or system component location where CUI is stored are documented.
Evidence Requirements
- E-DCH-05 Data Flow Diagram (DFD)
-
Documented evidence of a Data Flow Diagram (DFD) that accurately identifies where sensitive/regulated data is stored, transmitted and/or processed.
Data Protection
Technology Recommendations
Micro/Small
- Microsoft Visio or draw.io (free, https://draw.io) for data flow diagrams
- LucidChart (https://lucidchart.com)
Small
- Microsoft Visio or draw.io (free, https://draw.io)
- LucidChart (https://lucidchart.com)
- Documented data flow diagrams with sensitivity labels
Medium
- Microsoft Visio
- LucidChart (https://lucidchart.com)
- draw.io (https://draw.io)
- Data flow diagrams integrated with privacy impact assessments
Large
- Microsoft Visio
- LucidChart (https://lucidchart.com)
- Data flow diagrams maintained in CMDB or GRC platform
- Automated data mapping tools (e.g., BigID, OneTrust Data Mapping)
Enterprise
- Enterprise data flow/action mapping platform (e.g., BigID, OneTrust, Securiti.ai)
- Microsoft Visio / LucidChart for technical documentation
- Automated data lineage tools (e.g., Collibra, Alation)
- Data maps maintained current for regulatory compliance (GDPR Article 30)