> 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/generic-on-premise-data-collectors/broker-vm-data-collector-applets/activate-network-mapper.md).
# Activate Network Mapper
{% hint style="info" %}
This feature is included with a Cortex XSIAM Premium license. It is also included with any other Cortex XSIAM license that includes endpoints or Cortex Cloud Runtime Security.
{% endhint %}
{% hint style="warning" %}
### Prerequisite
After you have configured and registered your Broker VM, you can choose to activate the Network Mapper application.
{% endhint %}
The Network Mapper allows you to scan your network to detect and identify unmanaged hosts in your environment according to defined IP address ranges. The Network Mapper configurations are used to locate unmanaged assets that appear in the Assets table. For more information, see [All assets](/cortex-xsiam/detect-investigate-and-respond-to-threats/asset-management/all-assets.md).
1. Select **Settings** → **Configurations** → **Data Broker** → **Broker VMs**.
2. Do one of the following:
* On the **Brokers** tab, find the Broker VM, and in the **APPS** column, left-click **Add** → **Network Mapper**.
* On the **Clusters** tab, find the Broker VM, and in the **APPS** column, left-click **Add** → Network Mapper.
3. In the **Activate Network Mapper** window, define the following parameters:
| Field | Description |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scan Method | Select the either ICMP echo or TCP SYN scan method to identify your network hosts. When selecting TCP SYN you can enter single ports and ranges together, for example **`80-83, 443`**. |
| Scan Requests per Second | Define the maximum number of scan requests you want to send on your network per second. By default, the number of scan requests are defined as 1000.
Each IP address range can receive multiple scan requests based on it's availability.
|
| Scanning Scheduler | Define when you want to run the network mapper scan. You can select either daily, weekly, or monthly at a specific time. |
| Scanned Ranges | Select from the list of exiting IP address ranges to scan. Make sure to 
after each selection.
IP address ranges are displayed according to what you defined as your Network Parameters.
|
4. **Activate** the applet.
After a successful activation, the **APPS** field displays **Network Mapper** with a green dot indicating a successful connection.
5. In the **APPS** field, left-click the **Network Mapper** connection to view the following scan and applet metrics:
**Scan Details**
| Field | Description |
| ------------------- | --------------------------------------------------------------------------- |
| Connectivity Status | Whether the applet is connected to Cortex XSIAM . |
| Scan Status | State of the scan. |
| Scan Start Time | Timestamp of when the scan started. |
| Scan Duration | Period of time in minutes and seconds the scan is running. |
| Scan Progress | How much of the scan has been completed in percentage and IP address ratio. |
| Detected Hosts | Number of hosts identified from within the IP address ranges. |
| Scan Rate | Number of IP addresses scanned per second. |
**Applet Metrics**
**Resources**: Displays the amount of CPU, Memory, and Disk space the applet is using.
6. Manage the Network Mapper.
After the network mapper has been activated, left-click the **Network Mapper** connection in the **APPS** column to display the Network Mapper settings, and select:
* **Configure** to redefine the network mapper configurations.
* **Scan Now** to initiate a scan.
* **Deactivate** to disable the network mapper.
---
# 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/generic-on-premise-data-collectors/broker-vm-data-collector-applets/activate-network-mapper.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.