> 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-posture-management/onboard-and-configure/deployment-steps-and-checklist/activate-cortex-cloud/enable-access-to-required-panw-resources/inbound-source-resources.md). # Inbound source resources Review inbound source resources required for Cortex Cloud access. Allow these IPs to connect inbound to your network. These are required for communication with your resources (Broker VM, Syslog) and for collecting data from your SaaS/Cloud environments. Configure your firewall (and relevant receivers) to allow inbound traffic from these Source IPs. Service definitions * Infrastructure: Communication to your on-premise resources (for example, Broker VM, Syslog) * Data collection: Traffic from Cortex Cloud to your network to collect data. * App-ID: `cortex-xdr` {% tabs %} {% tab title="Americas" %} | REGION | INFRASTRUCTURE IP ADDRESSES (ALLOW INBOUND) | DATA COLLECTION IP ADDRESSES (ALLOW INBOUND) | | ------------------ | ------------------------------------------- | -------------------------------------------- | | United States (US) | 34.132.108.184, 34.69.63.16 | 34.66.69.154, 35.202.21.123 | | Canada (CA) | 35.203.108.13, 35.203.101.162 | 34.95.33.72, 34.95.62.136 | | {% endtab %} | | | {% tab title="EMEA (Europe, the Middle East, Africa)" %} | REGION | INFRASTRUCTURE IP ADDRESSES (ALLOW INBOUND) | DATA COLLECTION IP ADDRESSES (ALLOW INBOUND) | | ------------------------ | ------------------------------------------- | -------------------------------------------- | | France (FA) | 34.155.5.117, 34.155.41.247 | 34.163.125.167, 34.163.155.105 | | Germany (DE) | 35.234.118.195, 34.89.183.45 | 34.89.197.46, 34.107.3.224 | | Israel (IL) | 34.165.33.165, 34.165.27.131 | 34.165.131.171, 34.165.120.206 | | Italy (IT) | 34.154.23.156, 34.154.186.12 | 34.154.208.247, 34.154.243.11 | | Netherlands/ Europe (EU) | 34.147.107.51, 34.91.26.125 | 34.90.70.107, 35.204.129.196 | | Poland (PL) | 34.118.48.171, 34.116.202.235 | 34.118.71.237, 34.118.124.130 | | Qatar (QT) | 34.18.34.118, 34.18.39.155 | 34.18.44.71, 34.18.30.132 | | Saudi Arabia (SA) | 34.166.61.81, 34.166.58.213 | 34.166.59.20, 34.166.53.242 | | South Africa (ZA) | 34.35.42.196, 34.35.79.219 | 34.35.69.156, 34.35.60.86 | | Spain (ES) | 34.175.46.46, 34.175.80.182 | 34.175.27.251, 34.175.198.50 | | Switzerland (CH) | 34.65.108.153, 34.65.155.169 | 34.65.225.124, 34.65.89.6 | | United Kingdom (UK) | 35.242.180.163, 34.105.173.229 | 34.105.227.146, 34.105.137.22 | | {% endtab %} | | | {% tab title="JPAC (Asia-Pacific)" %} | REGION | INFRASTRUCTURE IP ADDRESSES (ALLOW INBOUND) | DATA COLLECTION IP ADDRESSES (ALLOW INBOUND) | | ---------------- | ------------------------------------------- | -------------------------------------------- | | Australia (AU) | 34.151.83.236, 34.116.67.90 | 35.197.181.108, 35.197.175.44 | | India (IN) | 35.200.175.78, 34.93.9.198 | 34.93.3.196, 34.93.175.218 | | Indonesia (ID) | 34.128.126.138, 34.128.82.158 | 34.101.158.32, 34.101.79.159 | | Japan (JP) | 35.200.3.131, 34.146.181.233 | 34.85.68.167, 34.84.99.239 | | Singapore (SG) | 35.240.243.57, 34.126.183.208 | 35.247.148.38, 35.247.173.40 | | South Korea (KR) | 34.64.93.168, 34.64.237.45 | 34.64.107.163, 34.64.84.25 | | Taiwan (TW) | 34.80.133.68, 35.234.18.10 | 35.201.142.86, 35.189.176.163 | | {% endtab %} | | | | {% endtabs %} | | | --- # 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-posture-management/onboard-and-configure/deployment-steps-and-checklist/activate-cortex-cloud/enable-access-to-required-panw-resources/inbound-source-resources.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.