Skip to main content

More Info:

Unused AWS Elastic Network Interfaces (ENIs) should be removed to follow best practices.

Risk Level

Informational

Address

Cost optimization, Operational Maturity

Compliance Standards

  • APRA CPS 234 (Australia)
  • AWS Startup Security Baseline
  • AWS Well Architected Framework
  • BSI C5 (Germany)
  • Brazil LGPD
  • CCPA / CPRA (California)
  • CIS Critical Security Controls v8
  • CMMC 2.0
  • CSA Cloud Controls Matrix v4
  • DPDPA
  • Digital Operational Resilience Act (EU)
  • HITRUST CSF
  • ISO/IEC 27017
  • ISO/IEC 27018
  • ISO/IEC 27701
  • KSA PDPL
  • MAS Technology Risk Management (Singapore)
  • MITRE ATT&CK (Cloud)
  • NIS2 Directive
  • NIST CSF
  • NIST SP 800-171
  • NYDFS 23 NYCRR 500
  • SOC2
  • SWIFT Customer Security Controls Framework
  • Sarbanes-Oxley IT General Controls
  • UK NCSC Cyber Assessment Framework

Triage and Remediation

Remediation

Using Console

To remediate the unused Elastic Network Interfaces in AWS, you can follow the below steps using AWS console:
  1. Login to AWS console and navigate to the EC2 dashboard.
  2. Click on the “Network Interfaces” option from the left-hand menu.
  3. Sort the list of network interfaces by the “Status” column, and identify the interfaces that have a status of “available” or “detached”. These are the unused interfaces.
  4. Select the unused network interfaces that you want to remove.
  5. Click on the “Actions” dropdown menu and select “Delete network interface”.
  6. A confirmation message will appear. Click on “Yes, Delete” to confirm the deletion of the selected network interfaces.
Once the unused network interfaces are deleted, you have successfully remediated the misconfiguration.

To remediate the misconfiguration of unused Elastic Network Interfaces in AWS, you can follow the below steps using AWS CLI:
  1. First, you need to identify the unused Elastic Network Interfaces (ENIs). To do this, run the following command:
This command will list all the available ENIs that are not currently attached to any EC2 instances.
  1. Once you have identified the unused ENIs, you can delete them using the following command:
Replace <eni-id> with the ID of the unused ENI that you want to delete. You can run this command for each unused ENI that you identified in step 1.
  1. Finally, to confirm that the unused ENIs have been deleted, you can run the following command:
This command should return an empty list, indicating that there are no more available ENIs that are not currently attached to any EC2 instances.
To remediate the misconfiguration of unused Elastic Network Interfaces in AWS using Python, you can use the Boto3 library which is the AWS SDK for Python. Here are the steps to remediate the misconfiguration:
  1. Import the necessary libraries:
  1. Set up logging to capture any errors:
  1. Create an EC2 client using Boto3:
  1. Use the describe_network_interfaces method to get a list of all the network interfaces in your account:
  1. Loop through the response to find all the unused network interfaces and delete them:
  1. Run the script and it will delete all the unused network interfaces in your AWS account.
Note: Please make sure to test this script in a non-production environment before running it in a production environment.
This change forces permanent deletion of the ENI; once you remove the aws_network_interface resource from code and run terraform apply, Terraform will destroy the ENI just like aws ec2 delete-network-interface. Before removing it from code, manually inspect the ENI (description, status = available, attachments, Elastic IP associations) in the AWS Console or via aws ec2 describe-network-interfaces as per the warning, and do not delete ENIs created/managed by other AWS services.Verification: terraform plan should show a single - destroy action for aws_network_interface.UNUSED_ENI_TO_DELETE (or whatever its name is in your config) with no replacements or recreations.

Additional Reading: