Set up IoT Security and Cortex XSOAR for Microsoft Entra ID Integration

Set up IoT Security and Cortex XSOAR for Microsoft Entra ID Integration

1. Log in to IoT Security, and from there access the Microsoft Entra ID integration settings in Cortex XSOAR.

   1. Log in to IoT Security and then click Integrations.
   2. Launch Cortex XSOAR from the IoT Security portal.

      IoT Security uses Cortex XSOAR to integrate with Microsoft Entra ID. The settings you must configure are in the Cortex XSOAR interface. To access these settings from the Integrations page, Launch Cortex XSOAR. The Cortex XSOAR interface opens in a new browser tab or window.
   3. Find the Microsoft Entra ID integration.

      Click Settings in the left navigation menu. Search for Microsoft Entra ID to locate it among other integrations.

      
2. Configure the Microsoft Entra ID integration instance.

   1. Click Add instance to open the settings panel.
   2. In the settings panel, configure the following settings:

      • Name: Use the default name of the instance or enter a new one.
      • Default URL: The default URL is graph.microsoft.com
      • Tenant ID: Enter the Tenant ID from your Microsoft application.
      • Client ID: Enter the Client ID from your Microsoft application.
      • Client Secret: Enter the Client Secret ID from your Microsoft application.
      • Run on Single engine: Choose No engine.

      

   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. Create a job for Cortex XSOAR to query Microsoft Entra ID for devices and device attributes and import them to IoT Security.

   1. Create a new Cortex XSOAR job.

      Copy the name of the instance you created, click Jobs near the bottom of the left navigation menu, and then click New Job at the top of the page.
   2. Configure the new Cortex XSOAR job.

      In the New Job panel that appears, configure the following and leave the other settings at their default values:

      • Recurring: Select this if you want to periodically import device information from Microsoft Entra ID. Clear it if you want to import device details on demand.
      • Every: If you select 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 Microsoft Entra ID for information about device details.
      • Name: Enter a name for the job.
      • Playbook: Choose Import MS Entra ID devices to PANW IoT cloud.
      • Integration Instance Name: Paste the instance name of your Microsoft Defender XDR integration instance.
   3. Click Create new job and verify that the job appears in the Jobs list.
4. Enable the job and run it.

   1. Check the job status for the job you created.

      If the job is Disabled, select the appropriate check boxes and then click Enable.
   2. Run the job.

      After you enable the job, keep the check box selected and click Run now. The Run Status should change from Idle to Running.

      If you selected Recurring, Cortex XSOAR queries Microsoft Entra ID for information at the defined intervals and forwards imported information to IoT Security.

      If you cleared Recurring, Cortex XSOAR immediately queries Microsoft Entra ID and forwards imported information to IoT Security.
5. Return to the IoT Security portal and check the status of the Microsoft Entra ID integration.

   An integration instance can be in one of the following four states, which IoT Security displays in the Status column on the Integrations page:

   • 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.
   • Active — the integration was configured and enabled and is functioning properly.

   When you see that the status of an integration instance is Active, its setup is complete.