> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/search-and-investigate/network-queries/network-config-queries.md).

# Network Configuration Queries

Prisma Cloud provides the `config from network where` network query that is based on network configuration, which you can use to identify overly-exposed resources by providing end-to-end network path visibility from any source, such as AWS EC2 virtual machine, DB instance, or Lambda application to any destination, such as the internet, another VPC, or on-premises networks. This visibility in to the associations between security groups and compute instances help you identify network security risks before they become incidents. Prisma Cloud does not send traffic or read network logs for performing network path analysis.

Investigate functions that use the `config from network where` query, require both READ config and READ network permissions to work. While you can you can save your custom RQL queries for `config from network where`, you cannot yet download the query result as a CSV from the console.

Use the `config from network where` RQL, to query Prisma Cloud for network exposure on the following resources:

| Cloud Services | Resources that Support Network Exposure                                                                                                                                                                                                                                                                                                                                                                                                                    |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AWS**        | <ul><li>Network (VPC)</li><li>Internet Gateway</li><li>Subnet</li><li>NACL</li><li>NAT Gateway</li><li>EC2</li><li>ENI</li><li>EIP</li><li>Security Group</li><li>VPC Service Endpoint/PrivateLink</li><li>Route Table</li><li>Transit Gateway and Route Table</li><li>VPC Peering</li></ul>                                                                                                                                                               |
| **Azure**      | <ul><li>Virtual Machine (VM)</li><li>Virtual Machine Scale Set (flexible VMSS, uniform VMSS)</li><li>Network Interface (NIC)</li><li>Subnet</li><li>Public IP Addresses (PIP, PIP prefixes, shared PIP)</li><li>User Define Route (effective UDR)</li><li>Virtual Network (Vnet)</li><li>NAT Gateway</li><li>Loadbalancer (NLB, ALB)</li><li>Application Security Group (ASG)</li><li>Network Security Group (NSG)</li><li>PaaS Services (PgSQL)</li></ul> |
| **GCP**        | <ul><li>Subnet</li><li>VPC Firewall</li><li>Hierarchical Firewall Rules</li><li>BackendService</li><li>FirewallPolicy</li><li>LB ForwardingRule</li><li>VM</li><li>InstanceGroup</li><li>VPC</li><li>NetworkEndpointGroup</li><li>TargetHttpProxy</li><li>TargetHttpsProxy</li><li>TargetInstance</li><li>TargetPool</li><li>TargetSslProxy</li><li>TargetTcpProxy</li><li>URLMap</li></ul>                                                                |

Network exposure queries are currently supported only on AWS, Azure, and GCP cloud environments and are currently not available in the Government and China regions.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/content-collections/search-and-investigate/network-queries/network-config-queries.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.