Detections
Analytics

2.3.1 Ensure that encryption is enabled for EFS file systems

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

EFS data should be encrypted at rest using AWS KMS (Key Management Service).

Data should be encrypted at rest to reduce the risk of a data breach via direct access to the storage device.

Solution

It is important to note that EFS file system data-at-rest encryption must be turned on when creating the file system. If an EFS file system has been created without data-at-rest encryption enabled, then you must create another EFS file system with the correct configuration and transfer the data.

Steps to create an EFS file system with data encrypted at rest:

From Console:

 - Login to the AWS Management Console and Navigate to the Elastic File System (EFS) dashboard.
 - Select File Systems from the left navigation panel.
 - Click the Create File System button from the dashboard top menu to start the file system setup process.
 - On the Configure file system access configuration page, perform the following actions:

 - Choose an appropriate VPC from the VPC dropdown list.
 - Within the Create mount targets section, check the boxes for all of the Availability Zones (AZs) within the selected VPC. These will be your mount targets.
 - Click Next step to continue.

<xhtml:ol start="5"> - Perform the following on the Configure optional settings page:

 - Create tags to describe your new file system.
 - Choose performance mode based on your requirements.
 - Check the Enable encryption box and choose aws/elasticfilesystem from the Select KMS master key dropdown list to enable encryption for the new file system, using the default master key provided and managed by AWS KMS.
 - Click Next step to continue.

<xhtml:ol start="6"> - Review the file system configuration details on the review and create page and then click Create File System to create your new AWS EFS file system.
 - Copy the data from the old unencrypted EFS file system onto the newly created encrypted file system.
 - Remove the unencrypted file system as soon as your data migration to the newly created encrypted file system is completed.
 - Change the AWS region from the navigation bar and repeat the entire process for the other AWS regions.

From CLI:

 - Run the describe-file-systems command to view the configuration information for the selected unencrypted file system identified in the Audit steps:

aws efs describe-file-systems --region <region> --file-system-id <file-system-id> <xhtml:ol start="2"> - The command output should return the configuration information.
 - To provision a new AWS EFS file system, you need to generate a universally unique identifier (UUID) to create the token required by the create-file-system command. To create the required token, you can use a randomly generated UUID from "https://www.uuidgenerator.net".
 - Run the create-file-system command using the unique token created at the previous step:

aws efs create-file-system --region <region> --creation-token <uuid> --performance-mode generalPurpose --encrypted <xhtml:ol start="5"> - The command output should return the new file system configuration metadata.
 - Run the create-mount-target command using the EFS file system ID returned from step 4 as the identifier and the ID of the Availability Zone (AZ) that will represent the mount target:

aws efs create-mount-target --region <region> --file-system-id <file-system-id> --subnet-id <subnet-id> <xhtml:ol start="7"> - The command output should return the new mount target metadata.
 - Now you can mount your file system from an EC2 instance.
 - Copy the data from the old unencrypted EFS file system to the newly created encrypted file system.
 - Remove the unencrypted file system as soon as your data migration to the newly created encrypted file system is completed:

aws efs delete-file-system --region <region> --file-system-id <unencrypted-file-system-id> <xhtml:ol start="11"> - Change the AWS region by updating the --region and repeat the entire process for the other AWS regions.

See Also

https://workbench.cisecurity.org/benchmarks/19631

Item Details

References: CSCv7|14.8

Plugin: amazon_aws

Control ID: 1a05b66e07c6db5035c33301ae0cf0e5c6f150f195d05bbd744982380563b8c0