TDA-15: Secure Development Environments
Mechanisms exist to maintain a segmented development network to ensure a secure development environment.
Renumbered: Formerly TDA-07 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, TDA-15 was Developer Threat Analysis & Flaw Remediation. That control is now TDA-20.1.
Control Question: Does the organization maintain a segmented development network to ensure a secure development environment?
General (20)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 16.8 |
| CIS CSC 8.1 IG2 | 16.8 |
| CIS CSC 8.1 IG3 | 16.8 |
| COBIT 2019 | BAI07.04 |
| CSA CCM 4.1.0 | AIS-06 |
| IEC 62443-4-1 2018 | SM-7 |
| ISO 27002 2022 | 8.25 8.31 |
| ISO 27017 2015 | 12.1.4 14.2.6 |
| ISO 27018 2025 | 8.25 8.31 |
| NIST AI 600-1 | MS-2.3-004 |
| NIST 800-53 R5.2 | SA-03(01) |
| NIST 800-82 R3 | SA-03(01) |
| NIST 800-218 | PO.5 PO.5.1 |
| PCI DSS 4.0.1 (source) | 6.5.3 11.4.5 11.4.6 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 11.4.5 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 11.4.5 |
| PCI DSS 4.0.1 SAQ C (source) | 11.4.5 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 6.5.3 11.4.5 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 6.5.3 11.4.5 11.4.6 |
| SPARTA 4.0 | CM0004 |
US (3)
| Framework | Mapping Values |
|---|---|
| USA Federal DHS CISA SSDAF | 1 1.a |
| USA Federal EO 14028 | 4e(i) 4e(i)(A) |
| USA California CCPA 2025 | 7123(c)(14) |
EMEA (8)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | DEV-11.01B |
| EMEA Spain CCN-STIC 825 | mp.sw.1 |
| EMEA EU DORA RTS 2024 | Article 16.1(c) Article 37.1(c) |
| EMEA EU EBA GL/2019/04 | 3.6.2.72 |
| EMEA EU NIS2 Annex 2024 | 6.2.2(c) 6.8.2(h) |
| EMEA LUX CCSF 20/750 2020 | 3.6.2-69 |
| EMEA Saudi Arabia CSCC-1 2019 | 1-3-2-4 |
| EMEA Saudi Arabia OTCC-1 2022 | 1-4-1-4 |
APAC (5)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0400 ISM-1419 |
| APAC Japan ISMAP | 14.2.1.1 14.2.6 14.2.6.1 14.2.6.2 14.2.6.3 14.2.6.4 14.2.6.5 14.2.6.6 14.2.6.7 14.2.6.8 14.2.6.9 14.2.6.10 14.2.6.11 14.2.6.12 |
| APAC Malaysia RMiT 2025 | 10.7 |
| APAC New Zealand NZISM 3.9 | 14.4.4.C.01 |
| APAC Singapore MAS TRM 2021 | 5.7.3 |
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 a segmented development network to ensure a secure development environment.
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
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. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Assessment Objectives
- TDA-15_A01 system pre-production environments are protected commensurate with risk throughout the system development life cycle for the system, system component or system service.
Evidence Requirements
- E-TDA-20 Development / Test / Production Environment Separation
-
Documented evidence of secure development environments and separation of development, test and production environments, including secure migration practices.
Technology Design & Acquisition
Technology Recommendations
Micro/Small
- Development on separate cloud accounts/VMs from production
Small
- Separate development network/VLAN or cloud account
- Access limited to developers
Medium
- Segmented development environment (network/cloud account separation)
- Access control and monitoring of development environment
- Hardened developer workstations
Large
- Dedicated secure development environment with segmentation, MFA and monitoring
- Secure developer workstations
- Protected build infrastructure
Enterprise
- Enterprise secure development environment program aligned with NIST SSDF (segmented networks, hardened endpoints, protected build systems)
- Continuous monitoring of development infrastructure