---
title: EFS file systems should have encryption at rest enabled
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > EFS file systems should have encryption
  at rest enabled
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# EFS file systems should have encryption at rest enabled
 
## Description{% #description %}

Amazon Elastic File System (EFS) file systems should have encryption at rest enabled in every AWS region. This rule passes when the file system's `Encrypted` attribute is `true`, as reported by the EFS console or `aws efs describe-file-systems`, and fails otherwise. Encryption at rest uses AWS Key Management Service (KMS) to protect file system contents from unauthorized access.

## Remediation{% #remediation %}

Encryption at rest can be enabled only when a file system is created. Create a new encrypted file system, copy the data from the unencrypted file system to it, and then delete the unencrypted file system, as described in [Encrypting data at rest in Amazon EFS](https://docs.aws.amazon.com/efs/latest/ug/encryption-at-rest.html).

## References{% #references %}

- [Encrypting data at rest in Amazon EFS](https://docs.aws.amazon.com/efs/latest/ug/encryption-at-rest.html)
- [AWS CLI reference: describe-file-systems](https://docs.aws.amazon.com/cli/latest/reference/efs/describe-file-systems.html)
- [CIS Amazon Web Services Benchmarks](https://www.cisecurity.org/benchmark/amazon_web_services)
