Set up IoT Security and XSOAR for DNA Center Integration

Set up IoT Security and Cortex XSOAR to integrate with Cisco DNA Center.
To set up IoT Security to integrate through Cortex XSOAR with Cisco DNA Center, you must add a Cortex XSOAR engine to your network.
You must also configure the Cisco DNA Center integration instance in XSOAR. To do this, you need the URL of your Cisco DNA Center system and the username and password of the read-only user account that the XSOAR engine will use when forming a secure connection with DNA Center.

Cortex XSOAR Engine Installation

The Cortex XSOAR engine initiates connections to Cisco DNA Center and to the Cortex cloud and provides the means through which they communicate with each other. 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 Administrator’s Guide.
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 Cisco DNA Center system API on TCP port 443. The XSOAR engine uses TCP 443 when authenticating with Cisco DNA Center and requesting and receiving device data.
The on-premises firewall must allow the 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 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 XSOAR interface.
To create an XSOAR engine, access the Cortex XSOAR interface (from the IoT Security portal, click
Integrations
and then click
Launch Cortex XSOAR
). In the XSOAR UI, click
Settings
Engines
+ Create New Engine
. Choose
Shell
as the type.
For installation instructions, see Install Cortex XSOAR Engines.
For help troubleshooting Cortex XSOAR engines, including installations, upgrades, connectivity, and permissions, see Troubleshoot Cortex XSOAR Engines and Troubleshoot Integrations Running on Engines.

Configure IoT Security and Cortex XSOAR

  1. Log in to IoT Security and then access Cisco DNA Center settings in Cortex XSOAR.
    1. Log in to IoT Security and then click
      Integrations
      .
    2. IoT Security uses Cortex XSOAR to integrate with Cisco DNA Center, and the settings you must configure to integrate with DNA Center 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
      cisco dna center
      to locate it among other instances.
  2. Configure the Cisco DNA Center 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 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.
      Cisco DNA Center Server URL
      : Enter the Cisco DNA Center Server URL.
      Cisco DNA Center username
      : Enter the name of the user account you previously created in Cisco DNA Center with read-only permission to access its API.
      Password
      : Enter the password associated with the user account.
      Run on Single engine
      : Choose the XSOAR engine that you want to communicate with the Cisco DNA Center system.
    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. To enable Cisco DNA Center Integration Instance, click
    Enable
    .
  4. Create a job for XSOAR to get a list of MAC addresses of active devices from IoT Security and then query Cisco DNA Center for details about the devices in the list.
    IoT Security and XSOAR only request details from Cisco DNA Center if a device has a MAC address. If your network has static IP devices without MAC addresses, they will not be included.
    Copy the name of the instance you just created, navigate to Jobs, and then click New Job at the top of the page.
    In the New Job panel that appears, enter the following and leave the other settings at their default values:
    Recurring
    : Select this because you want to periodically poll the DNA Center for device details.
    Every
    : Enter a number and set the interval value (Minutes, Hours, Days, or Weeks) and select the days on which to run the job. This determines how often XSOAR sends a list of MAC addresses of currently active devices from IoT Security to Cisco DNA Center and receives device details in response.
    As a general rule of thumb, this job takes about 15 minutes per 1000 devices to complete. Other factors that might affect the time required to complete a job are the Cisco DNA Center API processing speed and settings.
    Name
    : Enter a name for the job.
    Playbook
    : Choose
    extract-dnac-clients
    .
    Integration Instance Name
    : Paste the instance name you copied a few moments ago.
    Playbook Poll Interval
    : Enter a number (the value, though unspecified, is minutes) defining the period of time during which IoT Security must see device activity to include it in the list of currently active devices it provides to XSOAR. It’s common to use the same interval as the one above for running the recurring job.
    Site Names
    : By default, the XSOAR retrieves device data from all sites that IoT Security manages. If there are multiple sites and you want to get device data from a subset of them or the DNA Center is managing a subset of them, specify them by name here. Separate multiple names with commas. Use quotation marks around names with spaces. Because the Cortex XSOAR UI opens in a new browser window, you can return to the previous window with the IoT Security portal and navigate to
    Administration
    Sites and Firewalls
    Sites
    to view a list of site names.
    Click
    Create new job
    .
    The newly created job appears at the bottom of the Jobs list.
  5. Enable the job and run it.
    Check the Job Status for the job you created. If it’s Disabled,
    Enable
    it.
    After you enable it, keep the check box selected and click
    Run now
    . The Run Status changes from Idle to Running. In addition, running a job in XSOAR triggers the referenced integration instance to appear on the Integrations page in the IoT Security portal.
    At the defined interval, XSOAR begins the job by first requesting an active device list from IoT Security and then using that list to query Cisco DNA Center for client details, which it forwards to the IoT Security cloud.
  6. If you have multiple DNA Center instances, add more jobs as necessary.
    To add another, click
    Add instance
    , configure the settings as previously explained, and then click
    Done
    .
    You can configure multiple instances with different XSOAR engines retrieving device information from the same Cisco DNA Center server. However, a single engine cannot retrieve information from multiple servers.
    Run each job initially to add the related instance to the Integrations page in the IoT Security portal.
  7. When done, return to the IoT Security portal and check the status of the Cisco DNA Center 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.

Recommended For You