Evidence of Customer Data Stores Encrypted at Rest
Provide screenshots of system configurations to demonstrate encryption at rest.
The evidence should demonstrate what encryption standards and protocols you require.
Public Facing URL and APIs
Provide evidence of all public-facing web addresses and public-facing APIs that are used to provide your in-scope services.
Encryption In Transit Configurations (Ex. TLS Protocols)
Provide your Transport Layer Security (TLS) configuration settings for the in-scope production network and production API traffic. This evidence should demonstrate that your sensitive data is encrypted in transit.
Additional Guidance
We recommend that you use transport socket layer (TLS) 1.2 or higher encryption for data in transit over public and untrusted networks.
If you do not use TLS 1.2 or higher, explain why in the Evidence Description.
If the service you are using encrypts data by default at rest, please provide the supporting documentation.
Example Evidence (Data Encryption at Rest)
Example Evidence
AWS RDS
AWS S3
AWS DynamoDB
Azure SQL
Associated Unified Control ID | Associated Framework Control |
CTRL-112 | LCL-35 |