IAO-10: Threat Analysis & Flaw Remediation During Development
Mechanisms exist to require system developers and integrators to create and execute a Security Testing and Evaluation (ST&E) plan, or similar process, to identify and remediate flaws during development.
Renumbered: Formerly IAO-04 in SCF 2025.4.
Control Question: Does the organization require system developers and integrators to create and execute a Security Testing and Evaluation (ST&E) plan, or similar process, to identify and remediate flaws during development?
General (21)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC4.1 CC4.2 |
| COBIT 2019 | DSS06.04 |
| COSO 2013 | 16.0 17.0 |
| IEC 62443-2-1 2024 | ORG 2.4(c) |
| ISO/SAE 21434 2021 | RQ-09-03 RQ-09-03(a) RQ-09-03(b) RQ-09-03(c) RQ-09-03(d) RQ-09-03(e) RQ-09-03(f) |
| ISO 27002 2022 | 8.25 |
| ISO 27018 2025 | 8.25 |
| ISO 42001 2023 | 10.2 10.2(a) 10.2(a)(1) 10.2(a)(2) 10.2(b) 10.2(b)(1) 10.2(b)(2) 10.2(b)(3) 10.2(c) 10.2(d) 10.2(e) |
| NIST 800-37 R2 | TASK A-5 TASK M-3 |
| NIST 800-53 R5.2 | SA-11(05) |
| NIST 800-82 R3 | SA-11(05) |
| NIST 800-160 Vol2 R1 | SA-11(05) |
| OWASP Top 10 2025 | A01:2025 A02:2025 A05:2025 A06:2025 A07:2025 A09:2025 A10:2025 |
| PCI DSS 4.0.1 (source) | 6.2.1 6.2.2 6.2.3 6.2.3.1 6.2.4 6.3.1 6.4.1 6.4.2 11.4.1 11.4.4 12.4.2.1 A1.2.3 |
| PCI DSS 4.0.1 SAQ A (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 6.2.1 6.2.2 6.2.4 6.3.1 6.4.1 6.4.2 11.4.1 11.4.4 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ C (source) | 6.2.1 6.2.2 6.2.3.1 6.2.4 6.3.1 |
| PCI DSS 4.0.1 SAQ C-VT (source) | 6.3.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 6.2.1 6.2.2 6.2.3 6.2.3.1 6.2.4 6.3.1 6.4.1 6.4.2 11.4.1 11.4.4 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 6.2.1 6.2.2 6.2.3 6.2.3.1 6.2.4 6.3.1 6.4.1 6.4.2 11.4.1 11.4.4 12.4.2.1 A1.2.3 |
US (2)
| Framework | Mapping Values |
|---|---|
| USA Federal DoW BaTB OT 2026 | 10 |
| USA Federal IRS 1075 2021 | SA-11(CE-5) SA-11(CE-5).a SA-11(CE-5).b |
EMEA (8)
| Framework | Mapping Values |
|---|---|
| EMEA Spain CCN-STIC 825 | mp.sw.1 |
| EMEA EU Cyber Resiliency Act 2024 | Article 13(6) Article 13(21) |
| EMEA EU Cyber Resiliency Act Annex I 2024 | Annex I, Part II(2) Annex I, Part II(3) |
| EMEA EU EBA GL/2019/04 | 3.4.6.42 3.6.2.69 3.6.2.70 |
| EMEA EU NIS2 2022 | Article 21.4 |
| EMEA Saudi Arabia CSCC-1 2019 | 1-3-2-1 |
| EMEA Saudi Arabia ECC-1 2018 | 1-5-3 |
| EMEA Saudi Arabia SACS-002 2022 | VII.B.TPC-72 |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia CCM 2026 | IDE-04 |
| APAC New Zealand NZISM 3.9 | 6.2.5.C.01 6.2.6.C.01 |
| APAC Singapore MAS TRM 2021 | 5.7.5 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada OSFI Self-Assessment Guidance | 2.4.4 |
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
Information Assurance (IAO) 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 IAO domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with IAO 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 IAO domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Information Assurance (IA)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ IA management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Pre-production security testing is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ IT and/or cybersecurity personnel implement and maintain a limited Information Assurance Program (IAP) capability to conduct limited control testing to meet specific statutory, regulatory and/or contractual requirements for pre-production cybersecurity and data protection control testing.
Level 3 — Well Defined
Information Assurance (IAO) 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 IAO 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 IAO domain capabilities are well-documented and kept current by process owners. ▪ An information assurance team, or similar function, is appropriately staffed and supported to implement and maintain IAO domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of information assurance operations (e.g., assessment scheduling software and risk assessment software). ▪ 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 IAO 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 require system developers and integrators to create and execute a Security Testing and Evaluation (ST&E) plan, or similar process, to identify and remediate flaws during development.
Level 4 — Quantitatively Controlled
Information Assurance (IAO) 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
- IAO-10_A01 the breadth of penetration testing is defined.
- IAO-10_A02 the depth of penetration testing is defined.
- IAO-10_A03 constraints of penetration testing are defined.
- IAO-10_A04 the developer of the system, system component, or system service is required to perform penetration testing at an organization-defined breadth.
- IAO-10_A05 the developer of the system, system component, or system service is required to perform penetration testing at an organization-defined level of rigor.
- IAO-10_A06 the developer of the system, system component, or system service is required to perform penetration testing under organization-defined constraints.
Evidence Requirements
- E-TDA-03 Application Security Testing (AST)
-
Documented evidence of application security testing (e.g., DAST, SAST, fuzzing, etc.).
Technology Design & Acquisition
Technology Recommendations
Micro/Small
- Pre-production Control Validation Testing (CVT)
Small
- Pre-production Control Validation Testing (CVT)
Medium
- Pre-production Control Validation Testing (CVT)
Large
- Pre-production Control Validation Testing (CVT)
Enterprise
- Pre-production Control Validation Testing (CVT)