ISO 27001:2022
Technological controls – ISO 27001:2022

ISO 27001:2022 8.25: Secure development life cycle

The organization is to set and apply rules for developing software and systems securely. Purpose (stated in ISO/IEC 27002:2022): builds security into software and systems from design through implementation. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.25.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 107 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 11 controls

CIS Controls v8 · 10 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.14 Conduct Threat Modeling
  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-16.4 Establish and Manage an Inventory of Third-Party Software Components
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-16.9 Train Developers in Application Security Concepts and Secure Coding

FedRAMP High · 9 controls

  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))
  • SA-10 Developer Configuration Management
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-15(3) Development Process, Standards, and Tools | Criticality Analysis (SA-15(3))
  • SA-3 System Development Life Cycle
  • SA-4(1) Acquisition Process | Functional Properties of Controls (SA-4(1))
  • SA-4(2) Acquisition Process | Design and Implementation Information for Controls (SA-4(2))
  • SA-8 Security and Privacy Engineering Principles

FedRAMP Moderate · 9 controls

  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))
  • SA-10 Developer Configuration Management
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-15(3) Development Process, Standards, and Tools | Criticality Analysis (SA-15(3))
  • SA-3 System Development Life Cycle
  • SA-4(1) Acquisition Process | Functional Properties of Controls (SA-4(1))
  • SA-4(2) Acquisition Process | Design and Implementation Information for Controls (SA-4(2))
  • SA-8 Security and Privacy Engineering Principles

PCI DSS 4.0 · 9 controls

  • 12.6.1 12.6.1 Formal security awareness program
  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.2.3 6.2.3 Code review before release
  • 6.2.3.1 6.2.3.1 Manual code review independence and approval
  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 9.2.4 9.2.4 Locking of consoles in sensitive areas
  • 6.4.3 6.4.3 Payment page script management
  • 6.5.1 6.5.1 Change control procedure for production
  • 8.6.2 8.6.2 No hard-coded passwords for interactive system accounts

ISO/IEC 42001:2023 · 8 controls

  • 8.3 AI risk treatment
  • A.5.4 Assessing AI system impact on individuals or groups of individuals
  • A.6 AI system life cycle
  • A.6.1.3 Processes for responsible design and development of AI systems
  • A.6.2.2 AI system requirements and specification
  • A.6.2.3 Documentation of AI system design and development
  • A.7.3 Acquisition of data
  • A.9 Use of AI systems

NIST SP 800-218 · 8 controls

ISO 27002:2022 · 6 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles
  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • 8.30 Outsourced development

ISO 27701:2019 · 5 controls

  • 6.11 Systems acquisition, development and maintenance
  • 6.11.1 Security requirements of information systems
  • 6.11.2 Security in development and support processes
  • 7.4 Privacy by design and privacy by default
  • 8.4 Privacy by design and privacy by default

CMMC 2.0 · 4 controls

AWS Well-Architected Security Pillar · 3 controls

  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP04 Conduct code reviews
  • SEC11-BP07 Regularly assess security properties of the pipelines

Azure Security Benchmark · 3 controls

  • ASBv3-DS-3 Secure DevOps infrastructure
  • ASBv3-GS-10 Define and implement DevOps security strategy
  • DS-6 Enforce security of workload throughout DevOps lifecycle

COBIT 2019 · 3 controls

  • BAI03.03 BAI03.03 Develop solution components
  • BAI03.05 BAI03.05 Build solutions
  • BAI03.12 BAI03.12 Design solutions based on the defined development methodology

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

  • CCM-AIS-01 Application and Interface Security Policy and Procedures
  • CCM-AIS-04 Secure Application Design and Development
  • CCM-DSP-07 Data Protection by Design and Default

C5 (Germany) · 2 controls

  • C5-DEV-01 Policies for the development/procurement of information systems
  • C5-DEV-03 Policies for changes to information systems

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-161 Rev 1 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-01 Train Operational Teams in Information System Security

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-4 Formal vulnerability management program

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-5 Systems Development and Quality Assurance Category

EU AI Act · 1 control

ISO 27001:2013 · 1 control

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST SP 800-171 Rev 3 · 1 control

  • 03.16.01 Security Engineering Principles

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Technological controls – ISO 27001:2022

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 8.25 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gapsIf you hold ISO 27001:201383.9% covered · 15 gapsIf you hold FedRAMP Moderate80.6% covered · 18 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gapsIf you hold C5 (Germany)69.9% covered · 28 gapsIf you hold NIST Cybersecurity Framework 2.063.4% covered · 34 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 107 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll ISO 27001:2022 controls