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

    Set up Device Security and Cortex XSOAR for Nozomi CMC Integration

    Table of Contents

    Set up Device Security and Cortex XSOAR for Nozomi CMC Integration

    Configure Cortex XSOAR with an integration instance and jobs to set up Device Security to integrate with your Nozomi Central Management Console (CMC) appliance.
    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 Nozomi CMC, configure Cortex XSOAR with an integration instance and jobs. Because CMC aggregates data from all of the Nozomi Guardian appliances it manages, one integration instance in Cortex XSOAR typically covers every Guardian behind the CMC — you do not need a separate integration instance per Guardian. Configure additional integration instances only if you have more than one CMC appliance to integrate with, or if you have different OpenAPI key tokens for different network ranges.
    Before configuring an integration instance in Cortex XSOAR, Set up Nozomi CMC for Integration and have the following information ready:
    • The Domain URL of your Nozomi CMC appliance
    • The API Key Name and API Key Token that you generated in the CMC console
    Because Nozomi CMC is always deployed on-premises, you must also add a Cortex XSOAR engine to your network when you use a cloud-hosted Cortex XSOAR instance so that Cortex XSOAR can reach the CMC appliance. You don't need a Cortex XSOAR engine if you are using a full-featured, on-premises Cortex XSOAR.

    Cortex XSOAR Engine Installation

    An on-premises Cortex XSOAR engine facilitates communications between the Cortex XSOAR cloud and your on-premises Nozomi CMC appliance. 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'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 Cortex XSOAR engine on your network, make sure it can reach the Nozomi CMC appliance on the HTTPS port that the CMC API listens on (default TCP 443). If your CMC uses a non-standard port, allow that port instead.
    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 Nozomi CMC instance settings in Cortex XSOAR.
      1. Log in to Device Security and select IntegrationsIntegration ManagementManage Integrations.
        Device Security uses Cortex XSOAR to integrate with Nozomi CMC, 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 Integrations Instances, and search for Nozomi CMC to locate it among other instances.
    2. Configure the Nozomi CMC integration instance.
      One integration instance typically covers every Nozomi Guardian that your CMC manages. Configure additional instances if you have more than one Nozomi CMC appliance to integrate with, or if you have different OpenAPI key tokens for different network ranges.
      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:
        1. Name: Use the default name (Nozomi CMC_instance_1) or enter a new one to help you identify the instance.
        2. Domain URL: Enter the URL of your Nozomi CMC appliance.
        3. API Key Name: Enter the API Key Name that you generated in the Nozomi CMC console.
        4. API Key Token: Enter the API Key Token that you generated together with the API Key Name.
        5. Last Seen: Enter the cutoff, in days, for retrieving vulnerabilities. Cortex XSOAR retrieves vulnerabilities seen within this number of days. The default value is 1 day.
        6. Learn New Devices: Enable this setting to automatically ingest new devices from Nozomi into Device Security. This setting is enabled by default.
        7. (Cloud-based Cortex XSOAR with Nozomi CMC on-premises) Run on Single engine: Choose the Cortex XSOAR engine that you want to communicate with your Nozomi CMC appliance.
      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 Nozomi CMC integration instance.
    4. Create a job for Cortex XSOAR to receive information from Nozomi CMC.
      Create one job per playbook. Two jobs are typical — one for the device-details playbook and one for the vulnerabilities playbook.
      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:
        1. Recurring: Select this if you want to periodically run the job. Clear it if you want to run the job on-demand.
        2. (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, the job runs every day by default. This determines how often Cortex XSOAR queries Nozomi CMC for information.
          You can configure Queue Handling to determine what happens if a new job starts while an old job is still running.
        3. Name: Enter a name for the job.
        4. Playbook: Select one of the following Nozomi CMC playbooks:
          • Import Device Details From Nozomi CMC To Device Security — imports device inventory records and their attributes.
          • Import Vulnerabilities From Nozomi CMC To Device Security — imports vulnerability findings mapped to the corresponding devices.
        5. Integration Instance Name: Enter the name of the Nozomi CMC integration instance that you want the job 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 Nozomi CMC 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.