Set up IoT Security and XSOAR for Forescout Integration
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
Set up IoT Security and XSOAR for Forescout Integration
Set up IoT Security and Cortex XSOAR to integrate with
Forescout.
To set up IoT Security to integrate through
Cortex XSOAR with an on-premises Forescout system, you must install
an XSOAR engine to your network.
You must also configure a
Forescout integration instance in XSOAR and a job that exports device
attributes from IoT Security through XSOAR to your Forescout instance.
To
do this, you need the IP address of your Forescout system, the name
of the Data Exchange (DEX) account in Forescout, and the username and
password of the DEX user account that the XSOAR engine will use
when forming a secure connection with Forescout.
Cortex XSOAR Engine Installation
Because the Forescout system is on premises,
you must install an XSOAR engine to facilitate communications between Forescout
and the Cortex XSOAR cloud. Although it's possible to install an
XSOAR engine on machines running Windows, macOS, and Linux operating
systems, only an engine on a Linux machine supports IoT Security
integrations. For more information about operating system and hardware requirements,
see the Cortex Administrator’s Guide.
We
recommend downloading the 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 XSOAR engine on your network, make sure it can form connections
to your Forescout system on the TCP port on which it’s listening
for connection requests. The default port number is TCP 443.
The
firewall must also allow the 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 XSOAR instance when you log in to the
IoT Security portal and click . It’s visible
in the address bar of the web page displaying the XSOAR interface.
Integrations
Launch Cortex XSOAR
To create an XSOAR engine, access the Cortex XSOAR interface (from the IoT Security portal, click ). Click . Choose
Integrations
Launch Cortex XSOAR
Settings
Engines
+ Create New Engine
Shell
as the type.For installation instructions, see Install Cortex XSOAR Engines.
For
help troubleshooting Cortex XSOAR engines, including installations,
upgrades, connectivity, and permissions, see Troubleshoot Cortex XSOAR Engines and Troubleshoot Integrations Running
on Engines.
Configure IoT Security and Cortex XSOAR
- Log in to IoT Security and from there access Forescout integration settings in Cortex XSOAR.
- Log in to IoT Security and then clickIntegrations.
- IoT Security uses Cortex XSOAR to integrate with Forescout, and the settings you must configure to integrate with it are in the XSOAR interface. To access these settings, clickLaunch Cortex XSOAR.The Cortex XSOAR interface opens in a new browser window.
- ClickSettingsin the left navigation menu, search forforescoutto locate it among other instances.
- Create an integration instance for Forescout.
- ClickAdd instance, configure the following, and leave the other settings at their default values:Name: Enter a name for the instance. Example:Forescout_instance_1Remember the instance name because you are going to use it again when creating a job that Cortex XSOAR will run.Network address: Enter the IP address or domain name of the Forescout Enterprise Manager or standalone appliance. Example:https://10.1.1.125Data Exchange (DEX) Username: Enter the username of the account that the XSOAR engine uses to log in to the Forescout application.Password: Enter the password for the account.DEX Exchange (DEX) Account: Enter the name of the DEX account you configured in Forescout.Use single engine: Choose the XSOAR engine that you installed previously.
- When finished, clickRun testorTest.If the test is successful, a Success message appears. If not, check that the settings were entered correctly and then test the configuration again.
- After the test succeeds, clickSave & exitto save your changes and close the settings panel.
- (Optional) Create more integration instances to which IoT Security and XSOAR will export device attributes.You can add multiple Forescout integration instances, each one with settings to communicate through an XSOAR engine with a different Forescout server. To add another instance, clickAdd instance.
- Add a job to update Forescout with custom endpoint attributes incrementally.
- Copy the name of the integration instance, navigate toJobs, and then clickNew Jobat the top of the page.
- In the New Job panel that appears, enter the following and leave the other settings at their default values:Recurring: Select this because you want to periodically export endpoint attributes to Forescout.Every: 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 anything, the job runs everyday.) This determines how often XSOAR sends data to Forescout. It’s important to set an interval that allows enough time for the job to complete, considering factors such as the number of devices involved, the amount of bandwidth and latency in the connection, and the processing speed of the Forescout server. You might start by running the job every 15 minutes and then increasing it as necessary until each job completes before the next one starts. You can see the run status of a recurring job on the Jobs page. When in progress, its status isRunning. When done, its status changes toCompleted.Name: Enter a name for the job. Example:Forescout - Incremental UpdatesPlaybook: ChooseIncremental Export to Forescout - PANW IoT 3rd Party Integration.Integration Instance Name: Paste the name of the Forescout integration instance you copied earlier. If this field is empty or an entered name doesn’t match an instance, the job won’t run successfully.PANW IoT Device Custom Attributes: By default, IoT Security exports all device attributes through XSOAR to Forescout. If you want to export a subset, clear the Export Attribute check box for the ones you don’t want to export.If you defined your own custom endpoint attribute names in Forescout, replace the default names with those.PANW IoT In Scope Tag Enforcement: SelectYesto filter attributes that IoT Security exports to only devices with theForescouttag type and theIn Scopetag value. If you don’t want to filter exported attributes by tagged devices, leave this asNo. For information about tagging devices in IoT Security, see Tag Management.Playbook Poll Interval: Enter a number (the value, though unspecified, is minutes) defining the period of time during which IoT Security must see newly discovered devices or changes in any attribute fields of previously discovered devices to include their attributes in the list it provides to XSOAR for export. It’s common to use the same interval as the one for running the recurring job. However, if you increase the interval between jobs, you can set a shorter interval for polling than that for the job. If you leave it blank, the default poll interval is 15 minutes.Site Names: Leave the field empty to export device attributes for all sites. To limit exports to devices at one or more sites, enter comma-separated site names.
- Create new job.
- Add a job to export custom endpoint attributes in bulk to Forescout.
- ClickNew Jobat the top of the Jobs page.
- In the New Job panel that appears, enter the following and leave the other settings at their default values:Name: Enter a name for the job. Example:Forescout - Bulk ExportPlaybook: ChooseBulk Export to Forescout - PANW IoT 3rd Party Integration.Integration Instance Name: Paste the name of the Forescout integration instance you copied earlier. If this field is empty or an entered name doesn’t match an instance, the job won’t run successfully.PANW IoT Device Custom Attributes: By default, IoT Security exports all device attributes through XSOAR to Forescout. If you want to export a subset, clear the Export Attribute check box for the ones you don’t want to export.If you defined your own custom endpoint attribute names in Forescout, replace the default names with those.PANW IoT In Scope Tag Enforcement: SelectYesto filter attributes that IoT Security exports to only devices with theForescouttag type and theIn Scopetag value. If you don’t want to filter exported attributes by tagged devices, leave this asNo. For information about tagging devices in IoT Security, see Tag Management.Site Names: Leave the field empty to export device attributes for all sites. To limit exports to devices at one or more sites, enter comma-separated site names.
- Create new job.
- Continue creating more jobs for other Forescout integration instances as needed.
- To enable Forescout integration instances, return to the Settings page and clickEnablefor all the instances you created.
- Export device attributes to Forescout.Whenever you want to export device attributes from IoT Security, selectForescout - Bulk Export(or whatever you named the job) and then clickRun now.The first time you run a job, it triggers XSOAR to report the integration instance that the job references to IoT Security, which then displays the instance on the Integrations page. Be sure to run each job you create at least once to populate the Integrations page with all the integration instances you’re using.When you run the bulk export job, Cortex XSOAR exports device attributes for devices in the IoT Security device inventory through the XSOAR engine to the Forescout instance that the job references. You can do this as often as you want, once a month being a common choice. Each time you do, XSOAR exports the device attributes of all devices in the IoT Security inventory.Although regular, automated incremental updates are now in progress, Forescout doesn’t yet have a complete device inventory from IoT Security. This requires a bulk data export from IoT Security to Forescout that you initiate from the XSOAR interface at a time that’s suitable for network operations. To shorten the time required for the bulk export to complete, plan to run it during off-peak hours on a slow day such as a holiday or weekend. Doing this when network traffic is light can shorten the time needed to complete the job.During the bulk export and after the job completes, the automated incremental update will continue running every 15 minutes.Although it’s possible to run multiple bulk export jobs in parallel, doing so can affect the XSOAR engine performance. Therefore, we advise not running more than one at a time.