Configure Device Security and Cortex XSOAR

1. Log in to Device Security and from there access the SentinelOne instance settings in Cortex XSOAR.

   1. Log in to Device Security and then click Integrations Integration Management Manage Integrations.

      Device Security uses Cortex XSOAR to integrate with SentinelOne Singularity, and the settings you must configure are in the Cortex XSOAR interface.
   2. 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 SentinelOne to locate it among other instances.
2. Configure the settings for a SentinelOne 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.

      Server URL: Enter the URL of your SentinelOne Singularity server.

      API Token: Enter the API token for SentinelOne.

      Optional Last Seen: Enter the time range in days that you want to get device or vulnerability information from SentinelOne. Device Security polls for all vulnerabilities or devices identified or updated in the specified time. By default, the SentinelOne jobs retrieve devices or vulnerabilities last seen in the past one day.

      Optional Severity Levels: Select the severity levels for vulnerabilities that you want to import from SentinelOne to Device Security. By default, Device Security imports only vulnerabilities with a severity level of Critical.

      Optional Learn Device Software Components: Select if you want the import job to include information about software components running on the devices from SentinelOne.

      Cloud-based Cortex XSOAR Run on Single engine: When using a cloud-based Cortex XSOAR instance and an on-premises SentinelOne Singularity server, choose the Cortex XSOAR engine that you want to communicate with the SentinelOne 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 SentinelOne integration instance.
4. Create a job for Cortex XSOAR to receive information from SentinelOne.

   Depending on whether you want to send device details or get vulnerability information, 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:

      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 SentinelOne 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 playbook depending on the type of job you're configuring:
         1. Import SentinelOne Devices to PANW IoT – Import assets and asset information from SentinelOne.
         2. Import SentinelOne Open Vulnerabilities to PANW IoT – Get all known open vulnerabilities from SentinelOne SentinelOne Singularity.
      5. Integration Instance Name: Enter the name of the SentinelOne 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 SentinelOne Singularity 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.