AST-30: Roots of Trust Protection
Mechanisms exist to provision and protect the confidentiality, integrity and authenticity of product supplier keys and data that can be used as a “roots of trust” basis for integrity verification.
Renumbered: Formerly AST-18 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, AST-30 was Decommissioning. That control is now AST-36.
Control Question: Does the organization provision and protect the confidentiality, integrity and authenticity of product supplier keys and data that can be used as a “roots of trust” basis for integrity verification?
General (3)
| Framework | Mapping Values |
|---|---|
| CSA IoT SCF 2 | IOT-09 |
| IEC 62443-4-2 2019 | EDR 3.12 EDR 3.13(a) EDR 3.13(b) HDR 3.12 HDR 3.13(a) NDR 3.12 NDR 3.13(a) NDR 3.13(b) |
| NIST CSF 2.0 (source) | ID.RA-09 |
US (2)
| Framework | Mapping Values |
|---|---|
| USA Federal CMMC 2.0 Level 3 | SI.L3-3.14.1E |
| USA Federal DoD Zero Trust Reference Architecture 2.0 | 4.2 |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Saudi Arabia IoT CGIoT-1 2024 | 2-15-1 |
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 provision and protect the confidentiality, integrity and authenticity of product supplier keys and data that can be used as a “roots of trust” basis for integrity verification.
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
- AST-30_A01 security-critical or essential software is defined.
- AST-30_A02 root of trust mechanisms or cryptographic signatures are identified.
- AST-30_A03 the integrity of security critical or essential software is verified using root of trust mechanisms or cryptographic signatures.
Evidence Requirements
- E-AST-26 Roots of Trust Evidence
-
Documented evidence of product supplier data that can be used as a “roots of trust” basis for integrity verification.
Asset Management
Technology Recommendations
Micro/Small
- IT Asset Management (ITAM) program
- Configuration Management Database (CMDB)
Small
- IT Asset Management (ITAM) program
- Configuration Management Database (CMDB)
Medium
- IT Asset Management (ITAM) program
- Configuration Management Database (CMDB)
Large
- IT Asset Management (ITAM) program
- Configuration Management Database (CMDB)
Enterprise
- IT Asset Management (ITAM) program
- Configuration Management Database (CMDB)