> 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/investigate-an-internet-exposure.md). # Investigate an internet exposure Investigate internet-exposed assets through Issues and Graph Search. You can investigate assets exposed to the internet by reviewing issues detected by Cloud Network Analyzer or by using Graph Search. ### Investigate internet exposure issues Review internet exposure issues to learn which assets are exposed to the internet. You can find internet exposure issues under **Cases & Issues**. 1. Go to **Cases & Issues**. 2. Select the **Detection Method** filter and then select the **Cloud Network Analyzer** as the **Detecting Engine**. 3. Select a specific issue to investigate. You can review: * Affected asset * Policy that triggered the exposure * Exposure details (Public IP, FQDN, protocol, port, and HTTPs response code) * Exposure path 4. From an issue, navigate to an affected asset. Then open the **Network** tab. The **Network** tab provides in-depth visibility into network details and internal reachability:

The Network tab is currently only available for virtual machines. It is only displayed when you have access to the main asset and associated ones, such as security groups, VPCs, and subnets. For more information about configuring granular scoping, see Manage user scope.

* **Networking Details:** Access details such as where the VM is deployed, connected subnets, and associated network security controls. Review a visual representation of the asset and all connected private IPs. * **Networking Security Rules:** Investigate the network rules associated with the asset. ### Investigate internet-exposed assets using Graph Search You can use [What is Graph Search?](/cortex-cloud-runtime-security/graph-search/what-is-graph-search.md) to search for and investigate internet-exposed assets. 1. Go to **Investigation and Response** → **Search** → **Query Builder** → **Graph Search**. 2. Define a query that finds selected assets where Internet Exposed = True: 1. Select one or more specific asset types that are supported by CNA exposure detection, such as a **Virtual Machine** or a **Kubernetes Workload**. 2. Add a condition **WHERE Internet Exposed = True**. 3. Click **Search**. 4. Click on an object and then click on **View Details** to view details of the asset. 5. Open the **Network** tab. The **Network** tab provides in-depth visibility into network details and internal reachability:

The Network tab is currently only available for virtual machines. It is only displayed when you have access to the main asset and associated ones, such as security groups, VPCs, and subnets. For more information about configuring granular scoping, see Manage user scope.

* **Networking Details:** Access details such as where the VM is deployed, connected subnets, and associated network security controls. Review a visual representation of the asset and all connected private IPs. * **Networking Security Rules:** Investigate the network rules associated with the asset. --- # 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/investigate-an-internet-exposure.md?ask=&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.