What evidence do auditors commonly ask for on SEC08-BP01 Implement secure key management?

KMS key inventory with rotation status; Key policies; CloudHSM cluster configuration; Key owner mapping.

What is the most common gap auditors find on SEC08-BP01?

AWS managed keys only for sensitive data

AWS Well-Architected Security Pillar · Data Protection

`SEC08-BP01` Implement secure key management

Centralise key management in AWS KMS or CloudHSM, define key hierarchies, use customer managed keys for sensitive data and rotate keys on policy.

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

moderate

to go live

Key management / PKI

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

CloudHSM cluster configuration · Key management / PKI

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

KMS key inventory with rotation status · Policy repository / GRC workspace
Key policies · Policy repository / GRC workspace
Key owner mapping · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Key management / PKI); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

AWS managed keys only for sensitive data
no rotation
broad kms:* in key policies

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

SEC07-BP04 Define scalable data lifecycle management · SEC08-BP02 Enforce encryption at rest