A.8 Technological controls

A.8.29 Security testing in development and acceptance

Not mandatory by default – decided in your SoA

What it means in plain language

Test security during development and before accepting systems into production.

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

Security testing should be integrated into development and acceptance so the decision to promote software is based on evidence, not optimism. Teams should connect testing with Secure Development Life Cycle and Secure Coding because test design depends on build quality, while unresolved defects should feed corrective action and release risk decisions. Identify who can waive failures, who records acceptance, and what proof is kept when testing is incomplete or overridden.

Common auditor findings to check for

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

  • Release approval files lack security test results, so the acceptance decision cannot show that high-risk defects were checked before deployment.
  • Penetration test findings are filed, but no one owns retesting, so closed issues reappear in later releases without traceable verification.
  • Automated tests exist, yet coverage omits authentication, authorization, and input validation, leaving critical code paths untested at acceptance.

How you can implement it

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

  • Define security test gates for each delivery path: unit-level security checks in the pipeline, dynamic testing for exposed interfaces, and acceptance testing before production release. Make the owner explicit: developers maintain automated tests, quality assurance coordinates execution, and the product or system owner approves release only after material findings are resolved or formally risk-accepted.
  • Link test depth to risk. High-change or internet-facing systems may need targeted penetration testing, abuse-case scenarios, and manual verification of access control, session handling, and error responses; low-risk changes may rely on regression and focused automated tests. Record the rationale for test scope, because the question is whether the selected evidence matches the change, not whether every tool was used.
  • Ensure failed tests create action-tracked defects with severity, fix owner, target date, and retest requirement. Do not let informal chat messages substitute for closure. Keep the test report, defect ticket, retest evidence, and final acceptance sign-off together so later review can confirm the issue was either fixed or accepted through an authorized risk decision.
  • Review test effectiveness after incidents, major defects, or repeated false positives. The security lead and engineering lead should refine test cases, update pipeline rules, and remove obsolete checks that waste time without improving assurance. Retain evidence of lessons learned, changed test scripts, and release notes showing whether exceptions were temporary, approved, and time-bound.

What an auditor will ask to see

  • Security test plan with scope, risk rationale, test owner, and release gate criteria.
  • Automated test results, penetration test report, defect log, and retest confirmation for closed findings.
  • Acceptance sign-off, risk acceptance record, and release notes showing any waived issues and approved conditions.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.8.25 — Secure development life cycle and A.8.28 — Secure coding. 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.