> 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/storage/appsec-aws-42.md).

# AWS Elastic File System (EFS) with encryption for data at rest is disabled misconfiguration detected

## Rule Details

|                        |                                                       |
| ---------------------- | ----------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_42                                       |
| Category - Subcategory | Storage - Encryption                                  |
| Provider               | AWS                                                   |
| Severity               | LOW                                                   |
| Framework              | CloudFormation, Serverless, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule  | 5eb50d57-7e94-4204-a4e7-3471b3f7e82e                  |

## Impact

Amazon Elastic File System (Amazon EFS) is a simple, scalable file storage solution for AWS services and on-premises resources. Amazon EFS is built to elastically scale on-demand. It grows and shrinks automatically as files are added and removed. It is essential to encrypt your Amazon EFS to protect data and metadata against unauthorized access. Encrypting your Amazon EFS also fulfils compliance requirements for data-at-rest encryption when file systems are used in production systems.

## How to Fix

*Resource:* AWS::EFS::FileSystem

* *Arguments:* Encrypted - (Optional) If true, the disk will be encrypted. If you are using AWS KMS you can optionally provides a KMS customer master key. \[source,go]

***

Resources: FileSystemResource: Type: 'AWS::EFS::FileSystem' Properties: ...

* Encrypted: true

***


---

# 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/storage/appsec-aws-42.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.