SEC02-BP03 Store and use secrets securely
Store application secrets, database credentials and API keys in AWS Secrets Manager or Parameter Store with encryption, automatic rotation and least privilege access policies.
Source: AWS Well-Architected Security Pillar, SEC02-BP03. 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.
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
- Rotation lambda configuration · Cloud console / configuration management
- Secret access IAM policies · Policy repository / GRC workspace
- Git secret scanning results · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Secrets Manager inventory · Policy repository / GRC workspace
First move
Common gaps auditors find
- secrets in environment variables or code
- no rotation enabled
- broad read access to all secrets
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 sheetSEC02-BP02 Use temporary credentials · SEC02-BP04 Rely on a centralized identity provider