> 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/appsec-aws-23.md).

# Not every Security Group rule has a description misconfiguration detected in code

## Rule Details

|                        |                                                       |
| ---------------------- | ----------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_23                                       |
| Category - Subcategory | Public Exposure - Ingress Controls                    |
| Provider               | AWS                                                   |
| Severity               | LOW                                                   |
| Framework              | CloudFormation, Serverless, Terraform, Terraform Plan |

## Impact

This rule ensures that each security group rule has a description to help identify the purpose of the rule. Descriptions improve the manageability and understanding of security group rules.

## How to Fix

To mitigate this issue, ensure that the `Description` field is added to all security group rules in `AWS::EC2::SecurityGroup`, `AWS::EC2::SecurityGroupIngress`, and `AWS::EC2::SecurityGroupEgress` resources.

## Example: \[source,go]

{ "Resources": { "MySecurityGroup": { "Type": "AWS::EC2::SecurityGroup", "Properties": { "GroupDescription": "My security group", "SecurityGroupIngress": \[ { ...

* "Description": "Allow HTTP traffic" } ], "SecurityGroupEgress": \[ { ...
* "Description": "Allow HTTPS traffic" } ] } } } }

***

Resources: MySecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupDescription: My security group SecurityGroupIngress:

* IpProtocol: tcp ...
* Description: Allow HTTP traffic SecurityGroupEgress:
* IpProtocol: tcp ...
* Description: Allow HTTPS traffic

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.