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.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Rotation lambda configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Secrets Manager inventory · Policy repository / GRC workspace
- Secret access IAM policies · Policy repository / GRC workspace
- Git secret scanning results · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
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