Skip to content

EC2 network interfaces should have source/destination checking enabled

This control checks whether source/destination checking is enabled for an Amazon EC2 elastic network interface (ENI) that's managed by users. The control fails if source/destination checking is disabled for the user-managed ENI. This control checks only the following types of ENIs: aws_codestar_connections_managed, branch, efa, interface, lambda, and quicksight.

How to fix

Attribute source_dest_check of aws_network_interface must be true.

Implementation options

Choose the option that matches how you manage Terraform. All options satisfy this control.

Option 1: Terraform AWS provider resources

If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_network_interface.

resource "aws_network_interface" "this" {
  subnet_id = "subnet-12345678"

  source_dest_check = true
}
Which option should I choose?
  • Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
  • Open source module (terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready.
  • Terraform AWS provider resources: manage Terraform resources directly.

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf (CTF) Control: ec2_network_inteface_source_destination_check_enabled

  • AWS Config Managed Rule: EC2_ENIS_SOURCE_DESTINATION_CHECK_ENABLED

  • Powerpipe Control: aws_compliance.control.ec2_network_inteface_source_destination_check_enabled