> 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-xsiam/cloud-security/network-exposure-detection.md). # Network exposure detection Discover how to identify, prioritize, and remediate internet, outbound, and lateral network exposure risks in Cortex XSIAM. Cortex XSIAM improves network security posture in your public cloud environments. It identifies assets exposed to the internet so you can prioritize and remediate risks. Cortex XSIAM publishes network exposure findings and issues based on out-of-the-box and custom [cloud security rules and policies](/cortex-xsiam/cloud-security/rules-and-policies/cloud-security-rules-and-policies.md). Security teams can review these findings and issues to gain visibility into network exposures, finding answers to the following questions: * Which assets are exposed to the internet? * Which assets can connect to the internet? * Which assets can communicate across VPCs or cloud accounts? * Which protocols, ports, or services are exposed to the internet? * What is the network path between the source and destination? --- # 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-xsiam/cloud-security/network-exposure-detection.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.