Configure Device Security and Cortex XSOAR

1. Log in to Device Security, and from there access the Aruba AirWave integration settings in Cortex XSOAR.

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

   2. Launch Cortex XSOAR from the Device Security portal.

      Device Security uses Cortex XSOAR to integrate with Aruba AirWave. The settings you must configure are in the Cortex XSOAR interface. To access these settings from the Integrations page, Launch Cortex XSOAR. The Cortex XSOAR interface opens in a new browser tab or window.
   3. Find the Aruba AirWave integration.

      Click Settings in the left navigation menu. Search for Aruba AirWave to locate it among other integrations.

2. Configure the Aruba AirWave integration instance.

   1. Click Add instance to open the settings panel.
   2. In the settings panel, configure the following settings:

      • Name: Use the default name of the instance or enter a new one.
        Remember the instance name because you're going to use it again when creating a job that Cortex XSOAR will run to gather device data from the Aruba AirWave instance specified in this integration instance.
      • Aruba AirWave IP or Hostname: Enter the domain URL of a cloud-hosted Aruba AirWave instance or the FQDN of an on-premises Aruba AirWave server.
      • Username: Enter the username of the Aruba AirWave Read-Only Monitoring & Auditing user account that you created for the Cortex XSOAR engine to use when connecting to Aruba AirWave.
      • Password: Enter the password associated with the user account.
      • Use single engine: When using a cloud-based Cortex XSOAR instance and an on-premises Aruba AirWave server, choose the Cortex XSOAR engine that you want to communicate with the Aruba AirWave server.

   3. When finished, click Run test or Test to test the integration instance.

      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. Create a job for Cortex XSOAR to query Aruba AirWave for floor plan maps and import them to Device Security.

   1. Create a new Cortex XSOAR job.

      Copy the name of the instance you created, click Jobs near the bottom of the left navigation menu, and then click New Job at the top of the page.
   2. Configure the new Cortex XSOAR job.

      In the New Job panel that appears, configure the following and leave the other settings at their default values:

      • Recurring: Select this if you want to periodically import floor plan maps from Aruba AirWave. Clear it if you want to import floor plan maps on demand.
      • Every: If you select Recurring, 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 specific days, then the job will run every day by default. This determines how often Cortex XSOAR queries Aruba AirWave for information about floor plan maps.
      • Name: Enter a name for the job.
      • Playbook: Choose Import Aruba AirWave VisualRF Floor Plans to PANW IoT.
      • Integration Instance Name: Paste the instance name you copied a few moments ago.
   3. Click Create new job and verify that the job appears in the Jobs list.
4. Create a job for Cortex XSOAR to query Aruba AirWave for device details and import them to Device Security.

   1. Create a new Cortex XSOAR job.

      Stay on the Jobs page, and click New Job at the top of the page.
   2. Configure the new Cortex XSOAR job.

      In the New Job panel that appears, configure the following and leave the other settings at their default values:

      • Recurring: Select this if you want to periodically import device details from Aruba AirWave. Clear it if you want to import device details on demand.
      • Every: If you select Recurring, 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 specific days, then the job will run every day by default. This determines how often Cortex XSOAR queries Aruba AirWave for information about device details.
      • Name: Enter a name for the job.
      • Playbook: Choose Import Aruba AirWave VisualRF Clients to PANW IoT.
      • Integration Instance Name: Paste the same instance name you used for the floor plan maps job.
   3. Click Create new job and verify that the job appears in the Jobs list.
5. Enable the jobs and run them.

   If you run the device detail job before the floor plans map job, Device Security will still import device information, but the devices won't appear in the Device Location Map widget.

   1. Check the job status for the jobs you created.

      If the jobs are Disabled, select the appropriate checkboxes and then click Enable.
   2. Run the floor plan maps job.

      After you enable the jobs, select only the checkbox for the floor plan maps job and click Run now. The Run Status should change from Idle to Running.
   3. Run the device details job.

      Once the floor plan maps job Run Status changes to Completed, deselect that job. Select the checkbox for the clients job and click Run now. The Run Status should change from Idle to Running.

   For either job, if you selected Recurring, Cortex XSOAR queries Aruba AirWave for information at the defined intervals and forwards imported information to Device Security.

   If you cleared Recurring, Cortex XSOAR immediately queries Aruba AirWave and forwards imported information to Device Security.
6. Optional Add more jobs for each integration instance.

   If you created more integration instances for multiple on-premises Aruba AirWave servers, add more jobs as necessary. Each Aruba AirWave server requires a separate job.

   Run the job for each integration instance you create. The first time you run a job that references an integration instance, it triggers Cortex XSOAR to report the instance to Device Security, which then displays the integration instance on the Integrations page.
7. Return to the Device Security portal and check the status of the Aruba AirWave integration.

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

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

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