What evidence do auditors commonly ask for on SEC06-BP05 Automate compute protection?

Automated patch schedule and its execution records; Automated remediation rules and their trigger history; Dependency scanning results from the CI/CD pipeline; Mean time to patch measured by severity.

What is the most common gap auditors find on SEC06-BP05?

patching raised as tickets that queue behind feature work

AWS Well-Architected Security Pillar · Infrastructure Protection

`SEC06-BP05` Automate compute protection

Automate scanning, patching and remediation of compute resources so protection operations run without human intervention, including dependency freshness checks in the delivery pipeline.

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

Cloud console / configuration management

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

Automated remediation rules and their trigger history · Cloud console / configuration management
Dependency scanning results from the CI/CD pipeline · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Automated patch schedule and its execution records · Policy repository / GRC workspace
Mean time to patch measured by severity · Policy repository / GRC workspace

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

patching raised as tickets that queue behind feature work
remediation automation built but left in report-only mode
dependency scanning absent from the pipeline

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

SEC06-BP04 Validate software integrity · SEC07-BP01 Understand your data classification scheme