---
title: Configuring IPS for enabling Behavioral Analytics
slug: ag-25x/1098
createdAt: 2026-07-27T04:11:10.704Z
---

For the fresh Installation of IPS, UEBA package will not be available by default for anomaly detection. Admin must add the UEBA package. In case of upgrade of IPS (R7 or earlier to R8 or later), the previous UEBA package is retained. You may download latest UEBA package from Ivanti Support Site ([https://my.pulsesecure.net](https://my.pulsesecure.net/)).

### UEBA Package

To upload the UEBA package:

1. Log in to Ivanti Support Site, [https://my.pulsesecure.net](https://my.pulsesecure.net/).
2. Select Ivanti Policy Secure as product and navigate to the "Ivanti Behavioral Analytics Database" section. Download the package, "ps-ics-ips-behavioral-analytics-v1.0.x.pkg".
3. From the Admin Console, select **System > Behavioral Analytics**.
4. Navigate to Browse and select the UEBA package.
5. Click **Upload & Activate**.
6. Click **Save Changes**.

### Configuring IPS for Adaptive Authentication

To enable adaptive authentication:

1. Select **System > Behavioral Analytics > Configuration**.
2. Under Configurations, select **Enable Behavioral Analytics**.
3. For enabling Adaptive Authentication, select **Enable data collection** during authentication of devices and users.
   - For location-based anomaly detection, select **Enable subnet&#x20;**&#x62;ased location anomaly detection.
4. Enter the Subnet details. For example, 10.11.1.2/24.
5. Enter the location name.
6. Type the location to search and press Enter.
7. Click **Add** to add the location.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/6IU0pLYOODFB-pX6jX2hK_configuringipsforadaptiveauthentication.png" alt caption size="80" width="1348" height="295"}
8. Select **User > User Realms > General.**
9. Under Additional Authentication Server, **Enable Additional Authentication Server**.
   - Select **Enable Adaptive authentication**.
   - Under Authentication #2, select the desired secondary authentication server from the drop-down list.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/-zRtF8uPIATFOp7FL3WKC_configuringipsforadaptiveauthentication1.png" position="flex-start" size="73" width="730" height="315" initialPath="images/configuring_ips_for_adaptive_authentication_1.png" githubPath="images/configuring_ips_for_adaptive_authentication_1.png" darkWidth="730" darkHeight="315" showCaption="false"}

1. Click **Save Changes**.

### Configuring IPS to detect Anomaly Traffic from IoT devices

As a pre-requisite Profiler should have been configured for detecting the anomaly traffic from IoT devices. For more information, see *Profiler Deployment Guide*.

To determine anomaly traffic from IoT devices:

1. Select **System > Behavioral Analytics > Configuration**.
2. Under Configurations, select **Enable Behavioral Analytics**.
3. Select **Enable Network Traffic** from switches.
   - Configure the list of switches in the network from where the required data can be received/forwarded to analytics engine on IPS.
   - **Add the switches&#x20;**&#x6D;anually by adding (Switch IP address/mac address) or add the existing switches under Add Switch from list table. Select **Dynamically add switches from RADIUS and SNMP&#x20;**&#x63;lients to automatically add switches from RADIUS and SNMP clients.
4. Select **Enable Data Collection through SPAN from switch to enable SPAN configuration** for determining unknown domain anomaly for unmanaged devices.
   - Select the network interface (External port/Internal port).
   - (Optional) Enter the IP address of the DNS server and click Add. DNS requests from these servers will not be considered for anomaly detection.
5. Enter the learning duration in days (7-30 days). Learning duration is learning period for unmanaged devices to build the device profile.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/hLb9aHojyicTTpdAdBAwd_configuringipstodetectanomalytrafficfromiotdevices.png" alt caption size="80" width="1346" height="949"}
6. Click **Save Changes.**
7. Configure the role mapping rules for user realm and/or MAC authentication realm.
   - Create new role mapping rule, select **Anomaly attribute under Rule&#x20;**&#x62;ased on and click **Update**.
   - Enter the rule name.
   - Under Rule: If device has any of the following anomaly types:
     - **Any of the anomalies found-** Select this option to detect the device with any anomaly type.
     - **Select from list of anomalies-** Select this option to configure the specific anomaly type from the available list. To detect anomaly traffic from IoT devices configure **Unknown server/Unknown&#x20;**&#x64;omain as anomaly from the list of **Available Anomaly Types**.
   - Select **Stop processing more rules** option to stop evaluating role mapping rules if the user meets the conditions specified for this rule. Ensure that the rule is at the top of the list.
8. Configure the required roles and click **Save Changes**.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/dUgkQ3d_cbnoSCrK88CRB_configuringipstodetectanomalytrafficfromiotdevices1.png" alt caption size="80" width="1347" height="685"}

### Configuring IPS to detect Potential Malware

IPS relies on DNS traffic collected through SPAN to determine the potential malware on the endpoint.

To configure IPS for detecting potential malware:

1. Select **System > Behavioral Analytics > Configuration**.
2. Under Configurations, select **Enable Behavioral Analytics**.
3. Select **Enable Data Collection through SPAN** from switch to enable SPAN configuration for determining DGA based potential malware attacks. This anomaly detection mechanism is supported for both managed and unmanged/IoT devices.
   - Select the network interface (External port/Internal port).
   - (Optional) Enter the IP address of the DNS server and click **Add**. DNS requests from these servers will not be considered for anomaly detection.
   - (Optional) Enter the white listed domains to exempt the domains from anomaly detection.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/mqn0qzITV9FUdCzJ-iYOe_configuringipstodetectpotentialmalware.png" position="flex-start" size="80" width="1348" height="398" initialPath="images/configuring_ips_to_detect_potential_malware.png" githubPath="images/configuring_ips_to_detect_potential_malware.png" showCaption="false"}

1. Configure the role mapping rules for user realm and/or MAC authentication realm.
   - Create new role mapping rule, select **Anomaly attribute** under **Rule based on&#x20;**&#x61;nd click **Update**.
   - Enter the rule name.
   - Under Rule: If device has any of the following anomaly types:
     - **Any of the anomalies found**- Select this option to detect the device with any anomaly type.
     - **Select from list of anomalies**- Select this option to configure the specific anomaly type from the available list. To detect potential malware from IoT devices configure **DGA** as anomaly from the list of **Available Anomaly Types**.
   - Select **Stop processing more rules** option to stop evaluating role mapping rules if the user meets the conditions specified for this rule. Ensure that the rule is at the top of the list.

:::hint{type="info"}
The Administrator can also create Anomaly rules based on Custom Expressions.
:::

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/bw-3rg6tUlYHwI10PFV2N_configuringipstodetectpotentialmalware1.png" position="flex-start" size="80" width="1347" height="687" initialPath="images/configuring_ips_to_detect_potential_malware_1.png" githubPath="images/configuring_ips_to_detect_potential_malware_1.png" showCaption="false"}

1. Click **Save Changes**.
