Skip to main content

PRM-07: Secure Development Life Cycle (SDLC) Management

PRM 10 — Critical Protect

Mechanisms exist to ensure changes to Technology Assets, Applications and/or Services (TAAS) within the Secure Development Life Cycle (SDLC) are controlled through formal change control procedures.

Control Question: Does the organization ensure changes to Technology Assets, Applications and/or Services (TAAS) within the Secure Development Life Cycle (SDLC) are controlled through formal change control procedures?

General (45)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC5.2 CC8.1 CC8.1-POF1
CIS CSC 8.1 15.7
CIS CSC 8.1 IG3 15.7
COBIT 2019 BAI01.01 BAI01.02 BAI01.03 BAI02.04 BAI03.09 BAI03.11 BAI04.03 BAI05.01 BAI05.07 BAI09.03
COSO 2013 11.0
CSA CCM 4.1.0 AIS-04
CSA IoT SCF 2 LGL-02 LGL-03 LGL-04 LGL-05 LGL-06 LGL-07 POL-04
GovRAMP SA-03
GovRAMP Low SA-03
GovRAMP Low+ SA-03
GovRAMP Moderate SA-03
GovRAMP High SA-03
ISO 27002 2022 5.8 8.25 8.32
ISO 27017 2015 6.1.5 12.1.2 14.2.2
ISO 27018 2025 5.8 8.25 8.32
ISO 31000 2018 5.3 5.4.2 5.4.5 6.2
ISO 31010 2009 4.3.2
ISO 42001 2023 A.3.3 A.4.2 A.6.2.2 A.6.2.7 A.6.2.8
MITRE ATT&CK 16 T1078 T1078.001 T1078.003 T1078.004 T1213.003 T1574.002
NIST AI 100-1 (AI RMF) 1.0 GOVERN 1.7 MANAGE 2.2
NIST 800-37 R2 TASK P-13 TASK M-7
NIST 800-53 R4 SA-3
NIST 800-53 R5.2 SA-03 SA-03(01) SA-08(30)
NIST 800-53B R5 (low) (source) SA-03
NIST 800-53B R5 (moderate) (source) SA-03
NIST 800-53B R5 (high) (source) SA-03
NIST 800-53B R5 (privacy) (source) SA-03
NIST 800-82 R3 SA-03 SA-03(01) SA-08(30)
NIST 800-82 R3 LOW OT Overlay SA-03
NIST 800-82 R3 MODERATE OT Overlay SA-03
NIST 800-82 R3 HIGH OT Overlay SA-03
NIST 800-161 R1 SA-3
NIST 800-161 R1 C-SCRM Baseline SA-3
NIST 800-161 R1 Level 1 SA-3
NIST 800-161 R1 Level 2 SA-3
NIST 800-161 R1 Level 3 SA-3
NIST 800-171 R2 (source) NFO - SA-3
NIST 800-218 PO.1
NIST CSF 2.0 (source) GV.SC-09 ID.AM-08 PR.PS-02 PR.PS-03
NIST Privacy Framework 1.0 CT.PO-P1 CT.PO-P4 CM.AW-P3
OWASP Top 10 2025 A06:2025
SCF DPMP 2026 5.12
TISAX ISA 6.0.3 5.3.1
UN R155 7.2.2.1(a) 7.2.2.1(b) 7.2.2.1(c) 7.2.2.5
UN ECE WP.29 7.2.2.1(a) 7.2.2.1(b) 7.2.2.1(c) 7.2.2.5
US (15)
EMEA (14)
Framework Mapping Values
EMEA Germany BAIT 2017 7.1 7.2 7.3
EMEA Germany C5 2026 DEV-01.01B
EMEA Spain CCN-STIC 825 op.pl.3 op.exp.5 mp.sw.1
EMEA EU Cyber Resiliency Act 2024 Article 13(14)
EMEA EU DORA 2023 Article 7(a) Article 7(b) Article 7(c) Article 7(d)
EMEA EU DORA RTS 2024 Article 16.1 Article 37.1
EMEA EU EBA GL/2019/04 3.3.1.13(f) 3.5.55
EMEA EU NIS2 2022 Article 21.3
EMEA LUX CCSF 20/750 2020 3.6.2-67
EMEA Saudi Arabia IoT CGIoT-1 2024 1-5-2
EMEA Saudi Arabia CSCC-1 2019 2-13-1
EMEA Saudi Arabia ECC-1 2018 1-5-3-1 1-5-3-2 1-5-3-3 1-5-3-4
EMEA Saudi Arabia OTCC-1 2022 1-4-1-1
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.1.5
APAC (7)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-1526 ISM-1739
APAC Australia Prudential Standard CPS230 2023 25
APAC India SEBI CSCRF 2024 PR.IP.S2
APAC Japan ISMAP 6.1.5.4 14.1
APAC Malaysia RMiT 2025 10.2(c) 10.5
APAC Singapore CCOP CII 2026 3.6.1 A.1.1
APAC Singapore MAS TRM 2021 5.1.2 5.4.1 5.4.4 5.5.2 5.8.1
Americas (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

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

Project & Resource Management (PRM) 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 PRM domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with PRM 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 PRM domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Project & Resource Management -related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Project & Resource Management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The Chief Information Officer (CIO), or similar function, analyzes the organization's business strategy and prioritizes the objectives and resourcing of the security function, based on broader business requirements. ▪ A Project Management Office (PMO), or project management function, enables the implementation of cybersecurity and data protection-related resource planning controls across the System Development Lifecycle (SDLC) for all high-value projects. ▪ The PM function enables project involvement for Information Assurance Program (IAP) as part of the organization's established project management processes to ensure both cybersecurity and data protection principles are identified and implemented.

Level 3 — Well Defined

Project & Resource Management (PRM) 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 PRM 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 PRM domain capabilities are well-documented and kept current by process owners. ▪ A Project Management Office (PMO), or similar function, is appropriately staffed and supported to implement and maintain PRM domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of project and resource management operations (e.g., project management solution). ▪ 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 PRM 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). ▪ The Chief Information Officer (CIO), or similar function, analyzes the organization's business strategy and prioritizes the objectives and resourcing of the security function, based on broader business requirements. ▪ An implemented and operational capability exists to ensure changes to Technology Assets, Applications and/or Services (TAAS) within the Secure Development Life Cycle (SDLC) are controlled through formal change control procedures.

