A.8.29 Security testing in development and acceptance
Security testing processes are to be defined and carried out within the development life cycle. Purpose (stated in ISO/IEC 27002:2022): checks that code and applications satisfy security requirements before they reach production. 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.29.
Source: ISO/IEC 27001:2022, A.8.29. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.
Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Security test results covering authentication, access restriction, cryptography, secure coding and configuration · Identity provider / directory
- Independent acceptance test records including code review, vulnerability scanning and penetration test findings · Vulnerability scanner / patch tooling
- Records verifying that security defects were remediated before go-live · Document repository
governing documentDocuments that govern the control
- Statement of Applicability entry for control A.8.29, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
- Security test plans with schedules, inputs, expected outputs, evaluation criteria and decisions, scaled to the system's importance and change impact · Policy repository / GRC workspace
First move
Common gaps auditors find
- Security testing is skipped for minor releases that still change security functions
- Developers test their own code with no independent acceptance testing
- Penetration test findings are released into production unresolved
- Test environments differ significantly from production, so results are unreliable
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet