Third-party Integrations Using a Full-featured XSOAR Server
Table of Contents
Expand all | Collapse all
-
- Integrate IoT Security with AIMS
- Set up AIMS for Integration
- Set up IoT Security and XSOAR for AIMS Integration
- Send Work Orders to AIMS
- Integrate IoT Security with Microsoft SCCM
- Set up Microsoft SCCM for Integration
- Set up IoT Security and XSOAR for SCCM Integration
- Integrate IoT Security with Nuvolo
- Set up Nuvolo for Integration
- Set up IoT Security and XSOAR for Nuvolo Integration
- Send Security Alerts to Nuvolo
- Send Vulnerabilities to Nuvolo
- Integrate IoT Security with ServiceNow
- Set up ServiceNow for Integration
- Set up IoT Security and XSOAR for ServiceNow Integration
- Send Security Alerts to ServiceNow
- Send Vulnerabilities to ServiceNow
-
- Integrate IoT Security with Cortex XDR
- Set up Cortex XDR for Integration
- Set up IoT Security and XSOAR for XDR Integration
- Integrate IoT Security with CrowdStrike
- Set up CrowdStrike for Integration
- Set up IoT Security and XSOAR for CrowdStrike Integration
- Integrate IoT Security with Tanium
- Set up Tanium for Integration
- Set up IoT Security and XSOAR for Tanium Integration
-
- Integrate IoT Security with Aruba Central
- Set up Aruba Central for Integration
- Set up IoT Security and XSOAR for Aruba Central Integration
- Integrate IoT Security with Cisco DNA Center
- Set up Cisco DNA Center to Connect with XSOAR Engines
- Set up IoT Security and XSOAR for DNA Center Integration
- Integrate IoT Security with Cisco Meraki Cloud
- Set up Cisco Meraki Cloud for Integration
- Set up IoT Security and XSOAR for Cisco Meraki Cloud
- Integrate IoT Security with Cisco Prime
- Set up Cisco Prime to Accept Connections from IoT Security
- Set up IoT Security and XSOAR for Cisco Prime Integration
- Integrate IoT Security with Network Switches for SNMP Discovery
- Set up IoT Security and Cortex XSOAR for SNMP Discovery
- Integrate IoT Security with Switches for Network Discovery
- Set up IoT Security and Cortex XSOAR for Network Discovery
-
- Integrate IoT Security with Aruba WLAN Controllers
- Set up Aruba WLAN Controllers for Integration
- Set up IoT Security and XSOAR for Aruba WLAN Controllers
- Integrate IoT Security with Cisco WLAN Controllers
- Set up Cisco WLAN Controllers for Integration
- Set up IoT Security and XSOAR for Cisco WLAN Controllers
-
- Integrate IoT Security with Aruba ClearPass
- Set up Aruba ClearPass for Integration
- Set up IoT Security and XSOAR for ClearPass Integration
- Put a Device in Quarantine Using Aruba ClearPass
- Release a Device from Quarantine Using Aruba ClearPass
- Integrate IoT Security with Cisco ISE
- Set up Cisco ISE to Identify IoT Devices
- Set up Cisco ISE to Identify and Quarantine IoT Devices
- Configure ISE Servers as an HA Pair
- Set up IoT Security and XSOAR for Cisco ISE Integration
- Put a Device in Quarantine Using Cisco ISE
- Release a Device from Quarantine Using Cisco ISE
- Apply Access Control Lists through Cisco ISE
- Integrate IoT Security with Cisco ISE pxGrid
- Set up Integration with Cisco ISE pxGrid
- Put a Device in Quarantine Using Cisco ISE pxGrid
- Release a Device from Quarantine Using Cisco ISE pxGrid
- Integrate IoT Security with Forescout
- Set up Forescout for Integration
- Set up IoT Security and XSOAR for Forescout Integration
- Put a Device in Quarantine Using Forescout
- Release a Device from Quarantine Using Forescout
-
- Integrate IoT Security with Qualys
- Set up QualysGuard Express for Integration
- Set up IoT Security and XSOAR for Qualys Integration
- Perform a Vulnerability Scan Using Qualys
- Get Vulnerability Scan Reports from Qualys
- Integrate IoT Security with Rapid7
- Set up Rapid7 InsightVM for Integration
- Set up IoT Security and XSOAR for Rapid7 Integration
- Perform a Vulnerability Scan Using Rapid7
- Get Vulnerability Scan Reports from Rapid7
- Integrate IoT Security with Tenable
- Set up Tenable for Integration
- Set up IoT Security and XSOAR for Tenable Integration
- Perform a Vulnerability Scan Using Tenable
- Get Vulnerability Scan Reports from Tenable
Third-party Integrations Using a Full-featured XSOAR Server
Set up a full-featured Cortex XSOAR server for IoT Security integration with third-party
solutions.
IoT Security can integrate with third-party systems through a full on-premises or cloud-hosted
Cortex XSOAR server running Cortex XSOAR version 6.0 –
6.10. This option supports the same IoT Security integrations as the cohosted
version but doesn’t require the purchase of an IoT Security Third-party Integrations
Add-on license. In addition, the full-featured Cortex XSOAR product allows you to
create and modify third-party integration playbooks, unlike the cohosted,
purpose-built XSOAR service, which has preconfigured playbooks that can't be
modified.


