Skip to main content

TDA-09: Product Tampering and Counterfeiting (PTC)

TDA 9 — Critical Protect

Mechanisms exist to maintain awareness of component authenticity by developing and implementing Product Tampering and Counterfeiting (PTC) practices that include the means to detect and prevent counterfeit components.

Renumbered: Formerly TDA-11 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, TDA-09 was Cybersecurity & Data Protection Testing Throughout Development. That control is now TDA-17.

Control Question: Does the organization maintain awareness of component authenticity by developing and implementing Product Tampering and Counterfeiting (PTC) practices that include the means to detect and prevent counterfeit components?

General (23)
Framework Mapping Values
CIS CSC 8.1 16.5
CIS CSC 8.1 IG2 16.5
CIS CSC 8.1 IG3 16.5
MITRE ATT&CK 16 T1059.002 T1195 T1195.001 T1195.002 T1195.003 T1204.003 T1505 T1505.001 T1505.002 T1505.004 T1546.006 T1554 T1601 T1601.001 T1601.002
NIST 800-53 R4 SA-12(10) SA-19
NIST 800-53 R5.2 SR-04(03) SR-04(04) SR-10 SR-11 SR-11(03)
NIST 800-53B R5 (low) (source) SR-10 SR-11
NIST 800-53B R5 (moderate) (source) SR-10 SR-11
NIST 800-53B R5 (high) (source) SR-10 SR-11
NIST 800-82 R3 SR-04(03) SR-04(04) SR-10 SR-11 SR-11(03)
NIST 800-82 R3 LOW OT Overlay SR-10 SR-11
NIST 800-82 R3 MODERATE OT Overlay SR-10 SR-11
NIST 800-82 R3 HIGH OT Overlay SR-10 SR-11
NIST 800-160 Vol2 R1 SR-04(03) SR-04(04) SR-10 SR-11 SR-11(03)
NIST 800-161 R1 SR-10 SR-11 SR-11(3)
NIST 800-161 R1 C-SCRM Baseline SR-10 SR-11
NIST 800-161 R1 Flow Down SR-10
NIST 800-161 R1 Level 1 SR-11
NIST 800-161 R1 Level 2 SR-10 SR-11 SR-11(3)
NIST 800-161 R1 Level 3 SR-10 SR-11 SR-11(3)
NIST 800-172 R3 03.17.02E 03.17.03E 03.17.05E
NIST 800-172A R3 A.03.17.02E.ODP[04] DS-A.03.17.03E.b A.03.17.03E.ODP[01] DS-A.03.17.05E[01] A.03.17.05E.ODP[01] DS-A.03.17.05E[02]
SPARTA 4.0 CM0028 CM0024
US (7)
EMEA (1)
Framework Mapping Values
EMEA Germany C5 2026 DEV-14.03B
APAC (1)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-1790 ISM-1791 ISM-1792

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

Technology Development & Acquisition (TDA) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with TDA domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Technology development & acquisition-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Secure development practices loosely conform to industry-recognized standards for secure engineering (e.g., OWASP, NIST SP 800-218 and NIST SP 800-160).

Level 2 — Planned & Tracked

Technology Development & Acquisition (TDA) 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 TDA domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with TDA 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 TDA domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Technology development and acquisition-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Technology development and acquisition management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Secure development practices mostly conform to industry-recognized standards for secure engineering of Technology Assets, Applications and/or Services (TAAS) (e.g., OWASP, NIST SP 800-218 and NIST SP 800-160). ▪ An application development team, or similar function, uses a structured process to design, build and maintain secure configurations for test, development, staging and production environments.

Level 3 — Well Defined

Technology Development & Acquisition (TDA) 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 TDA 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 TDA domain capabilities are well-documented and kept current by process owners. ▪ A software development team, or similar function, is appropriately staffed and supported to implement and maintain TDA domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of technology development and acquisition management (e.g., project management software, software escrow solution and software testing tools). ▪ 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 TDA 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 maintain awareness of component authenticity by developing and implementing Product Tampering and Counterfeiting (PTC) practices that include the means to detect and prevent counterfeit components.

Level 4 — Quantitatively Controlled

Technology Development & Acquisition (TDA) 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. TDA-09_A01 controls to validate that the system or system component received is genuine are defined.
  2. TDA-09_A02 controls to validate that the system or system component received has not been altered are defined.
  3. TDA-09_A03 controls are employed to validate that the system or system component received is genuine.
  4. TDA-09_A04 controls are employed to validate that the system or system component received has not been altered.
  5. TDA-09_A05 controls employed to ensure that the integrity of the system and system component are defined.
  6. TDA-09_A06 an analysis method to be conducted to validate the internal composition and provenance of critical or mission-essential technologies, products and services to ensure the integrity of the system and system component is defined.
  7. TDA-09_A07 controls are employed to ensure the integrity of the system and system components.
  8. TDA-09_A08 analysis method is conducted to ensure the integrity of the system and system components.
  9. TDA-09_A09 systems or system components that require inspection are defined.
  10. TDA-09_A10 frequency at which to inspect systems or system components is defined.
  11. TDA-09_A11 indications of the need for an inspection of systems or system components are defined.
  12. TDA-09_A12 systems or system components are inspected to detect tampering.
  13. TDA-09_A13 external reporting organizations to whom counterfeit system components are to be reported is/are defined.
  14. TDA-09_A14 personnel or roles to whom counterfeit system components are to be reported is/are defined.
  15. TDA-09_A15 anti-counterfeit procedures are developed and implemented.
  16. TDA-09_A16 the anti-counterfeit procedures include the means to detect counterfeit components entering the system.
  17. TDA-09_A17 the anti-counterfeit procedures include the means to prevent counterfeit components from entering the system.
  18. TDA-09_A18 counterfeit system components are reported per organization-defined criteria.
  19. TDA-09_A19 the frequency at which to scan for counterfeit system components is defined.
  20. TDA-09_A20 scanning for counterfeit system components is conducted per an organization-defined frequency.

Evidence Requirements

E-TDA-22 Anti-Counterfeit & Product Tampering Controls

Documented evidence of anti-counterfeit and product tampering controls, including anti-counterfeit training.

Technology Design & Acquisition

Technology Recommendations

Micro/Small

  • Buy hardware/software from authorized resellers only

Small

  • Authorized supplier policy
  • Inspect deliveries for tampering

Medium

  • Anti-counterfeit and anti-tamper procedures in procurement and receiving
  • Authorized distributor verification
  • Component authenticity checks

Large

  • Product Tampering and Counterfeiting (PTC) program within C-SCRM
  • Supplier authorization and verification
  • Tamper-evident packaging and inspection

Enterprise

  • Enterprise anti-counterfeit program (e.g., aligned with SAE AS6171, NIST SP 800-161)
  • Component authenticity testing
  • Supply chain traceability and supplier audits

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.