> 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-runtime-security/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/how-to-onboard-on-premise-assets-to-cortex-cloud-data-security.md).

# How to onboard on-premise assets to Cortex Cloud Data Security

**Overview of on-premise data security**

The following applets enable you to monitor and secure assets residing in your on-premise environment:

* **File share protection with the DSPM Fileshare applet**: By activating the **DSPM Fileshare** applet, you extend security coverage to your physical infrastructure, enabling classification for SMB and NFS file shares. This allows you to automatically discover stored content, identify sensitive data, and locate shadow backups, ensuring continuous visibility and consistent governance across hybrid and legacy environments.
* **Database visibility with the DSPM Database applet**: The **DSPM Database** applet provides insights into risks associated with data stored in on-premise databases, PostgreSQL and MySQL instances. Whether you are transitioning to the cloud or maintaining assets on-premise, activating this applet offers a customizable way to manage data security and compliance within a single, unified platform.

To extend the capabilities of Cortex Cloud Data Security to your on-premise infrastructure, you use the Broker VM and a specialized application called an applet. The Broker VM is a virtual machine deployed within your local network that acts as a secure, local collector and gateway. It is essential for unifying and packaging data from your on-premise resources before sending them to Cortex Cloud Data Security.

For information about working with Broker VM, see [What is the Broker VM?](/cortex-cloud-runtime-security/data-management/broker-vm/what-is-the-broker-vm.md).

{% hint style="info" %}

### Note

Your data is scanned on the Broker VM itself, and only the metadata and classification results are transmitted from the on-premise environment to Cortex Cloud.
{% endhint %}

**DSPM Fileshare applet**

The **DSPM Fileshare** applet is an application installed directly onto the Broker VM. The applet’s primary role is to establish and manage connections with your on-premise network file shares, including those using the SMB (Server Message Block) and NFS (Network File Sharing) protocols.

Once configured, this applet continuously:

* Accesses the designated file share paths.
* Ingests the file and folder metadata.
* Classifies files and identifies sensitive information.
* Transmits the collected metadata and results securely through the Broker VM to Cortex Cloud.

{% hint style="info" %}

### Note

For information about activating the **DSPM Fileshare** applet, see [Activate DSPM Fileshare](/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/generic-on-premise-data-collectors/broker-vm-data-collector-applets/activate-dspm-fileshare.md).
{% endhint %}

**DSPM Database applet**

The **DSPM Database** applet is an application installed directly onto the Broker VM. It is the core component responsible for auditing and securing your on-premises PostgreSQL and MySQL databases, providing visibility into the risks associated with your stored data.

Once configured, this applet continuously:

* Accesses your on-premise databases, including those containing regulated or confidential information.
* Identifies data that must be stored in accordance with specific compliance standards.
* Classifies database content to identify sensitive information.
* Transmits the collected insights and risk metadata securely through the Broker VM to Cortex Cloud Data Security.

{% hint style="info" %}

### Note

For information about activating the **DSPM Database** applet, see [Activate DSPM Database](#how-to-activate-the-dspm-fileshare-applet).
{% endhint %}

**Activate DSPM Fileshare**

{% hint style="warning" %}

### Danger

* [Set up and configure Broker VM](/cortex-cloud-runtime-security/data-management/broker-vm/set-up-and-configure-broker-vm.md)
* Know the complete path to the files and folders that you want Cortex Cloud to monitor.
* Necessary user permissions to access the network shares. For the SMB connection type, you need the user name and password.
  {% endhint %}

<details>

<summary>How to activate the DSPM Fileshare applet</summary>

1. Select Settings → Configurations → Data Broker → Broker VMs.
2. On the **Brokers** tab, find Broker VM, and in the **APPS** column, click **+ ADD**. In the list of applets, click **DSPM Fileshare**.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>The applet list displays only the applets for which you have permissions.</p></div>
3. Configure the **DSPM Fileshare** settings according to the following steps.

**Activate DSPM Database**

{% hint style="warning" %}

### Warning

* [Set up and configure Broker VM](/cortex-cloud-runtime-security/data-management/broker-vm/set-up-and-configure-broker-vm.md)
* Know the database engine, host, and port for the database you want to connect.
  {% endhint %}

</details>


---

# 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-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/how-to-onboard-on-premise-assets-to-cortex-cloud-data-security.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.