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

    Set up Device Security and Cortex XSOAR for Cisco Spaces Integration

    Table of Contents

    Set up Device Security and Cortex XSOAR for Cisco Spaces Integration

    Set up Device Security and Cortex XSOAR to integrate with Cisco Spaces.
    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
    • Precision AI bundle subscription
    • 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 with Cisco Spaces, configure Cortex XSOAR with integration instances and jobs. If you want to integrate with multiple Cisco Spaces solutions, you need to create separate integration instances and jobs.
    Before configuring an integration instance in Cortex XSOAR, Set up Cisco Spaces for Integration and have the following information ready:
    • Your Cisco Spaces server base URL
    • Your Cisco Spaces API key bearer token
    To set up Device Security to integrate through a cloud-hosted Cortex XSOAR instance with an on-premises Cisco Spaces deployment, you must also add a Cortex XSOAR engine to your network. If you are integrating with a cloud instance of Cisco Spaces, 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 Cisco Spaces server. To install a Cortex XSOAR engine, follow the Cortex 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 then access the Cisco Spaces instance settings in Cortex XSOAR.
      1. Log in to Device Security and select IntegrationsIntegration ManagementManage Integrations.
        Device Security uses Cortex XSOAR to integrate with Cisco Spaces, and the settings you must configure are in the Cortex XSOAR interface.
      2. Click 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 Cisco Spaces to locate it among other instances.
    2. Configure the settings for a Cisco Spaces 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.
        • bearer_token: Enter your Cisco Spaces API key bearer token.
        • URL: Enter the base URL for your Cisco Spaces solution. By default, the integration instance uses the base URL for the US region.
      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 Cisco Spaces integration instance.
    4. Create a job for Cortex XSOAR to receive information from Cisco Spaces.
      Depending on whether you want to import device details or get floor plans, select the appropriate playbook when configuring the job. If you want to run multiple playbooks, you must create separate jobs, one for each playbook. You can also 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 Cisco Spaces 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 playbook depending on the type of job you're configuring. For more information about what types of devices Cisco Spaces categorizes as clients, tags, or interferers, see Introduction to Cisco Spaces: Detect and Locate.
          • Import Cisco Spaces Clients to PANW IoT — Import clients and client information from Cisco Spaces.
          • Import Cisco Spaces Floor Plans to PANW IoT — Import floor plans, maps, and floor plan hierarchy from Cisco Spaces.
          • Import Cisco Spaces INTERFERER Devices to PANW IoT — Import interferers and interferer information from Cisco Spaces.
          • Import Cisco Spaces TAG Devices to PANW IoT — Import tags and tag information from Cisco Spaces.
        • Integration Instance Name: Enter the name of the Cisco Spaces integration instance.
      3. Click Create new job.
      4. Repeat to create additional jobs for each playbook you want to use.
    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 Cisco Spaces integration instance.
      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.