IoT Security Integration Guide
    : Set up IoT Security and XSOAR for BlueCat Integration
    Focus
    Download PDF
    Focus
    1. Home
    2. IoT
    3. IoT Security Integration Guide
    4. IP Address Management
    5. Set up IoT Security and XSOAR for BlueCat Integration
    Download PDF

    IoT Security Integration Guide

    Set up IoT Security and XSOAR for BlueCat Integration

    Table of Contents

    Set up IoT Security and XSOAR for BlueCat Integration

    Set up IoT Security and Cortex XSOAR to integrate with BlueCat.
    To set up IoT Security to integrate through Cortex XSOAR with a BlueCat Address Manager, you must add an XSOAR engine to your network.
    You must also configure Cortex XSOAR with a BlueCat IPAM integration instance and a job to periodically collect IPAM data from the BlueCat Address Manager. To do this, you need the IP address or hostname of the BlueCat Address Manager API and the username and password of the read/write user account that the XSOAR engine will use when forming a secure connection with it.

    Cortex XSOAR Engine Installation

    An on-premises XSOAR engine facilitates communications between the Cortex XSOAR cloud and a BlueCat Address Manager. 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 Administrator’s Guide.
    We recommend downloading the Cortex 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 HTTP or HTTPS connections to the API of your BlueCat Address Manager.
    The on-premises firewall must allow the Cortex XSOAR 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 Cortex XSOAR instance when you log in to the IoT Security portal and click Integrations and then click Launch Cortex XSOAR. It’s visible in the address bar of the web page displaying the Cortex XSOAR interface.
    To create an Cortex XSOAR engine, access the Cortex XSOAR interface (from the IoT Security portal, click Integrations and then click Launch Cortex XSOAR). In the Cortex XSOAR UI, click SettingsEngines+ Create New Engine. Choose Shell as the type.
    For Cortex XSOAR engine installation instructions, see Engine Installation.
    For help troubleshooting Cortex XSOAR engines, including installations, upgrades, connectivity, and permissions, see Troubleshoot Engines and Troubleshoot Integrations Running on Engines.

    Configure IoT Security and Cortex XSOAR

    1. Log in to IoT Security and from there access BlueCat IPAM settings in Cortex XSOAR.
      1. Log in to IoT Security and then click Integrations.
      2. IoT Security uses Cortex XSOAR to integrate with a BlueCat Address Manager, 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 bluecat to locate it among other instances.
    2. Configure the BlueCat IPAM 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 IPAM data from the BlueCat Address Manager specified in this instance.
        Server URL: Enter the IP address or hostname of the BlueCat Address Manager, preceded by http:// or https://, depending on your Address Manager configuration. For example, https://bluecat1.acme.com.
        Username: Type the name of the user account that you previously created in the BlueCat Address Manager UI for the XSOAR engine to use when connecting to the BlueCat API.
        Password: Type the password associated with the user account.
        Run on Single engine: Choose the XSOAR engine that you want to communicate with this BlueCat Address Manager.
      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. Create a job for XSOAR to query the BlueCat Address Manager for IPAM data about its subnets and blocks (referred to as networks and blocks by BlueCat) and send them to IoT Security.
      1. Copy the name of the BlueCat IPAM integration 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 the BlueCat Address Manager for IPAM data. Leave it unselected to run the bulk data import job manually.
        Every: If you select Recurring, enter a number and set the interval value (Minutes, Hours, Days, or Weeks) and select the days or time of day to run the job. (If you don’t select specific days, then the job will run everyday by default.) This determines how often and when XSOAR queries the BlueCat Address Manager. For example: 1 day and 2:00
        Name: Enter a name for the job.
        Playbook: Choose Bulk Import of subnet network info from BlueCat IPAM to PANW IoT Cloud.
        Import IPAM site definitions to IoT Security: Because BlueCat Address Manager does not support the concept of sites, this setting is ignored.
        Integration Instance Name: Paste the instance name you copied a few moments ago.
        Overwrite non-site data when an IP block or subnet is the same in IPAM and IoT Security: Non-site data for an IP block or subnet consists of its name and, for subnets, its gateway IP address. Select Yes if you want BlueCat non-site data to overwrite IoT Security data when there are matching IP blocks and subnets. Select No if you don’t want BlueCat non-site data to overwrite IoT Security data.
        Overwrite site data when a root block is the same in IPAM and IoT Security: Because BlueCat Address Manager does not support the concept of sites, this setting is ignored.
      3. Click Create new job.
    4. 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 configured the job to be run manually, it begins immediately. If you configured it to recur at a defined interval, it will start at the time you set. When it does start, XSOAR queries the BlueCat Address Manager for IPAM data, which it then forwards to the IoT Security cloud.
    5. If you created more integration instances for multiple BlueCat Address Managers, add more instances as necessary.
      Each BlueCat IPAM instance requires a separate job.
    6. When done, return to the IoT Security portal and check the status of the BlueCat IPAM 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.

    © 2024 Palo Alto Networks, Inc. All rights reserved.