A.8 Technological controls

A.8.25 Secure development life cycle

Not mandatory by default – decided in your SoA

What it means in plain language

Define rules for securely developing software and systems across the whole lifecycle.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Teams can turn secure development expectations into stage-by-stage controls for analysis, build, test, release, and maintenance. Document who approves security gates, what evidence proves reviews occurred, and how exceptions are recorded. Strong practice links project delivery to risk treatment, so design decisions, code changes, and release outcomes remain traceable for auditor-ready documents.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Security requirements are captured informally in tickets, but there is no lifecycle gate showing when threat modelling, review, or testing must occur before release.
  • Developers use inconsistent secure coding checks, leaving gaps between commit review, branch approval, and deployment; exception handling is undocumented.
  • Post-release fixes are handled reactively, but lessons learned are not fed back into standards, templates, or pipeline controls for future work.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Assign product owner, engineering lead, and security reviewer responsibilities across intake, design, code, test, release, and maintenance. Use a simple lifecycle map that names required security activities, approval points, and bypass conditions. Keep the map aligned to risk: higher-risk changes need stronger review, more test evidence, and explicit sign-off before production.
  • Embed practical tools into delivery work: secure coding checklist, threat modelling worksheet, pull request template, dependency scan output, and release checklist. Each tool should record the change identifier, control owner, date, reviewer, and any residual risk accepted. Keep evidence in the project record rather than in chat threads.
  • Set illustrative cadence for security activities: model new features at design time, review risky code at merge, and sample-release evidence before production. After incidents or near-misses, use corrective action to update patterns, secure coding guidance, or CI/CD gates. Clause 10.1 improvement can capture trend-based enhancements from repeated findings.
  • For outsourced or shared teams, define which security tasks remain with the organization and which are delegated. Require documented review of third-party changes, acceptance testing against security requirements, and traceable remediation for failed checks. A simple RACI matrix and release exception log help show governance without implying the policy itself performs the control.

What an auditor will ask to see

  • Secure Development Policy section showing lifecycle security activities, approval roles, and exception handling for high-risk changes.
  • Threat model, secure coding checklist, or release gate record linked to a specific feature, commit, or production deployment.
  • CI/CD scan output, peer review record, and acceptance test evidence showing security checks completed before release.
  • Corrective action ticket or retrospective note updating development standards after a defect, incident, or repeated control failure.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.25. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.26 — Application security requirements and A.8.29 — Security testing in development and acceptance. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.