TDA-17.4: Application Penetration Testing
Mechanisms exist to perform application-level penetration testing of custom-made Technology Assets, Applications and/or Services (TAAS).
Renumbered: Formerly TDA-09.5 in SCF 2025.4.
Control Question: Does the organization perform application-level penetration testing of custom-made Technology Assets, Applications and/or Services (TAAS)?
General (18)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 16.13 |
| CIS CSC 8.1 IG3 | 16.13 |
| CSA CCM 4.1.0 | AIS-05 |
| CSA IoT SCF 2 | SDV-07 SET-02 SET-06 |
| IEC 62443-4-1 2018 | SVV-4 |
| NIST 800-53 R5.2 | SA-11(05) |
| NIST 800-82 R3 | SA-11(05) |
| NIST 800-160 Vol2 R1 | SA-11(05) |
| NIST 800-218 | PW.7 PW.8 |
| OWASP Top 10 2025 | A01:2025 A02:2025 A03:2025 A04:2025 A05:2025 A06:2025 A07:2025 A08:2025 A09:2025 A10:2025 |
| PCI DSS 4.0.1 (source) | 6.2.4 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 6.2.4 |
| PCI DSS 4.0.1 SAQ C (source) | 6.2.4 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 6.2.4 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 6.2.4 |
| SWIFT CSF 2025 | 7.3A |
| UL 2900-1 2017 | 16.1 16.1(a) 16.1(b) 16.1(c) 16.2 16.2(a) 16.2(b) 16.2(c) 16.2(d) 16.2(e) 16.3 16.4 |
| UL 2900-2-2 2016 | 16.1 |
US (4)
| Framework | Mapping Values |
|---|---|
| USA Federal DHS CISA TIC 3.0 | 3.UNL.STEXE |
| USA Federal C2M2 2.1 | ARCHITECTURE-4h |
| USA Federal IRS 1075 2021 | SA-11(CE-5) |
| USA California CCPA 2025 | 7123(c)(6) |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | DEV-07.01AC PSS-02.01AC |
| EMEA Saudi Arabia ECC-1 2018 | 1-6-3-3 |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0402 |
| APAC Malaysia RMiT 2025 | A5-D4 |
| APAC New Zealand NZISM 3.9 | 14.5.6.C.01 |
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 perform application-level penetration testing of custom-made Technology Assets, Applications and/or Services (TAAS).
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
- TDA-17.4_A01 the developer of the system, system component, or system service is required to perform penetration testing per an organization-defined breadth.
- TDA-17.4_A02 the developer of the system, system component, or system service is required to perform penetration testing per an organization-defined depth.
- TDA-17.4_A03 the developer of the system, system component, or system service is required to perform penetration testing under organization-defined constraints.
- TDA-17.4_A04 the developer of the system, system component or system service is required to perform attack surface reviews.
Evidence Requirements
- E-TDA-03 Application Security Testing (AST)
-
Documented evidence of application security testing (e.g., DAST, SAST, fuzzing, etc.).
Technology Design & Acquisition - E-VPM-02 Penetration Testing - Application
-
Documented evidence of Application Security Testing (AST) activities: • Abuse case, malformed, and unexpected inputs (e.g., Robustness or Fuzz testing); • Attack surface analysis; • Vulnerability chaining; • Closed box testing of known vulnerability scanning; • Software composition analysis of binary executable files; and/or • Static and dynamic code analysis, including testing for credentials that are “hardcoded,” default, easily guessed, and easily compromised.
Vulnerability & Patch Management
Technology Recommendations
Micro/Small
- Annual penetration test of custom applications by qualified tester (or bug bounty platform lite)
Small
- Annual application penetration test by qualified third party
Medium
- Application penetration testing for custom TAAS before release and annually
- Retesting of findings
Large
- Application security testing program with pen tests per release cycle
- Bug bounty or vulnerability disclosure program (e.g., HackerOne, Bugcrowd)
Enterprise
- Enterprise application penetration testing program (internal red team and third parties)
- Continuous bug bounty
- Pen test findings integrated with vulnerability management