Triage and Remediation
- Remediation
Remediation
Using Console
Using Console
To remediate the EFS Encryption Enabled misconfiguration in AWS, you can follow the below steps:
- Open the AWS Management Console and navigate to the Amazon Elastic File System (EFS) service.
- Select the EFS file system that needs to be remediated.
- Click on the “Actions” button and select “Modify file system”.
- In the “Modify file system” window, scroll down to the “Encryption” section.
- Disable the encryption by selecting “No” for the “Encrypt file system” option.
- Click on the “Modify” button to save the changes.
- Once the changes are saved, the EFS file system will be unencrypted.
Using CLI
Using CLI
To remediate the misconfiguration of EFS Encryption Enabled in AWS using AWS CLI, follow these steps:Replace Replace
- Open the AWS CLI on your local machine.
- Run the following command to get a list of all the EFS file systems in your AWS account:
- Identify the EFS file system that has encryption disabled.
- Run the following command to enable encryption for the identified EFS file system:
<file-system-id> with the ID of the EFS file system that you want to enable encryption for.- Verify that encryption is enabled for the EFS file system by running the following command:
<file-system-id> with the ID of the EFS file system that you enabled encryption for.- Repeat the above steps for all the EFS file systems in your AWS account that have encryption disabled.
Using Python
Using Python
To remediate the EFS Encryption Enabled misconfiguration in AWS using Python, follow these steps:Make sure to replace
- Open the AWS console and navigate to the EFS service.
- Select the EFS file system that has encryption enabled.
- Click on the “Modify” button in the top menu bar.
- Scroll down to the “Encryption” section and select “No” in the “Encryption” dropdown menu.
- Click on the “Save” button to disable encryption for the EFS file system.
fs-12345678 with the actual ID of the EFS file system that you want to remediate.Using Terraform
Using Terraform
encrypted/kms_key_id on an existing aws_efs_file_system forces replacement of the file system, which deletes the old one and its data; plan carefully to avoid outage and data loss.To verify, terraform plan should show either:- creating a new
aws_efs_file_systemwithencrypted: "true"and the desiredkms_key_id, or - replacing the existing file system where the diff includes
encrypted: "false" => "true"(and/or a change tokms_key_id) with-/+on the resource.

