AIMS 2

1. Log in to Device Security and then access the AIMS 2 settings in Cortex XSOAR.

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

   2. Device Security uses Cortex XSOAR to integrate with AIMS 2, 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. Click Settings in the left navigation menu, search for aims to locate it among other instances.

2. Configure an AIMS 2 integration instance.

   1. Click Add instance to open the settings panel.
   2. Enter the following and leave other settings at their default values:
      Name: Use the default name of the instance (AIMS_instance_1) or enter a new one.
      Remember the instance name because you are going to use it again when creating jobs that Cortex XSOAR will run.
      AIMS Server (IP or hostname): Enter IP address or domain name of the AIMS server followed by the port number on which it listens for connection requests. By default, it listens on TCP port 443. For example: 10.1.1.150:443
      Auth Token: Enter the client ID that you recorded earlier when setting up AIMS.
      Trust any certificate (not secure): (select)
      Use single engine: For cloud-based AIMS systems, choose No engine. For on-premises AIMS systems, choose the Cortex 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. Enable the AIMS 2 integration instance.
4. Create a job that retrieves device data from AIMS 2 through XSOAR to Device Security.

   This job regularly imports device data from AIMS through Cortex XSOAR to Device Security.

   1. Click Jobs near the bottom of the left navigation menu to open the Jobs page.
   2. Click New Job at the top of the Jobs page.
   3. Enter the following, leave the other fields at their default values:
      Name: Type a name for the job such as AIMS device retrieval.
      Time triggered: (select)
      Recurring: (select)
      • Every: Enter the number of hours, minutes, days, or weeks to check AIMS for device data. Typically, shorter intervals provide more timely updates for active networks. However, for large networks, more frequent updates might exacerbate an already heavy traffic load. Weigh the two factors of activity and size when deciding and remember that you can always edit the playbook later to adjust this setting.
      • On: Select the days of the week that this job will run, or leave them unselected to run everyday.
      Playbook: Export AIMS maps and devices to PANW IoT
      Integration Instance Name: Enter the name of the AIMS integration instance you defined earlier. For example:

   4. When complete, Create new job.
5. Create a job that periodically retrieves work order assignee and priority lists from AIMS 2.

   This retrieves a list of employees and work order priority levels that populate fields in the Send Work Order dialog box in the Device Security portal. This allows the Device Security user to select this information when generating AIMS work orders to investigate security incidents.

   1. On the Jobs list, click New Job at the top of the Jobs page.
   2. Enter the following, leave the other fields at their default values:
      Name: Type a name for the job such as AIMS assignee and priority lists retrieval.
      Time triggered: (select)
      Recurring: (select)
      • Every: Enter the number of hours, minutes, days, or weeks to retrieve AIMS employee and work order priority lists.
      • On: Select the days of the week that this job will run, or leave them unselected to run everyday.
      Playbook: Export AIMS assignee and priority list to PANW IoT
      Integration Instance Name: Enter the name of the AIMS integration instance you defined earlier. For example: AIMS_instance_1

6. When complete, Create new job.

   Run a job for each integration instance you create. The first time you run a job that references an integration instance triggers XSOAR to report the instance to Device Security, which then displays the integration instance on the Integrations page.
7. When done, return to Device Security and check the status of the AIMS 2 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.