Set up IoT Security and Cortex XSOAR for Microsoft Defender XDR Integration

1. Log in to IoT Security, and from there access the Microsoft Defender XDR 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 Defender XDR. 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 Defender XDR integration.

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

2. Configure the Microsoft Defender XDR 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.
        Remember the instance name because you're going to use it again when creating the jobs that Cortex XSOAR runs to gather device data and vulnerability information from Microsoft Defender XDR.
      • Domain URL: Select the Microsoft Defender XDR API Gateway URL based on the geographical cluster where your account is registered. The possible domain URL options are:
        • https://api-us.securitycenter.microsoft.com
        • https://api-eu.securitycenter.microsoft.com
        • https://api-uk.securitycenter.microsoft.com
        • https://api-au.securitycenter.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 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 Defender XDR 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 Defender XDR. 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 Defender XDR for information about device details.
      • Name: Enter a name for the job.
      • Playbook: Choose Import MS Defender 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. Create a job for Cortex XSOAR to query Microsoft Defender XDR for vulnerabilities and vulnerability details and import them to IoT Security.

   1. Create a new Cortex XSOAR job.

      Stay on the Jobs page, and 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 vulnerabilities and vulnerability information from Microsoft Defender XDR. Clear it if you want to import vulnerability information 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 Defender XDR for information about vulnerabilities.
      • Name: Enter a name for the job.
      • Playbook: Choose Import MS Defender Vulnerabilities to PANW IoT cloud.
      • Integration Instance Name: Paste the same instance name you used for the device details job.
      • Optional Playbook Duration in days: Choose the number of days that you want to poll for discovered vulnerabilities. If the field is blank, then Cortex XSOAR requests vulnerabilities discovered in the last 30 days by default.
      • Optional Import vulnerabilities by CVE levels: Choose the CVE severity levels for vulnerabilities that you want to import. You can select multiple levels at once. If no level is selected, then Cortex XSOAR imports only CVEs with a severity level of Critical by default.
   3. Click Create new job and verify that the job appears in the Jobs list.
5. Enable the jobs and run them.

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

      If the jobs are Disabled, select the appropriate check boxes and then click Enable.
   2. Run the device details import job.

      After you enable the jobs, select only the check box for the device details import job and click Run now. The Run Status should change from Idle to Running.
   3. Run the vulnerabilities import job.

      Once the device details import job's Run Status changes to Completed, deselect that job. Select the check box for the vulnerabilities import job and click Run now. The Run Status should change from Idle to Running.

   For either job, if you selected Recurring, Cortex XSOAR queries Microsoft Defender XDR for information at the defined intervals and forwards imported information to IoT Security.

   If you cleared Recurring, Cortex XSOAR immediately queries Microsoft Defender XDR and forwards imported information to IoT Security.
6. Optional Create additional integration instances, and configure and run jobs for each integration instance as needed.
7. Return to the IoT Security portal and check the status of the Aruba AirWave 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 means that either the integration was configured but intentionally disabled or it was never configured and a job that references it is enabled and running.
   • Error means that the integration was configured and enabled but is not functioning properly, possibly due to a configuration error or network condition.
   • Inactive means that the integration was configured and enabled but no job has run for at least the past 60 minutes.
   • Active means that 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.