Control: 5 API Gateway REST API cache data should be encrypted at rest
Description
This control checks whether all methods in API Gateway REST API stages that have cache enabled are encrypted. The control fails if any method in an API Gateway REST API stage is configured to cache and the cache is not encrypted.
Encrypting data at rest reduces the risk of data stored on disk being accessed by a user not authenticated to AWS. It adds another set of access controls to limit unauthorized users ability access the data. For example, API permissions are required to decrypt the data before it can be read.
API Gateway REST API caches should be encrypted at rest for an added layer of security.
Remediation
To remediate this control, configure the stage to encrypt the cache data.
To configure API caching for a given stage
Open the API Gateway console
Choose the API.
Choose
Stages
.In the
Stages
list for the API, choose the stage to add caching to.Choose
Settings
.Choose
Enable API cache
.Update the desired settings, then select
Encrypt cache data
.Choose
Save Changes
.
Usage
Run the control in your terminal:
powerpipe control run aws_compliance.control.foundational_security_apigateway_5
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run aws_compliance.control.foundational_security_apigateway_5 --share
SQL
This control uses a named query:
apigateway_stage_cache_encryption_at_rest_enabled