: Set up IoT Security and XSOAR for Tanium Integration
Focus
Focus

Set up IoT Security and XSOAR for Tanium Integration

Table of Contents

Set up
IoT Security
and XSOAR for Tanium Integration

Set up
IoT Security
and
Cortex XSOAR
to integrate with Tanium.
To set up
IoT Security
to integrate through
Cortex XSOAR
with Tanium, configure XSOAR with a Tanium integration instance and a job to import device details and vulnerabilities. You can set the job to run at regular intervals or on demand. The configuration requires the following information from Tanium:
  • Domain URL of a cloud-hosted Tanium server, or an FQDN or IP address of an on-premises Tanium server
  • Username and password of the user account that XSOAR uses when connecting to the Tanium API
To set up
IoT Security
to integrate through a cloud-hosted
Cortex XSOAR
instance with an on-premises Tanium server, you must also add a
Cortex XSOAR
engine to your network.

Cortex XSOAR
Engine Installation

An on-premises XSOAR engine facilitates communications between the
Cortex XSOAR
cloud and an on-premises Tanium server. Although it's possible to install an XSOAR engine on machines running Windows, macOS, and Linux operating systems, only an engine on a Linux machine supports
IoT Security
integrations. For more information about operating system and hardware requirements, see the
Cortex XSOAR
.
We recommend downloading the XSOAR engine using the shell installer script and installing it on a Linux machine. This simplifies the deployment by automatically installing all required dependencies and also enables remote engine upgrades.
When placing the XSOAR engine on your network, make sure it can form HTTPS connections to your on-premises Tanium server. By default, HTTPS uses TCP port 443.
The firewall must also allow the engine to form HTTPS connections on TCP port 443 to the Cortex cloud at https://<your-domain>.iot.demisto.live/. You can see the URL of your XSOAR instance when you log in to the
IoT Security
portal and click
Integrations
Launch
Cortex XSOAR
. It’s visible in the address bar of the web page displaying the XSOAR interface.
To create an XSOAR engine, access the
Cortex XSOAR
interface (from the
IoT Security
portal, click
Integrations
Launch
Cortex XSOAR
). Click
Settings
Engines
+ Create New Engine
. Choose
Shell
as the type.
For installation instructions, see Install .
For help troubleshooting
Cortex XSOAR
engines, including installations, upgrades, connectivity, and permissions, see Troubleshoot and Troubleshoot Integrations Running on Engines.

Configure
IoT Security
and
Cortex XSOAR

  1. Log in to
    IoT Security
    and from there access Tanium settings in
    Cortex XSOAR
    .
    1. Log in to
      IoT Security
      and then click
      Integrations
      .
    2. IoT Security
      uses
      Cortex XSOAR
      to integrate with Tanium, 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
      tanium
      to locate it among other instances.
  2. Configure the Tanium integration instance.
    1. Click
      Add instance
      to open the settings panel.
    2. Enter the following settings:
      Name
      : Use the default name of the instance or enter a new one.
      Remember the instance name because you are going to use it again when creating a job that
      Cortex XSOAR
      will run to gather data from the Tanium instance specified in this integration instance.
      Domain URL
      : Enter the domain URL of a cloud-hosted Tanium instance or static IP address of an on-premises Tanium server. Note that you can include or omit
      https://
      from the URL. Both of these formats are acceptable:
      • https://<customername>-api.cloud.tanium.com
      • <customername>-api.cloud.tanium.com
      Username
      : Type the name of the user account that you previously created for the XSOAR engine to use when connecting to the Tanium API.
      Password
      : Type the password associated with the user account.
      Use single engine
      : When using a cloud-based XSOAR instance and an on-premises Tanium server, choose the XSOAR engine that you want to communicate with the Tanium server.
    3. When finished, click
      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
      Done
      to save your changes, close the settings panel, and activate the instance.
  3. To integrate with other Tanium servers, repeat the previous steps to add more integration instances.
  4. Create a job for XSOAR to query Tanium for device vulnerabilities and import them to
    IoT Security
    .
    IoT Security
    only imports vulnerabilities for devices that are already in its database and whose MAC address matches that Tanium returns. If Tanium returns vulnerabilities for MAC addresses that aren’t in the
    IoT Security
    database, they’re ignored and dropped.
    1. Copy the name of the instance you just created, click
      Jobs
      near the bottom of the left navigation menu and then click
      New Job
      at the top of the page.
    2. In the New Job panel that appears, enter the following and leave the other settings at their default values:
      Recurring
      : Select this if you want to periodically import vulnerabilities from Tanium. Clear it if you want to import them 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 everyday by default.) This determines how often XSOAR queries Tanium for device vulnerabilities. For example, every day at 2:00 AM.
      Name
      : Enter a name for the job.
      Playbook
      : Choose
      Import Tanium Vulnerabilities to PANW IoT cloud
      .
      Integration Instance Name
      : Paste the instance name you copied a few moments ago.
      Import vulnerabilities by CVE severity levels
      : Choose one or more severity levels to determine which vulnerabilities to import:
      Critical
      ,
      High
      ,
      Medium
      ,
      Low
      , or
      Unscored
      (that is, there is no severity score). Choosing all five severities is the same as not choosing any.
      The severity levels are based on Common Vulnerability Scoring System version 3 (CVSSv3).
    3. Click
      Create new job.
  5. Enable the job and run it.
    1. Check the Job Status for the job you created. If it’s Disabled, select its check box and then click
      Enable
      .
    2. After you enable it, keep the check box selected and click
      Run now
      . The Run Status changes from Idle to Running.
      If you selected
      Recurring
      , XSOAR queries Tanium for device vulnerabilities at the defined interval and forwards imported information to
      IoT Security
      .
      If you cleared
      Recurring
      , XSOAR immediately queries Tanium and forwards imported device vulnerabilities to
      IoT Security
      .
  6. If you created more integration instances for multiple on-premises Tanium servers, add more jobs as necessary.
    Each Tanium 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 XSOAR to report the instance to
    IoT Security
    , which then displays the integration instance on the Integrations page.
  7. When done, return to the
    IoT Security
    portal and check the status of the Tanium 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 its status is
    Active
    , the setup is complete.

Recommended For You