> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec2-aws-5.md).

# Security Groups are not attached to EC2 instances or ENIs misconfiguration detected in code

## Rule Details

|                        |                                    |
| ---------------------- | ---------------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_5                    |
| Category - Subcategory | Public Exposure - Ingress Controls |
| Provider               | AWS                                |
| Severity               | LOW                                |
| Framework              | Terraform, Terraform Plan          |

## Impact

Security groups are an important layer of security for Amazon EC2 instances and network interfaces (ENIs). They act as a virtual firewall for your instances, controlling inbound and outbound traffic to and from your instances. By attaching security groups to your EC2 instances or ENIs, you can specify which traffic is allowed to reach your instances, and which traffic is blocked. This can help to protect your instances from unauthorized access and prevent potential security vulnerabilities.

## How to Fix

*Resource:* aws\_network\_interface, aws\_instance, aws\_security\_group

* *Arguments:* *security\_groups* of aws\_instance or aws\_security\_group { "resource "aws\_network\_interface" "test" { subnet\_id = "aws\_subnet.public\_a.id" security\_groups = \[aws\_security\_group.ok\_sg.id] }

resource "aws\_instance" "test" { ami = "data.aws\_ami.ubuntu.id" instance\_type = "t3.micro" security\_groups = \[aws\_security\_group.ok\_sg.id] }

resource "aws\_security\_group" "ok\_sg" { ingress { description = "TLS from VPC" from\_port = 443 to\_port = 443 protocol = "tcp" cidr\_blocks = 0.0.0.0/0 }

## } ", }


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec2-aws-5.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.