Level 4 — Quantitatively Controlled

Project & Resource Management (PRM) 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. PRM-07_A01 system development life cycle is defined.
  2. PRM-07_A02 the system is acquired, developed and managed using organization-defined system-development life cycle that incorporates information cybersecurity / data privacy considerations.
  3. PRM-07_A03 cybersecurity / data privacy roles and responsibilities are defined and documented throughout the system development life cycle.
  4. PRM-07_A04 individuals with cybersecurity / data privacy roles and responsibilities are identified.
  5. PRM-07_A05 organizational cybersecurity / data privacy risk management processes are integrated into system development life cycle activities.
  6. PRM-07_A06 system pre-production environments are protected commensurate with risk throughout the system development life cycle for the system, system component or system service.
  7. PRM-07_A07 systems or system components that implement the security design principle of procedural rigor are defined.
  8. PRM-07_A08 systems or system components implement the security design principle of procedural rigor.

Evidence Requirements

E-PRM-03 Secure Development Lifecycle (SDLC)

Documented evidence of a secure development lifecycle that the organization utilizes for new initiatives or significant changes to existing initiatives to ensure cybersecurity & data privacy principles are identified and implemented by default.

Resource Management

Technology Recommendations

Micro/Small

  • Defined business processes
  • Product / project management
  • Defined technical requirements
  • Defined business requirements

Small

  • Defined business processes
  • Product / project management
  • Defined technical requirements
  • Defined business requirements

Medium

  • Defined business processes
  • Product / project management
  • Defined technical requirements
  • Defined business requirements
  • System Development Lifecycle (SDLC) governance / oversight

Large

  • Defined business processes
  • Product / project management
  • Defined technical requirements
  • Defined business requirements
  • System Development Lifecycle (SDLC) governance / oversight

Enterprise

  • Defined business processes
  • Product / project management
  • Defined technical requirements
  • Defined business requirements
  • System Development Lifecycle (SDLC) governance / oversight

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.