>
    Strata Copilot
    Set up Device Security and XSOAR for Cisco DNA Center Integration
    Focus
    Download PDF
    Focus
    1. Home
    2. Device Security
    3. Device Security Integration Guide
    4. Network Management
    5. Integrate Device Security with Cisco DNA Center
    6. Set up Device Security and XSOAR for Cisco DNA Center Integration
    Download PDF
    Device Security

    Set up Device Security and XSOAR for Cisco DNA Center Integration

    Table of Contents

    Set up Device Security and XSOAR for Cisco DNA Center Integration

    Set up Device Security and Cortex XSOAR to integrate with Cisco DNA Center.
    Where Can I Use This?What Do I Need?
    • Device Security (Managed by Strata Cloud Manager)
    • (Legacy) IoT Security (Standalone portal)
    One of the following subscriptions:
    • Device Security subscription for an advanced Device Security product (Enterprise Plus, Industrial OT, or Medical)
    • Device Security X subscription
    One of the following Cortex XSOAR setups:
    • A free, cohosted, limited-featured Cortex XSOAR instance
      AND
      A free Cortex XSOAR Engine (on-premises integration)
    • A full-featured Cortex XSOAR server
    To set up Device 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 Cortex XSOAR engine will use when forming a secure connection with DNA Center.
    When integrating Device Security with Cisco DNA Center, you can choose from two playbooks for the Cortex XSOAR job:
    • extract-dnac-clients - This playbook gets a list of MAC addresses of active devices from Device Security and then queries Cisco DNA Center for details about the devices on that list. Using this playbook, Device Security does not learn any new devices.
    • Import Cisco DNAC Network Devices and Clients to PANW IoT - This playbook requests all devices and device information from Cisco DNA Center. Device Security updates device attributes when it finds matches in the existing asset inventory. For devices with no existing matches, Device Security adds those devices to the asset inventory.

    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 Cortex 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 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 Cortex XSOAR engine on your network, make sure it can form HTTPS connections to your Cisco DNA Center system API on TCP port 443. The Cortex XSOAR engine uses TCP 443 when authenticating with Cisco DNA Center and requesting and receiving device data.
    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 Device Security 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 Device Security, 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 Device Security and Cortex XSOAR

    1. Log in to Device Security and then access Cisco DNA Center settings in Cortex XSOAR.
      1. Log in to Device Security and then click Integrations.
      2. Device 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, and 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're 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 Cortex 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. Enable the Cisco DNA Center integration instance.
    4. Create a job for Cortex XSOAR to query Cisco DNA Center for device information.
      Copy the name of the instance you 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 Device Security to Cisco DNA Center and receives device details in response.
      Generally, this job takes about 15 minutes per 1,000 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 the playbook that you want to use.
      • extract-dnac-clients - When running this playbook, Cortex XSOAR only requests details from Cisco DNA Center if a device has a MAC address. If your network has static IP devices without MAC addresses, they won't be included. Using this playbook, Device Security does not learn any new devices.
      • Import Cisco DNAC Network Devices and Clients to PANW IoT - When running this playbook, Cortex XSOAR queries Cisco DNA Center for all devices. Device Security updates existing devices and adds new devices learned through the integration.
      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 Device 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 Device 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 web interface opens in a new browser window, you can return to the previous window with the Device Security portal and navigate to AdministrationSites and FirewallsSites 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 Device Security portal.
      At the defined interval, XSOAR begins the job by first requesting an active device list from Device Security and then using that list to query Cisco DNA Center for client details, which it forwards to the Device 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 Cortex XSOAR engines retrieving device information from the same Cisco DNA Center server. However, a single engine can’t retrieve information from multiple servers.
      Run each job initially to add the related instance to the Integrations page in the Device Security portal.
    7. When done, return to Device Security and check the status of the Cisco DNA Center 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.

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