Configure IoT Security and Cortex XSOAR

1. Log in to IoT Security and from there access Aruba ClearPass settings in Cortex XSOAR.

   1. Log in to IoT Security and then click Integrations.

   2. IoT Security uses Cortex XSOAR to integrate with Aruba ClearPass, and the settings you must configure to integrate with it are in the XSOAR interface. To access these settings, click Launch Cortex XSOAR.
      The Cortex XSOAR interface opens in a new browser window.
   3. If necessary, search for clearpass to locate it among other instances.

2. Configure the Aruba ClearPass integration instance.

   1. Click the Settings icon (

      ) for the preconfigured Aruba ClearPass instance: PANW IoT 3rd Party Aruba Clearpass Integration Instance.
   2. Enter the following and leave other settings at their default values:
      Name: Use the default name of the instance or enter a new one.
      If you change the instance name, remember it because you’re going to use it again when creating jobs that Cortex XSOAR will run. On the other hand, if you keep the default instance name, the jobs will automatically use it.
      Server URL: Enter the Aruba ClearPass server URL (beginning with “https://”).
      Client ID: Enter the client ID that you previously recorded when configuring Aruba ClearPass.
      Client Secret: Enter the client secret that you previously recorded when configuring Aruba ClearPass.
      Run on Single engine: Choose the XSOAR engine that you previously installed.

   3. When finished, click Run test or Test.
      If the test is successful, a Success message appears. If not, check that the settings were entered correctly and then test the configuration again.

   4. After the test succeeds, click Save & exit to save your changes and close the settings panel.
3. (Optional) Create more integration instances to which IoT Security and XSOAR will export device attributes.

   You can add multiple Aruba ClearPass integration instances, each one with settings to communicate through an XSOAR engine with a different ClearPass server. To add another instance, click Add instance. Each additional integration instance must have a unique name, which the jobs you create to use the instance must reference.
4. Edit the preconfigured job that updates ClearPass with custom endpoint attributes incrementally or create a new job.

   1. Copy the name of the integration instance and then navigate to Jobs.
   2. To edit the preconfigured job, search for ClearPass near the top of the page, select PANW IoT Incremental Update to Aruba ClearPass, and then click Edit.
      or
      To create a new job, click New Job at the top of the page.
   3. In the job panel that appears, enter the following and leave the other settings at their default values:
      Recurring: Select this because you want to periodically export endpoint attributes to ClearPass.
      Every: Enter a number and set the interval value (Minutes, Hours, Days, or Weeks) and select the days on which to run the job. (If you don’t select anything, the job runs everyday.) This determines how often XSOAR sends data to ClearPass. It’s important to set an interval that allows enough time for the job to complete, considering factors such as the number of devices involved, the amount of bandwidth and latency in the connection, and the processing speed of the ClearPass server. You might start by running the job every 15 minutes and then increasing it as necessary until each job completes before the next one starts. You can see the run status of a recurring job on the Jobs page. When in progress, its status is Running. When done, its status changes to Completed.
      Name: For the preconfigured job, leave this as is. For a new job, enter a name. Example: ClearPass - Incremental Updates
      Playbook: Choose Incremental Export to Aruba ClearPass- PANW IoT 3rd Party Integration.
      Integration Instance Name: Paste the name of the Aruba ClearPass integration instance you copied earlier. If you leave this field empty, XSOAR uses the preconfigured ClearPass integration instance: PANW IoT 3rd Party Aruba Clearpass Integration Instance.
      PANW IoT Device Custom Attributes: By default, IoT Security exports all device attributes through XSOAR to ClearPass. If you want to export a subset, clear the Export Attribute check box for the ones you don’t want to export.
      When IoT Security connects through XSOAR to Aruba ClearPass, ClearPass automatically generates the custom endpoint attribute names defined here. If you modify any of the names, ClearPass automatically generates the modified names the next time XSOAR connects to it.
      PANW IoT In Scope Tag Enforcement: Select Yes to filter attributes that IoT Security exports to only devices with the Aruba Clearpass tag type and the In Scope tag value. If you don’t want to filter exported attributes by tagged devices, leave this as No. For information about tagging devices in IoT Security, see Tag Management.
      Playbook Poll Interval: Enter a number (the value, though unspecified, is minutes) defining the period of time during which IoT Security must see newly discovered devices or changes in any attribute fields of previously discovered devices to include their attributes in the list it provides to XSOAR for export. It’s common to use the same interval as the one for running the recurring job. However, if you increase the interval between jobs, you can set a shorter interval for polling than that for the job. If you leave it blank, the default poll interval is 15 minutes.
      Site Names: Leave the field empty to export device attributes for all sites. To limit exports to devices at one or more sites, enter comma-separated site names.
   4. Click Update Job or Create new job.
5. Edit the preconfigured job that exports custom endpoint attributes in bulk to ClearPass or add a new job.

   1. To edit the preconfigured job, search for ClearPass near the top of the page, select PANW IoT Bulk Update to Aruba ClearPass, and then click Edit.
      or
      To create a new job, click New Job at the top of the page.
   2. In the job panel that appears, enter the following and leave the other settings at their default values:
      Name: For the preconfigured job, leave this as is. For a new job, enter a name. Example: ClearPass - Bulk Export
      Playbook: Choose Bulk Export to Aruba ClearPass - PANW IoT 3rd Party Integration.
      Integration Instance Name: Paste the name of the Aruba ClearPass integration instance you copied earlier. If you leave this field empty, XSOAR uses the preconfigured ClearPass integration instance: PANW IoT 3rd Party Aruba Clearpass Integration Instance.
      PANW IoT Device Custom Attributes: By default, IoT Security exports all device attributes through XSOAR to ClearPass. If you want to export a subset, clear the Export Attribute check box for the ones you don’t want to export.
      If you defined your own custom endpoint attribute names in ClearPass, replace the default names with those.
      PANW IoT In Scope Tag Enforcement: Select Yes to filter attributes that IoT Security exports to only devices with the Aruba Clearpass tag type and the In Scope tag value. If you don’t want to filter exported attributes by tagged devices, leave this as No. For information about tagging devices in IoT Security, see Tag Management.
      Site Names: Leave the field empty to export device attributes for all sites. To limit exports to devices at one or more sites, enter comma-separated site names.
   3. Click Update Job or Create new job.
6. Continue creating more jobs for other ClearPass integration instances as needed.
7. To enable ClearPass integration instances, return to the Settings page and click Enable for the instances you edited and created.
8. Return to the IoT Security portal and check the status of the Aruba ClearPass integration.

   An integration instance can be in one of the following four states, which IoT Security displays in the Status column on the Integrations page:

   • Disabled means that either the integration was configured but intentionally disabled or it was never configured and a job that references it is enabled and running.
   • Error means that the integration was configured and enabled but is not functioning properly, possibly due to a configuration error or network condition.
   • Inactive means that the integration was configured and enabled but no job has run for at least the past 60 minutes.
   • Active means that the integration was configured and enabled and is functioning properly.

   When you see that the status of an integration instance is Active, its setup is complete.

9. Export device attributes to ClearPass.

   Whenever you want to export device attributes from IoT Security, select the name of the bulk export job that you want to use—the preconfigured job or one you created—and then click Run now. Cortex XSOAR will export device attributes for devices in the IoT Security device inventory through the XSOAR engine to the ClearPass instance that the job references.

   You can do this as often as you want, once a month being a common choice. Each time you do, XSOAR exports the device attributes of all devices in the IoT Security inventory.

   The first time you run a job that references an integration instance triggers XSOAR to report the instance to IoT Security, which then displays the integration instance on the Integrations page.
10. Export the IoT device inventory from IoT Security to Aruba ClearPass.

    After completing the setup, run a bulk export to add all the inventory to ClearPass. To start the bulk export, click Jobs, select PANW IoT Bulk Export to Aruba ClearPass, and then click Run now.

    Although regular, automated incremental updates are now in progress, ClearPass doesn’t yet have a complete device inventory from IoT Security. This requires a bulk data export from IoT Security to ClearPass that you initiate from the XSOAR interface at a time that’s suitable for network operations. To shorten the time required for the bulk export to complete, plan to run it during off-peak hours on a slow day such as a holiday or weekend. Doing this when network traffic is light can shorten the time needed to complete the job.

    During the bulk export and after the job completes, the automated incremental update will continue running every 15 minutes.

    Although it’s possible to run multiple bulk export jobs in parallel, doing so can affect the XSOAR engine performance. Therefore, we advise not running more than one at a time.