> 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/detect-investigate-and-respond-to-threats/exposure-management/ingest-assets-and-vulnerabilities-from-third-party-applications.md).

# Ingest assets and vulnerabilities from third-party applications

Ingest assets and vulnerabilities into Cortex Exposure Management from Palo Alto Networks sensors and third-party applications.

Cortex Exposure Management gathers asset and vulnerability data from Palo Alto Networks sensors and third-party scanners. See [Exposure Management](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/exposure-management/exposure-management.md) for the list of supported data sources.

## **Ingest assets and vulnerabilities using built-in integrations**

Cortex Exposure Management provides built-in integrations for ingesting assets and vulnerabilities from some third-party applications. These integrations only ingest vulnerabilities and assets associated with CVEs. Ingested assets all appear in Cortex XDR with the asset type **Generic Device** . Assets and vulnerabilities ingested through integrations are available in the following XQL data sets:

* {vendor}\_{product}\_assets\_raw
* {vendor}\_{product}\_vulnerabilities\_raw

How to configure built-in integrations to ingest assets and vulnerabilities

1. Navigate to the **Settings** → **Data Sources & Integrations**.
2. Search for the integration you want to set up, and click **+ Add New**.
3. Complete the **Connect** section on the **New Data Source** page with credentials and other connection details.

   For more information about the fields, click the question mark icon.
4. In the **Collect** section, select the checkbox for **Fetch assets and vulnerabilities**.

   Depending on the vendor, you may be able to select additional types of data to be ingested in this section.
5. Click **Advanced Settings** to specify the fetch settings.
6. Click **Test** to test the configuration. If the test fails, you can **Run Test & Download Debug Log** to debug the error.
7. Click **Connect**. Review the configuration in the summary screen.
8. Click **Finish** to return to the **Data Sources & Integrations** page.

## **Ingest assets and vulnerabilities using the Vulnerability Ingest API**

The Vulnerability Ingest API is a single API endpoint that ingests asset records along with nested vulnerabilities. This API enables you to import vulnerabilities and related assets from your third-party tools directly into your asset inventory and vulnerability management workflows.

Imported assets will be asset type **Generic Device**, and will include vendor and product fields in the asset record. On findings, the **Findings Source** field will indicate **Third Party Scanner**. Data imported with the Vulnerability Ingest API will not be available in an intermediary XQL data set, but will appear in platform datasets such as asset\_inventory and uvm\_findings.

{% hint style="info" %}

### Note

Uploading assets and vulnerabilities with this API requires the **Manage Vulnerabilities** permission, which is under **Vulnerability Management & Import** on the permissions page, and is included in Instance Admin and other admin roles.
{% endhint %}

See the [Vulnerability Management](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM-Platform-APIs/Vulnerability-Management-APIs) API documentation for more information.


---

# 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/detect-investigate-and-respond-to-threats/exposure-management/ingest-assets-and-vulnerabilities-from-third-party-applications.md?ask=<question>&goal=<user_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.