> 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/cortex-cloud-runtime-security/network-exposure-detection/outbound-exposure-detection.md).

# Outbound exposure detection

Learn about detecting workloads with unrestricted outbound internet access based on security configurations.

CNA supports outbound internet exposure detection. If CNA detects a workload that based on their security configurations has unrestricted internet access, CNA generates a finding.

This helps you determine which assets have potentially unrestricted access to the internet, taking into account the effect of cloud native security controls, network firewalls and NAT gateways. It allows you to:

* Visualize the complete network path of an asset from source to destination.
* Periodically re-validate the status of an exposed asset.
* Find which security group or firewall rule is causing the exposure.

#### Outbound exposure rules

Outbound exposure rules do not have out of the box rules, but you can create custom ones. See [Create a Network Exposure Rule](/cortex-cloud-runtime-security/rules-and-policies/cloud-security-rules-and-policies/cloud-security-rules.md).

#### Supported asset types

CNA can detect outbound internet exposure in the following cloud services and asset types:

| **Provider/ Service**        | **AWS**    | **Azure** | **GCP** |
| ---------------------------- | ---------- | --------- | ------- |
| **Managed virtual machines** | Amazon EC2 | –         | –       |


---

# 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/cortex-cloud-runtime-security/network-exposure-detection/outbound-exposure-detection.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.