What evidence do auditors commonly ask for on SEC10-BP02 Develop incident management plans?

Incident response plan document; Scenario-specific runbooks (key compromise, data exfil, ransomware); RACI matrix.

What is the most common gap auditors find on SEC10-BP02?

generic IR plan with no AWS specifics

AWS Well-Architected Security Pillar · Incident Response

`SEC10-BP02` Develop incident management plans

Document IR plans covering detection, triage, containment, eradication, recovery and lessons learned, mapped to specific AWS scenarios such as credential compromise.

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

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

none for this control

governing documentDocuments that govern the control

Incident response plan document · Policy repository / GRC workspace
Scenario-specific runbooks (key compromise, data exfil, ransomware) · Policy repository / GRC workspace
RACI matrix · 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

generic IR plan with no AWS specifics
no runbooks for cloud scenarios
plan untested

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

SEC10-BP01 Identify key personnel and external resources · SEC10-BP03 Prepare forensic capabilities