> 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-xpanse/inventory/upload-or-remove-assets/upload-assets.md). # Upload assets You can add assets to your inventory by submitting an asset upload request, in the form of a CSV file, through the Cortex Xpanse UI. After you've submitted an asset upload request, the requested assets appear in the **Asset Uploads/Removal** table with the status **Pending Review**. Cortex Xpanse will respond to your upload request within five days of submission. The status of each asset will be updated in the **Asset Uploads/Removal** table to either **Accepted**, which indicates that the asset has been added to your inventory, or **Rejected**. Rejected assets will have an explanation for the rejection. ## **Guidelines and restrictions for asset uploads** Before you submit an asset upload request, familiarize yourself with the following guidelines and restrictions: * You can upload domains (paid-level domains and subdomains) and IPv4 ranges. You can upload a single IPv4 address, but it must be submitted as an IPv4 range asset type. Upload of certificates and IPv6 ranges is not yet supported. * An asset upload request can include up to 500 assets. * The asset upload request must follow the CSV formatting requirements described in the [CSV format for upload requests](#UUID-dfea7167-b480-15d0-cbb3-7d0d04e7f455_section-idm234627043560313) section. * You can upload assets to a new business unit, even if the asset is already in your inventory and associated with an existing business unit. {% hint style="info" %} ### Note If an asset upload request has an invalid CSV or includes one or more invalid assets, the entire request will fail, and none of the assets will be uploaded. If this happens, Cortex Xpanse will display an error message indicating what caused the error, so you can fix the problem and resubmit if you choose. {% endhint %} ## **Overlap Analysis** When you submit an asset upload request,Cortex Xpanse automatically creates an overlap analysis report. This report explains the overlap between the new assets in your upload request and your existing inventory, including a breakdown of the overlap by business unit. The overlap analysis report is generated and available as a downloadable CSV file in the UI after you submit your upload request, but before you confirm the final submission. This allows you time to review the report before finalizing the upload. ## How to submit an asset upload request 1. Create and save a CSV file that lists the assets you want to add to your inventory. It is important to format the CSV file correctly, or the upload might fail. Refer to [CSV format for upload requests](#UUID-dfea7167-b480-15d0-cbb3-7d0d04e7f455_section-idm234627043560313) for an example and details about upload request CSV file formatting. 2. Navigate to **Settings** → **Configurations** → **Asset Management** → **Asset Uploads/Removals**. 3. Click the **Asset Upload/Removal** button and select **Add Asset(s)**. 4. Drag and drop or browse to your CSV file to upload it to Cortex Xpanse. The assets will be added to the **Asset Uploads/Removals** table with the status **Pending**, 5. Check the status of your asset upload request as needed on the **Asset Uploads/Removals** page. Within five days of submitting your request, each asset will be **Accepted** and added to the inventory or **Rejected**. Assets that were rejected will include an explanation in the **Decision Reason** field.
CSV format for upload requests An asset upload request is a CSV file that lists the assets you want to add along with the asset types and business units they will be assigned to. It is important to format the CSV file to match the following requirements. Incorrect formatting or typos may cause the upload to fail. **Upload request example** This example shows the correct CSV format for an asset upload request, including the supported values for asset types and supported IP range notation. The headers in your CSV must match the headers shown here. | BusinessUnits | AssetType | Asset | | ------------- | --------- | -------------------- | | BU1, BU2 | Domain | example.com | | BU3 | Domain | example1.com | | BU1 | IP\_Range | 192.0.2.0/32 | | BU2 | IP\_Range | 192.0.2.0-192.0.2.0 | | BU1, BU3 | IP\_Range | 192.0.2.0-192.0.2.24 | | BU2, BU3 | IP\_Range | 192.0.2.0/27 | **Upload request CSV details** The following table provides details about each field that is required in an asset upload request CSV file. | Field | Details | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Business Units |

This is the business unit you want to assign to the asset upon upload.

The header for this field must be written as BusinessUnits.

The business units in your CSV must already exist in Cortex Xpanse and must use the exact same spelling and capitalization.

If you aren't sure which business units are available in your tenant, follow these steps to download the complete list of business units:

1. Go to Settings → Configurations → Asset Management → Asset Uploads/Removals.

2. In the upper righthand corner, click the Asset Upload/Removal button and select Asset Upload.

3. In the Add List of Assets dialog box, click on Business Unit Directory to download the list of business units.

| | Asset Type |

The header for this field must be written as AssetType.

Supported values are Domain and IP\_Range.

| | Asset |

This is the specific domain or IPv4 range you want to add to your inventory.

The header for this field must be written as Asset.

IP ranges can be specified using the following types of notation:

Individual IP addresses can be specified using the following notation:

|
## **Rejection reasons for upload requests** After submitting an upload request, Cortex Xpanse will accept or reject each individual asset. Rejected assets will indicate the reason for the rejection in the **Decision Reason** column of the **Asset Uploads/Removal** table. Rejection reasons include the following: * The asset you uploaded shows registration information that is attributable to an unrelated organization. * The asset you uploaded is currently for sale. * The asset you uploaded is a cloud IP address or the asset you uploaded is a cloud or reserved internal IANA IP address. We do not add these asset types to customer maps. * The asset you uploaded contains your customer’s content. Cortex Xpanse focuses on corporate infrastructure for our telecommunications, ISPs, and other customer leasing organizations. --- # 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://cortex-docs.paloaltonetworks.com/cortex-xpanse/inventory/upload-or-remove-assets/upload-assets.md?ask=&goal= ``` `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.