> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-aws-308.md).

# API Gateway method setting is not set to encrypted caching misconfiguration detected in code

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_308                        |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type |
| Provider               | AWS                                     |
| Severity               | HIGH                                    |
| Framework              | Terraform, Terraform Plan               |

## Impact

This rule is verifying whether the API Gateway method setting caching is encrypted. The data caching in API Gateway is necessary to improve the latency of requests. However, if caching is not encrypted, sensitive information can be at risk as attackers could gain unauthorized access to it. Thus, failing to set this feature to encrypted can potentially compromise the security and data privacy, resulting in a data breach.

## How to Fix

*Resource:* aws\_api\_gateway\_method\_settings

* *Arguments:* settings.cache\_data\_encrypted

## To fix this rule, ensure that the settings for API Gateway methods have caching set to encrypted. For example, set the 'settings' block in your terraform code as shown below: \[source,go]

resource "aws\_api\_gateway\_method\_settings" "pass" { rest\_api\_id = aws\_api\_gateway\_rest\_api.fail.id stage\_name = aws\_api\_gateway\_stage.fail.stage\_name method\_path = "path1/GET"

settings { caching\_enabled = true metrics\_enabled = false logging\_level = "INFO"

* cache\_data\_encrypted = true data\_trace\_enabled = false } }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-aws-308.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.