>
    Strata Copilot
    Set up Device Security and Cortex XSOAR for Mist AI Integration
    Focus
    Download PDF
    Focus
    1. Home
    2. Device Security
    3. Device Security Integration Guide
    4. Network Management
    5. Integrate Device Security with HPE Juniper Networking Mist AI
    6. Set up Device Security and Cortex XSOAR for Mist AI Integration
    Download PDF
    Device Security

    Set up Device Security and Cortex XSOAR for Mist AI Integration

    Table of Contents

    Set up Device Security and Cortex XSOAR for Mist AI Integration

    Configure Cortex XSOAR with integration instances and jobs to import information from HPE Juniper Networking Mist AI to Device Security.
    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 Cortex XSOAR Engine (on-premises integration)
    • A full-featured Cortex XSOAR server
    To import information from HPE Juniper Networking Mist AI to Device Security, configure Cortex XSOAR with integration instances and jobs. If you want to integrate with multiple Mist AI deployments, you need to create separate integration instances and jobs.
    Before configuring an integration instance in Cortex XSOAR, Set up Mist AI for Integration and have the following information ready:
    • Your Juniper Mist URL
    • Your Juniper Mist API token
    To set up Device Security to integrate through a cloud-hosted Cortex XSOAR instance with an on-premises Mist AI deployment, you must also add a Cortex XSOAR engine to your network. If you are integrating with a cloud instance of Mist AI, or if you have an on-premises Cortex XSOAR server, you don't need to install a Cortex XSOAR engine.

    Cortex XSOAR Engine Installation

    An on-premises Cortex XSOAR engine facilitates communications between the Cortex XSOAR cloud and an on-premises Juniper Mist. To install a Cortex XSOAR engine, follow the instructions to Install a Cortex XSOAR Engine. For more information about general operating systems and hardware requirements, see the Cortex XSOAR Administrator 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.
    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 from there access the Mist AI instance settings in Cortex XSOAR.
      1. Log in to Device Security and then click IntegrationsIntegration ManagementManage Integrations.
        Device Security uses Cortex XSOAR to integrate with Mist AI, and the settings you must configure are in the Cortex XSOAR interface.
      2. Launch Cortex XSOAR.
        The Cortex XSOAR interface opens in a new browser tab or window.
      3. Click Settings in the left navigation menu to go to IntegrationsInstances, and search for Juniper Mist to locate it among other instances.
    2. Configure the settings for a Mist AI integration instance.
      1. Click the active integration instance settings icon, or click Add instance, to open the settings panel.
      2. Enter the following settings and leave the others at their default values:
        • Name: Use the default name or enter a new one to help you identify the instance.
        • Server URL: Enter the URL of your Mist AI solution.
        • API Token: Enter the API token key for Mist AI.
        • Device Details for the Cortex XSOAR job: Select the device details that you want the Cortex XSOAR integration job to learn. You must select at least one of the "Clients" options or else the job will not import any information.
          • Optional Sites List: Enter a comma-separated list of Juniper Mist site IDs for the sites that you want to learn information from. If you don't specify any site IDs, then the integration job will import information at the organization level.
          • Optional Wireless Clients: Learn about Juniper Mist wireless clients.
          • Optional Wired Clients: Learn about Juniper Mist wired clients.
          • Optional NAC Clients: Learn about Juniper Mist NAC clients.
          • Required for Sites List Use Site ID: Select this option if you specify a sites ID list of the sites you want the integration to learn from.
          • Optional Backoff Rate Limit: Select this if you expect to import a lot of information from Mist AI. If you don't select this, the integration job may fail due to rate limiting of API requests.
      3. When finished, click Test or Test resultsRun test to test the integration instance.
        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 Mist AI integration instance.
    4. Create a job for Cortex XSOAR to send and receive information from Mist AI.
      You can create multiple jobs if you have multiple integration instances.
      1. Click Jobs in the sidebar, and then click New Job to create a new Cortex XSOAR job.
      2. Configure the following settings in the New Job panel:
        • Recurring: Select this if you want to periodically run the job. Clear it if you want to run the job on-demand.
        • Optional Every: If you selected 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 every day by default. This determines how often Cortex XSOAR queries Mist AI for information.
          You can configure Queue Handling to determine what happens if a new job starts while an old job is still running.
        • Name: Enter a name for the job.
        • Playbook: Select the Import Juniper Mist Devices to PANW IoT - PANW IoT 3rd Party Integration playbook to import devices and device details from Mist AI to Device Security.
        • Integration Instance Name: Enter the name of the integration instance you created.
    5. Enable the job and run it.
      Check the Job Status for the job you created. If it's Disabled, select its checkbox and then click Enable.
      You can immediately run the job by selecting it and clicking Run now. Otherwise, if you scheduled a recurring job, then the enabled job will run as scheduled.
    6. Return to Device Security and check the status of the Mist AI 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.

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