Skip to main content

TDA-14.1: Software / Firmware Integrity Verification

TDA 8 — High Protect

Mechanisms exist to require developers of Technology Assets, Applications and/or Services (TAAS) to enable integrity verification of software and firmware components.

Control Question: Does the organization require developers of Technology Assets, Applications and/or Services (TAAS) to enable integrity verification of software and firmware components?

General (17)
Framework Mapping Values
CIS CSC 8.1 16.5 16.11
CIS CSC 8.1 IG2 16.5 16.11
CIS CSC 8.1 IG3 16.5 16.11
CSA IoT SCF 2 CCM-06 IAM-22 IOT-03 IOT-09
ENISA 2.0 SO12
GovRAMP Moderate SA-10(01)
GovRAMP High SA-10(01)
NIST Privacy Framework 1.0 PR.DS-P6
NIST 800-53 R4 SA-10(1)
NIST 800-53 R5 (source) SA-10(1)
NIST 800-53 R5 (NOC) (source) SA-10(1)
NIST 800-172 3.14.7e
NIST CSF 2.0 (source) ID.RA-09
UL 2900-1 2017 11.5 11.6 11.7
SCF CORE ESP Level 1 Foundational TDA-14.1
SCF CORE ESP Level 2 Critical Infrastructure TDA-14.1
SCF CORE ESP Level 3 Advanced Threats TDA-14.1
US (9)
Framework Mapping Values
US C2M2 2.1 ARCHITECTURE-4.G.MIL3
US DHS CISA SSDAF 2
US DHS ZTCF DEV-04
US EO 14028 4e(iii)
US FedRAMP R4 SA-10(1)
US FedRAMP R4 (moderate) SA-10(1)
US FedRAMP R4 (high) SA-10(1)
US IRS 1075 SA-10(1)
US - TX TX-RAMP Level 2 SA-10(1)
EMEA (2)
Framework Mapping Values
EMEA EU NIS2 Annex 6.6.1(c)
EMEA Israel CDMO 1.0 17.20

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to require developers of Technology Assets, Applications and/or Services (TAAS) to enable integrity verification of software and firmware components.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to require developers of Technology Assets, Applications and/or Services (TAAS) to enable integrity verification of software and firmware components.

Level 2 — Planned & Tracked

Technology Development & Acquisition (TDA) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Development and acquisition management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • IT/cybersecurity personnel identify cybersecurity and data protection controls to address applicable statutory, regulatory and contractual requirements for technology development and acquisition management.
  • IT/cybersecurity personnel implement secure practices to protect the confidentiality, integrity, availability and safety of the organization's technology assets, data and network(s).
  • Secure development practices mostly conform to industry-recognized standards for secure engineering (e.g., OWASP, NIST SP 800-218, NIST SP 800-160, etc.).
  • Procurement practices require third-party developers of Technology Assets, Applications and/or Services (TAAS) to follow secure engineering practices.
  • A Project Management Office (PMO), or project management function, enables the implementation of cybersecurity and data privacy-related resource planning controls across the System Development Lifecycle (SDLC) for all high-value projects.
Level 3 — Well Defined

Technology Development & Acquisition (TDA) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data for technology development and acquisition. o Ensures the Information Assurance Program (IAP) evaluates applicable cybersecurity and data protection controls as part of “business as usual” pre-production testing. o Operates the Cybersecurity Supply Chain Risk Management (C-SCRM) program to identify and mitigate supply chain-related risks and threats.

  • Secure development practices conform to industry-recognized standards for secure engineering (e.g., OWASP, NIST SP 800-218, NIST SP 800-160, etc.).
  • A procurement team, or similar function, ensures that third party development and/ or acquisitions meet, or exceed, the organization's business, cybersecurity and data privacy requirements to have secure and resilient systems, applications, services and processes.
  • A Software Assurance Maturity Model (SAMM) governs a secure development lifecycle for the development of systems, applications and services.
  • Administrative processes exist and technologies are configured to implement secure configuration settings by default to reduce the likelihood of software being deployed with weak security settings, putting the asset at a greater risk of compromise.
  • An IT Asset Management (ITAM) function, or similar function, categorizes devices according to the data the asset stores, transmits and/ or processes and applies the appropriate technology controls to protect the asset and data.
  • A formal Change Management (CM) program help to ensure that no unauthorized changes are made, all changes are documented, services are not disrupted and resources are used efficiently.
  • A Governance, Risk & Compliance (GRC) function, or similar function;
  • A Project Management Office (PMO), or project management function, enables IAP pre-production testing of cybersecurity and data protection controls as part of the organization's established project management processes.
Level 4 — Quantitatively Controlled

Technology Development & Acquisition (TDA) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • 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.
  • Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving

Technology Development & Acquisition (TDA) efforts are “world-class” capabilities that leverage predictive analysis (e.g., machine learning, AI, etc.). In addition to CMM Level 4 criteria, CMM Level 5 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions.
  • Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.

Assessment Objectives

  1. TDA-14.1_A01 the developer of the system, system component or system service is required to enable integrity verification of software and firmware components.

Evidence Requirements

E-TDA-01 Secure Software Development Principles (SSDP)

Documented evidence of a Secure Software Development Principles (SSDP). This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.

Technology Design & Acquisition
E-TDA-02 Secure Engineering & Data Privacy (SEDP)

Documented evidence of a Secure Engineering & Data Privacy (SEDP) program. This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.

Technology Design & Acquisition
E-TDA-04 Design and Development Plan (DDP)

Documented evidence of an engineering method to control the design process and govern the lifecycle of the product/service.

Technology Design & Acquisition
E-TDA-08 Secure Engineering Principles (SEP)

Documented evidence of defined secure engineering principles used to ensure Sensitivity, Integrity, Availability & Safety (CIAS) concerns are properly addressed in the design and implementation of systems, applications and services.

Technology Design & Acquisition

Technology Recommendations

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.