What evidence do auditors commonly ask for on SEC11-BP02 Automate testing throughout the development and release lifecycle?

Pipeline configuration with security gates; Scanner findings dashboards; Build failure on critical findings policy; Exception process.

AWS Well-Architected Security Pillar · Application Security

`SEC11-BP02` Automate testing throughout the development and release lifecycle

Embed SAST, SCA, IaC scanning, container image scanning and DAST into CI CD pipelines so vulnerabilities are caught and blocked before deployment.

Source: AWS Well-Architected Security Pillar, SEC11-BP02. 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 AWS Well-Architected Security Pillar in the compliance library.

artefacts

held by a system

at each review

easy

to go live

Source control / CI pipeline

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Pipeline configuration with security gates · Source control / CI pipeline
Scanner findings dashboards · Cloud console / configuration management

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Build failure on critical findings policy · Policy repository / GRC workspace
Exception process · Document repository

First move

Automate the pull from your Source control / CI pipeline. Pull-request approvals, pipeline test results and deployment records from source control, per release.

Common gaps auditors find

scans run but do not block
no IaC scanning
container images deployed without scan

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

SEC11-BP01 Train for application security · SEC11-BP03 Perform regular penetration testing