> 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/networking/appsec2-aws-74.md).

# AWS Load Balancers do not use strong ciphers misconfiguration detected in code

## Rule Details

|                       |                           |
| --------------------- | ------------------------- |
| Cortex AppSec Rule ID | APPSEC2\_AWS\_74          |
| Category              | Networking                |
| Provider              | AWS                       |
| Severity              | LOW                       |
| Framework             | Terraform, Terraform Plan |

## Impact

The rule is checking whether AWS Load Balancers are configured to use strong encryption ciphers for secure communication. Using weak or outdated encryption ciphers can expose data to interception or manipulation during transmission, making it easier for attackers to exploit vulnerabilities and compromise sensitive information. By ensuring that only strong ciphers are used, organizations can enhance the security of their network traffic, protect customer data, and comply with industry security standards and regulations.

## How to Fix

## To ensure that AWS Load Balancers use strong ciphers, configure the `ssl_policy` argument. Select a pre-defined policy that enforces the use of strong encryption methods. \[source,go]

resource "aws\_lb" "example" { ...

* ssl\_policy = "ELBSecurityPolicy-TLS-1-2-2017-01" ... }

***


---

# 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/networking/appsec2-aws-74.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.