Skip to main content

TDA-06.6: Information Assurance Enabled Products

TDA 2 — Low Protect

Mechanisms exist to limit the use of commercially-provided Information Assurance (IA) and IA-enabled IT products to those products that have been successfully evaluated against a National Information Assurance Partnership (NIAP)-approved Protection Profile or the cryptographic module is FIPS-validated or NSA-approved.

Renumbered: Formerly TDA-02.2 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, TDA-06.6 was Software Design Root Cause Analysis. That control is now TDA-05.5.

Control Question: Does the organization limit the use of commercially-provided Information Assurance (IA) and IA-enabled IT products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile or the cryptographic module is FIPS-validated or NSA-approved?

General (19)
Framework Mapping Values
GovRAMP IA-02(01) IA-02(02) SA-04(10)
GovRAMP Core IA-02(01)
GovRAMP Low IA-02(01)
GovRAMP Low+ IA-02(01)
GovRAMP Moderate IA-02(01) IA-02(02)
GovRAMP High IA-02(01) IA-02(02) SA-04(10)
NIST 800-53 R4 SA-4(10) IA-5(11)
NIST 800-53 R5.2 IA-02(01) IA-02(02) SA-04(06) SA-04(07) SA-04(10)
NIST 800-53B R5 (low) (source) IA-02(01) IA-02(02) SA-04(10)
NIST 800-53B R5 (moderate) (source) IA-02(01) IA-02(02) SA-04(10)
NIST 800-53B R5 (high) (source) IA-02(01) IA-02(02) SA-04(10)
NIST 800-82 R3 IA-02(01) IA-02(02) SA-04(06) SA-04(07) SA-04(10)
NIST 800-82 R3 LOW OT Overlay IA-02(01) IA-02(02) SA-04(10)
NIST 800-82 R3 MODERATE OT Overlay IA-02(01) IA-02(02) SA-04(10)
NIST 800-82 R3 HIGH OT Overlay IA-02(01) IA-02(02) SA-04(10)
NIST 800-161 R1 SA-4(7)
NIST 800-161 R1 Level 2 SA-4(7)
NIST 800-161 R1 Level 3 SA-4(7)
NIST 800-171 R2 (source) NFO - SA-4(10)
US (10)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 IA-2(1) IA-2(2)
USA Federal CJIS Security Policy 6.0 IA-2(1) IA-2(2) SA-4(10)
USA Federal FedRAMP R5 (low) IA-02(01) IA-02(02) SA-04(10)
USA Federal FedRAMP R5 (moderate) IA-02(01) IA-02(02) SA-04(10)
USA Federal FedRAMP R5 (high) IA-02(01) IA-02(02) SA-04(10)
USA Federal FedRAMP R5 (LI-SaaS) SA-04(10)
USA Federal IRS 1075 2021 IA-2(CE-1) IA-2(CE-2)
USA Texas DIR SCSC 2.2 2025 IA-02(1) IA-02(2)
USA Texas TX-RAMP Level 1 IA-02 (01)
USA Texas TX-RAMP Level 2 IA-02 (01)
APAC (1)
Framework Mapping Values
APAC India RBI Digital Payments 2021 68.0

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

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 limit the use of commercially-provided Information Assurance (IA) and IA-enabled IT products to those products that have been successfully evaluated against a National Information Assurance partnership (NIAP)-approved Protection Profile or the cryptographic module is FIPS-validated or NSA-approved.

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-06.6_A01 as required per statutory, regulatory or contractual obligations, only information technology products on the FIPS 201-approved products list for the Personal Identity Verification (PIV) capability implemented within organizational systems are employed.
  2. TDA-06.6_A02 the use of commercially-provided Information Assurance (IA) and IA-enabled IT products is limited to products that have been successfully evaluated against a National Information Assurance Partnership (NIAP)-approved Protection Profile or whose cryptographic module is FIPS-validated or NSA-approved.

Technology Recommendations

Micro/Small

  • Note: Typically not required at this size

Small

  • Note: Typically not required at this size; prefer validated security products where available

Medium

  • Preference for FIPS 140-3 validated and Common Criteria evaluated security products
  • Product evaluation criteria in procurement

Large

  • Requirement for validated IA/IA-enabled products (FIPS 140-3, Common Criteria/NIAP) where required by contract or regulation
  • Procurement standards

Enterprise

  • Enterprise IA product acquisition standards requiring validated/evaluated products (NIAP, FIPS 140-3, CSfC)
  • Product security evaluation function

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.