What evidence do auditors commonly ask for on SEC11-BP07 Regularly assess security properties of the pipelines?

Pipeline threat model; IAM role review for pipelines; Self hosted runner hardening evidence; OIDC trust policies.

What is the most common gap auditors find on SEC11-BP07?

pipeline roles have AdministratorAccess

AWS Well-Architected Security Pillar · Application Security

`SEC11-BP07` Regularly assess security properties of the pipelines

Treat the CI CD pipeline itself as a sensitive workload and review its IAM roles, secrets handling, runner isolation and tamper resistance regularly.

Source: AWS Well-Architected Security Pillar, SEC11-BP07. 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

hard

to go live

Policy repository / GRC workspace

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

none for this control

periodic reviewEvidence produced at each review

IAM role review for pipelines · Identity provider / directory
Self hosted runner hardening evidence · Source control / CI pipeline

governing documentDocuments that govern the control

Pipeline threat model · Policy repository / GRC workspace
OIDC trust policies · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

pipeline roles have AdministratorAccess
long lived deploy keys
shared runner pool with no isolation

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-BP06 Deploy software programmatically · SEC11-BP08 Build a program that embeds security ownership in workload teams