SEC09-BP02 Enforce encryption in transit
Require TLS 1.2 or higher for all client to service and service to service traffic, including within VPCs, and disable legacy protocols and ciphers.
Source: AWS Well-Architected Security Pillar, SEC09-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.
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
- API Gateway TLS settings · Cloud console / configuration management
- Internal service TLS configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- ELB security policies · Policy repository / GRC workspace
- CloudFront viewer protocol policy · Policy repository / GRC workspace
First move
Common gaps auditors find
- HTTP listeners still open
- TLS 1.0 or 1.1 accepted
- internal traffic unencrypted
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 sheetSEC09-BP01 Implement secure key and certificate management · SEC09-BP03 Authenticate network communications