The following instructions for setting up IoT Security and a full-featured XSOAR server assume
that you’ve already installed an XSOAR server on your network
or in the cloud and that you are now preparing it to provide third-party integration
opportunities for IoT Security. IoT Security supports third-party integrations
through XSOAR servers running Cortex XSOAR version 6.0 – 6.10.
For FedRAMP compliance, the on-premises XSOAR server must be running a vendor-approved FIPS version that complies with the
FIPS 140-2 standard.
- Choose a Cortex XSOAR server for IoT Security to use for third-party integrations.
- Log in to the IoT Security portal, selectIntegrations.If you have not bought and activated an IoT Security Third-Party Integrations Add-on license, two options appear on the Integrations page.
- SelectIntegrate through a full-featured Cortex XSOAR serverand thenSave.IoT Security takes a few minutes to prepare to use a Cortex XSOAR server for third-party integrations. When done, the Integrations page changes to show XSOAR installation settings and a list of the steps for setting up third-party integrations through a full-featured XSOAR server.After you save your selection, a button appears in the upper right of the page:Switch integration methods. If you have both a full-featured Cortex XSOAR server and an IoT Security Third-party Integrations Add-on license, you can switch between the XSOAR server and the cohosted XSOAR instance. However, you can only use one method at a time.
- Download the IoT Security Content Pack.On the Integrations page, download the IoT Security content pack as a .zip file.Do not download and attempt to use the IoT Security content pack from the Cortex XSOAR marketplace. It isn't current and doesn't support all the third-party integrations that the content pack available from the IoT Security portal does. Only download and use the content pack from the IoT Security portal.
- Create an API access key and then download the key and key ID.If you have the text file for a currently active API access key, you can use that instead of creating a new API access key.
- On the Integrations page in IoT Security, clickCreateunder API Access Key.
- In the Create Access Key dialog box, clickCreateagain.
- In the Access Key Created dialog box,Downloadthe access key and key ID as a text file.
- Copy the IoT Security tenant URL.
- Configure the Cortex XSOAR server.Log in to the Cortex XSOAR server, upload the content pack, and use your IoT Security tenant URL, API access key, and key ID to configure the "Palo Alto Networks IoT 3rd Party" integration instance.
- Log in to the XSOAR server using credentials for a user account with administrator privileges, which let you upload the IoT Security content pack.
- Because the IoT Security content pack is not provided by Cortex XSOAR, set content pack verification tofalse. Select, enterSettingsAboutTroubleshootingfalsein thecontent.pack.verifyfield in the Server Configuration section, and thenSave.
- On the XSOAR server, navigate to theMarketplace, click the three vertical dots icon in the upper right, and thenUpload Content Packs.
- Select the previously downloaded IoT Security content pack for XSOAR to upload and install.
- SelectSettings, search forpalo alto networks iot 3rd party, and then clickAdd instanceto open the settings panel.
- Enter the following and leave other settings at their default values:Name: Use the default name (Palo Alto Networks IoT 3rd Party_instance_1) or enter a new one.IoT Security Tenant URL: Copy this from the Integrations page in IoT Security and paste it here.Access Key: Copy this from the API access key file you downloaded and paste it here.Key ID: Copy this from the API access key file you downloaded and paste it here.Long running instance: (select; this maintains a session between the XSOAR server and IoT Security, using a regular heartbeat mechanism to monitor connectivity)Single engine: ChooseNo engine.
- Test the integration instance settings.When finished, clickTest. If the test is successful, a Success message appears and Cortex XSOAR and IoT Security have established a link. If not, check that the settings were entered correctly and then test the configuration again.
- ClickSave & exitto save your changes and close the settings panel.
- Configure IoT Security third-party integrations.After you’ve installed a content pack for IoT 3rd party integrations, you can begin configuring integrations with third-party systems. For IoT Security and Cortex XSOAR to integrate with a third-party system, you must configure XSOAR with an integration instance specifying connection settings and a job running a playbook over the connection.The following is a list of the jobs and their configuration elements for the third-party integrations that IoT Security supports. For detailed configuration instructions, see the section for specific integrations in this guide.Although the integration instructions later in this guide assume that you’re using a cohosted XSOAR module, the configuration instructions for the integration instances and jobs are similar for both cohosted deployments and full-featured Cortex XSOAR server deployments.Asset DiscoveryIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - Asset Attribute PollingBulk Import Asset Attributes Using Asset Attribute Polling - PANW IoT 3rd Party IntegrationNoRequired:"Integration Instance Name" and "Device Polling IP address/Subnet"Imports device attributes using asset attribute polling.Asset ManagementIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - AIMSExport AIMS maps and devices to PANW IoTYesNo arguments required. Only a single instance is supported.Exports AIMS facilities, vendors, employees, work order priority list mappings, and device data to IoT Security.PANW IoT 3rd Party Integration - AIMSExport AIMS assignee and priority lists to PANW IoTYesNo arguments required. Only a single instance is supported.Exports the assignee list and work order priority list from AIMS to IoT Security.PANW IoT 3rd Party Integration - Microsoft SCCMImport Microsoft SCCM devices to PANW IoT cloudYesRequired: "Integration Instance Name".Fetches available endpoint data from a Microsoft SCCM SQL server and sends it to IoT Security.PANW IoT 3rd Party Integration - NuvoloBulk Export Devices to Nuvolo - PANW IoT 3rd Party IntegrationNoNo arguments required. Only a single instance is supported.Retrieves all devices from IoT Security and sends it to a third-party integration instance.PANW IoT 3rd Party Integration - NuvoloBulk Import Devices from Nuvolo to PANW IoT Cloud - PANW IoT 3rd Party IntegrationNoNo arguments required. Only a single instance is supported.Retrieves all devices from the Nuvolo instance and sends them to IoT Security.Although this job is prebuilt on a cohosted XSOAR instance, it must be manually created on a full-featured XSOAR server.PANW IoT 3rd Party Integration - NuvoloIncremental Export Devices to Nuvolo - PANW IoT 3rd Party IntegrationYesNo arguments required. Only a single instance is supported. The fixed poll interval is 15 minutes.Retrieves devices from IoT Security and sends them to the third-party integration instance.Although this job is prebuilt on a cohosted XSOAR instance, it must be manually created on a full-featured XSOAR server.PANW IoT 3rd Party Integration - ServiceNow v2Incremental Export Devices to ServiceNow - PANW IoT 3rd Party IntegrationYesNo arguments required. Only a single instance is supported. The fixed poll interval is 15 minutes.Retrieves devices discovered by IoT Security and sends them to a third-party integration instance.PANW IoT 3rd Party Integration - ServiceNow v2Bulk Export Devices to ServiceNow - PANW IoT 3rd Party IntegrationNoNo arguments required. Only a single instance is supported.Retrieves all devices from IoT Security and sends them to a third-party integration instance.Endpoint ProtectionIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - Cortex XDR - IRIncremental Export of Cortex XDR - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Optional: "Site Names", and "Playbook Poll Interval".Retrieves active devices found by IoT Security, queries Cortex XDR to get associated device attributes, and reports the data to IoT Security. Filters for active devices: Site names and playbook poll interval.PANW IoT 3rd Party Integration - CrowdStrike FalconIncremental Import of CrowdStrike Falcon - PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Optional: "Site Names", and "Playbook Poll Interval".Retrieves active devices found by IoT Security, queries CrowdStrike Falcon to get associated device attributes and reports the data to IoT Security. Filters for active devices: Site names and playbook poll interval.PANW IoT 3rd Party Integration - TaniumImport Tanium Vulnerabilities to PANW IoT cloudYesRequired: "Integration Instance Name"Optional:"Import vulnerabilities by CVE severity levels"Imports vulnerabilities from Tanium to the IoT Security.Network ManagementIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - Aruba CentralImport Aruba Central devices to PANW IoT cloudYesRequired: "Integration Instance Name"Optional: “Import Aruba Central wired client details to IoT Security”Retrieves client details from Aruba Central. By default, only wireless device details are retrieved. You have the option to retrieve details for both wired and wireless devicesPANW IoT 3rd Party Integration - cisco-dnac-IoTextract-dnac-clientsYesRequired: "Integration Instance Name".Optional: "Site Names" and "Playbook Poll Interval".Retrieves active devices found by IoT Security, queries Cisco DNA Center to get associated device attributes, and reports the data to IoT Security. Filters for active devices: Site names and playbook poll interval.PANW IoT 3rd Party Integration - Cisco Meraki CloudGet Cisco Meraki Cloud Organizations and Networks - PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name"Retrieves Cisco Meraki Cloud organizations and networks.PANW IoT 3rd Party Integration - Cisco Meraki CloudImport Cisco Meraki Cloud Network Clients - PANW IoT 3rd Party IntegrationYesRequired:"Integration Instance Name"Optional:"Cisco Meraki Networks"Optional:"Cisco Meraki Organizations"Optional:"Poll Interval" (Range: 1-31 days, default: 31)Imports all the Cisco Meraki Cloud clients to IoT Security.PANW IoT 3rd Party Integration - Cisco PrimeCisco Prime ClientsYesRequired: "Integration Instance Name".Optional: "Site Names" and "Playbook Poll Interval".Retrieves active devices found on IoT Security, queries Cisco Prime to get associated device attributes, and reports the data to IoT Security. Filters for active devices: Site names and playbook poll interval.PANW IoT 3rd Party Integration - SNMPIncremental SNMP data import to PANW IoT Cloud - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Performs an SNMP crawl, retrieves all available endpoint data, and reports it to IoT Security.PANW IoT 3rd Party Integration - Network DiscoveryNetwork Discovery - Export Devices using SNMPYesRequired: "Integration Instance Name".Optional: Network Discovery Skip Neighbor Discovery PatternsPerforms an SNMP crawl, retrieves all available L2, L3, and endpoint data and reports it to IoT Security.IP Address ManagementIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - BlueCat IPAMBulk Import of subnet network info from BlueCat IPAM to PANW IoT CloudYesRequired: "Integration Instance Name".Fetches available IPAM data from a BlueCat Address Manager and sends it to IoT Security.PANW IoT 3rd Party Integration - Infoblox IPAMBulk Import of subnet network info from Infoblox IPAM to PANW IoT CloudYesRequired: "Integration Instance Name".Fetches available IPAM data from an Infoblox Grid Master and sends it to IoT Security.Wireless Network ControllersIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - Aruba WLAN ControllerImport Aruba WLC devices to PANW IoT cloudYesRequired: "Integration Instance Name".Fetches available endpoint data from an Aruba WLAN controller and sends it to IoT Security.PANW IoT 3rd Party Integration - Cisco WLAN ControllerImport Cisco WLC devices to PANW IoT cloudYesRequired: "Integration Instance Name".Fetches available endpoint data from a Cisco WLAN controller and sends it to IoT Security.Security Information and Event ManagementIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - Syslog SenderBulk Export to SIEM - PANW IoT 3rd Party IntegrationNoNo arguments required. Sends syslogs to all configured instances.Retrieves all devices from IoT Security and sends them to a third-party integration instance.PANW IoT 3rd Party Integration - Syslog SenderIncremental Export to SIEM - PANW IoT 3rd Party IntegrationYesNo arguments required. Sends syslogs to all configured instances. Fixed poll interval is 15 minutes.Retrieves devices from IoT Security and sends them to a third-party integration instance.Although this job is prebuilt on a cohosted XSOAR instance, it must be manually created on a full-featured XSOAR server.Network Access ControlIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - Aruba ClearPassIncremental Export to Aruba ClearPass- PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Playbook Poll Interval", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves devices from IoT Security and sends it to a third-party integration instance. Filters for IoT Security devices: Custom attributes, poll interval, site names, and tag enforcement.PANW IoT 3rd Party Integration - Aruba ClearPassBulk Export to Aruba ClearPass - PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves all devices from IoT Security and sends them to the third-party integration instance. Filters for IoT Security devices: Custom attributes, site names, and tag enforcement.PANW IoT 3rd Party Integration - Cisco ISEIncremental Export to Cisco ISE - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Playbook Poll Interval", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves devices from IoT Security and sends them to a third-party integration instance.Filters for IoT Security devices: Custom attributes, poll interval, site names, and tag enforcement.PANW IoT 3rd Party Integration - Cisco ISEBulk Export to Cisco ISE - PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves all devices from IoT Security and sends them to a third-party integration instance.Filters for IoT Security devices: Custom attributes, site names, and tag enforcement.PANW IoT 3rd Party Integration - Cisco ISE pxGridBulk Export to Cisco ISE pxGrid - PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves all devices from IoT Security and sends them to a third-party integration instance.Filters for IoT Security devices: Custom attributes, site names, and tag enforcement.PANW IoT 3rd Party Integration - Cisco ISE pxGridIncrement Export to Cisco ISE pxGrid - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Playbook Poll Interval", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves devices from IoT Security and sends them to a third-party integration instance. Filters for IoT Security devices: Custom attributes, poll interval, site names, and tag enforcement.PANW IoT 3rd Party Integration - ForescoutIncremental Export to Forescout - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Playbook Poll Interval", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves devices from IoT Security and sends them to a third-party integration instance.Filters for IoT Security devices: Custom attributes, poll interval, site names, and tag enforcement.PANW IoT 3rd Party Integration - ForescoutBulk Export to Forescout - PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Optional: "PANW IoT Device Custom Attributes", "Site Names", and "PANW IoT In Scope Tag Enforcement".Retrieves all devices from IoT Security and sends it to the third party integration instance.Filters for PANW IoT devices: site name(s), custom attributes, tag enforcement.Vulnerability ScanningIntegration NamePlaybookRecurring JobJob ParametersDescriptionDetailsPANW IoT 3rd Party Integration - QualysIncremental Qualys Get Scans and Report Handling V2- PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Generates and retrieves all reports from scans generated in the last hour.PANW IoT 3rd Party Integration - QualysBulk Qualys Get Scans and Report Handling V2- PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Generates and retrieves all reports from scans generated in the last 30 days.PANW IoT 3rd Party Integration - QualysGet Qualys Scanners and Profiles - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Run this job periodically to retrieve names of all scan engines, sites, and vulnerability scan templates that Qualys uses. Set the interval to run the job based on the frequency of change on the Qualys side of the integration.Although this job is prebuilt on a cohosted XSOAR instance and runs every 15 minutes by default, it must be manually created on a full-featured XSOAR server.PANW IoT 3rd Party Integration - QualysQualys Report Handling - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Generates reports for all scans initiated from IoT Security since the last time this job was run. A typical recurring interval is every 20 or 30 minutes.Although this job is prebuilt on a cohosted XSOAR instance, it must be manually created on a full-featured XSOAR server.PANW IoT 3rd Party Integration - Rapid7 NexposeIncremental Rapid7 Get Scans and Report Handling V2- PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Generates and retrieves all reports from scans generated in the last hour.PANW IoT 3rd Party Integration - Rapid7 NexposeBulk Rapid7 Get Scans and Report Handling V2- PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Generates and retrieves all reports from scans generated in the last 30 days.PANW IoT 3rd Party Integration - Rapid7 NexposeGet Nexpose Engines, Sites and Templates - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Run this job periodically to retrieve names of all scan engines, sites, and vulnerability scan templates that Rapid7 uses. Set the interval to run the job based on the frequency of change on the Rapid7 side of the integration.Although this job is prebuilt on a cohosted XSOAR instance and runs every 15 minutes by default, it must be manually created on a full-featured XSOAR server.PANW IoT 3rd Party Integration - Rapid7 NexposeRapid7 Nexpose Report Handling - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Generates reports for all scans initiated from IoT Security since the last time this job was run. A typical recurring interval is every 20 or 30 minutes.Although this job is prebuilt on a cohosted XSOAR instance, it must be manually created on a full-featured XSOAR server.PANW IoT 3rd Party Integration - Tenable.ioIncremental Tenable Get Scans and Report Handling V2- PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Generates and retrieves all reports from scans generated in the last hour.PANW IoT 3rd Party Integration - Tenable.ioBulk Export Devices to ServiceNow - PANW IoT 3rd Party IntegrationNoRequired: "Integration Instance Name".Generates and retrieves all reports from scans generated in the last 30 days.PANW IoT 3rd Party Integration - Tenable.ioPANW IoT Get Tenable Scanners and Profiles - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Run this job periodically to retrieve names of all scan engines, sites, and vulnerability scan templates that Tenable uses. Set the interval to run the job based on the frequency of change on the Tenable side of the integration.Although this job is prebuilt on a cohosted XSOAR instance and runs every 15 minutes by default, it must be manually created on a full-featured XSOAR server.PANW IoT 3rd Party Integration - Tenable.ioTenable Report Handling - PANW IoT 3rd Party IntegrationYesRequired: "Integration Instance Name".Generates reports for all scans initiated from IoT Security since the last time this job was run. A typical recurring interval is every 20 or 30 minutes.Although this job is prebuilt on a cohosted XSOAR instance, it must be manually created on a full-featured XSOAR server.