AST-29: Technology Asset Inspections
Mechanisms exist to physically and logically inspect critical technology assets to detect evidence of tampering.
Renumbered: Formerly AST-15.1 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, AST-29 was Radio Frequency Identification (RFID) Security. That control is now CFG-04.13.
Control Question: Does the organization physically and logically inspect critical technology assets to detect evidence of tampering?
General (24)
| Framework | Mapping Values |
|---|---|
| NIST 800-53 R4 | SA-18(2) |
| NIST 800-53 R5.2 | SR-10 |
| NIST 800-53B R5 (low) (source) | SR-10 |
| NIST 800-53B R5 (moderate) (source) | SR-10 |
| NIST 800-53B R5 (high) (source) | SR-10 |
| NIST 800-82 R3 | SR-10 |
| NIST 800-82 R3 LOW OT Overlay | SR-10 |
| NIST 800-82 R3 MODERATE OT Overlay | SR-10 |
| NIST 800-82 R3 HIGH OT Overlay | SR-10 |
| NIST 800-160 Vol2 R1 | SR-10 |
| NIST 800-161 R1 | SR-10 |
| NIST 800-161 R1 C-SCRM Baseline | SR-10 |
| NIST 800-161 R1 Flow Down | SR-10 |
| NIST 800-161 R1 Level 2 | SR-10 |
| NIST 800-161 R1 Level 3 | SR-10 |
| NIST 800-172 R3 | 03.17.02E |
| NIST 800-172A R3 | DS-A.03.17.02E |
| PCI DSS 4.0.1 (source) | 9.5.1 9.5.1.2 |
| PCI DSS 4.0.1 SAQ B (source) | 9.5.1 9.5.1.2 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 9.5.1 9.5.1.2 |
| PCI DSS 4.0.1 SAQ C (source) | 9.5.1 9.5.1.2 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 9.5.1 9.5.1.2 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 9.5.1 9.5.1.2 |
| PCI DSS 4.0.1 SAQ P2PE (source) | 9.5.1 9.5.1.2 |
US (6)
| Framework | Mapping Values |
|---|---|
| USA Federal CJIS Security Policy 6.0 | SR-10 |
| USA Federal FedRAMP R5 (low) | SR-10 |
| USA Federal FedRAMP R5 (moderate) | SR-10 |
| USA Federal FedRAMP R5 (high) | SR-10 |
| USA Federal FedRAMP R5 (LI-SaaS) | SR-10 |
| USA Federal IRS 1075 2021 | SR-10 |
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
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). ▪ Periodic physical inspections are performed to validate the integrity of unattended technology assets (e.g., kiosks, ATMs and point of sale devices).
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 physically and logically inspect critical technology assets to detect evidence of tampering.
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
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. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Assessment Objectives
- AST-29_A01 systems or system components that require inspection are defined.
- AST-29_A02 the frequency at which to inspect systems or system components is defined.
- AST-29_A03 indications of the need for an inspection of systems or system components are defined.
- AST-29_A04 systems or system components are inspected to detect tampering.
Evidence Requirements
- E-AST-25 Logical Tamper Detection Tool
-
Documented evidence of software that is implemented and configured to detect logical tampering (e.g., configurations).
Asset Management
Technology Recommendations
Micro/Small
- Tamper detection tape
- Indicators of Compromise (IoC)
- File Integrity Monitoring (FIM)
Small
- Tamper detection tape
- Indicators of Compromise (IoC)
- File Integrity Monitoring (FIM)
Medium
- Tamper detection tape
- Indicators of Compromise (IoC)
- File Integrity Monitoring (FIM)
- CimTrak Integrity Suite (https://cimcor.com/cimtrak)
- Netwrix Auditor (https://netrix.com)
- Tripwire Enterprise (https://tripwire.com)
Large
- Tamper detection tape
- Indicators of Compromise (IoC)
- File Integrity Monitoring (FIM)
- CimTrak Integrity Suite (https://cimcor.com/cimtrak)
- Netwrix Auditor (https://netrix.com)
- Tripwire Enterprise (https://tripwire.com)
Enterprise
- Tamper detection tape
- Indicators of Compromise (IoC)
- File Integrity Monitoring (FIM)
- CimTrak Integrity Suite (https://cimcor.com/cimtrak)
- Netwrix Auditor (https://netrix.com)
- Tripwire Enterprise (https://tripwire.com)