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

    Set up Device Security and Cortex XSOAR for Philips Focal Point Integration

    Table of Contents

    Set up Device Security and Cortex XSOAR for Philips Focal Point Integration

    Configure Cortex XSOAR with integration instances and jobs to set up Device Security to integrate with Philips Focal Point.
    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 with Philips Focal Point, configure Cortex XSOAR with integration instances and jobs. If you want to integrate with multiple Focal Point solutions, you need to create separate integration instances and jobs.
    Before configuring an integration instance in Cortex XSOAR, Set up Philips Focal Point for Integration and have the following information ready:
    • Your Philips Focal Point entry server IP for SNMP crawling
    • Your Philips Focal Point SNMP authentication credentials
    To set up Device Security to integrate through a cloud-hosted Cortex XSOAR instance with an on-premises Philips Focal Point deployment, you must also add a Cortex XSOAR engine to your network. 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 an on-premises Philips Focal Point 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'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 FocalPoint server on UDP port 161, which FocalPoint uses for SNMP communication.
    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 Philips Focal Point instance settings in Cortex XSOAR.
      1. Log in to Device Security and select IntegrationsIntegration ManagementManage Integrations.
        Device Security uses Cortex XSOAR to integrate with Philips Focal Point, 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 Philips Focal Point to locate it among other instances.
    2. Configure the Philips FocalPoint integration instance.
      You must configure a separate integration instance for each Focal Point Server.
      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 or enter a new one to help you identify the instance.
        2. Entry server IP: Enter the IP address of the entry server that you want to start the SNMP crawl from.
        3. SNMP Version: Select 2c, and then configure the Community String.
        4. (SNMPv2c) Community String: Enter the SNMP community string configured on the switches to permit read-only access.
        5. SNMP Timeout: Enter the time, in seconds, that the job should wait for a response from the Focal Point server to an SNMP query. The default value is 1 second. You can configure a time between 1 and 120 seconds.
        6. SNMP Retries: Enter the number of times the job should try an SNMP query. If the job has reached the maximum number of retries, then it skips that SNMP query. The number of retries does not include the initial query. The default value is 0 retries. You can configure a max of 5 retries.
        7. (Cloud-based Cortex XSOAR) Run on Single engine: When using a cloud-based Cortex XSOAR instance, choose the Cortex XSOAR engine that you want to communicate with the Philips Focal Point server.
      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 Philips Focal Point integration instance.
    4. Create a job for Cortex XSOAR to receive information from Philips Focal Point.
      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:
        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, then the job will run every day by default. This determines how often Cortex XSOAR queries Philips Focal Point 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 the Import Philips Focal Point Devices to PANW IoT playbook to import assets and asset information from Philips Focal Point.
        5. Integration Instance Name: Enter the name of the Philips Focal Point integration instance.
    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 FocalPoint 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.