> 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-xdr-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/configure-cortex-xdr-network-parameters.md).
# Configure Cortex XDR network parameters
Define the IP address ranges and domain names used by Cortex XDR to identify your network assets.
Define your internal IP address ranges and domain names to enable Cortex XDR to identify, track, and analyze network assets.
**Define internal IP address ranges**
The **IP Address Ranges** page displays the address ranges that Cortex XDR Analytics monitors. Addresses are pre-populated with the default IPv4 and IPv6 address spaces. The names you define appears when investigating the network-related events in Cortex XDR.
You can add a new IP address range manually or upload IP address ranges from a CSV file.
How to define internal IP address ranges
1. Select **Inventory** → **Assets** → **Network Configuration** → **Internal IP Address Ranges**.
2. Do one of the following:
| To | Do this |
| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Add a new IP address manually | 1. Click Add New Range → Create New, and then enter the IP address name and IP address range or CIDR values.
By default, Cortex XDR creates Private Network ranges that specify reserved industry-approved ranges. Private Network ranges are marked with a 
icon and you can only edit the name.
Note
You can add a range that is fully contained in an existing range, however, you cannot add a new range that partially intersects with another range.
2. Click Save.
|
| Upload IP address ranges from a CSV file | 1. Select Inventory+Assets → Network Configuration → IP Address Ranges.
2. Click Add New Range → Upload from File.
3. Locate the CSV file you want to upload, and then click Add.
|
**Define internal domain names**
1. Select **Inventory** → **Assets** → **Network Configuration** → **Internal Domain Suffixes**.
2. Type the domain suffix you want to include as part of your internal network, for example, **`acme.com`**.
3. Select  to add the suffix to the **Domains List**.
---
# 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-xdr-5.x/configure-cortex-xdr/configure-and-deploy-cortex-xdr/configure-cortex-xdr-network-parameters.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.