> 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-365.md).

# TLS not enforced in SES configuration set misconfiguration detected in code

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_365                           |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | AWS                                        |
| Severity               | MEDIUM                                     |
| Framework              | Terraform, Terraform Plan                  |

## Impact

This rule checks whether the Simple Email Service (SES) Configuration configured in AWS enforces Transport Layer Security (TLS). TLS plays a crucial role in safeguarding the confidentiality and integrity of transmitted data, especially in emails. Not enforcing TLS can potentially expose data to risks such as interception and manipulation.

## How to Fix

*Resource:* aws\_ses\_configuration\_set

* *Arguments:* delivery\_options.tls\_policy

To fix this issue, modify your AWS Simple Email Service (SES) configurations to ensure the enforcement of Transport Layer Security (TLS) usage.

## The revised Terraform code above implements TLS enforcement in the SES configuration set, guaranteeing secure transmission for all outgoing emails. By setting `tls_policy` to `"Require"`, AWS SES will only deliver emails through connections encrypted with TLS. Any attempt to deliver emails over unencrypted SSL/TLS connections will be rejected. \[source,go]

resource "aws\_ses\_configuration\_set" "example" { ...

## delivery\_options { tls\_policy = "Require" } }


---

# 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/appsec-aws-365.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.