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 click

Integrations

.



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, click

Launch Cortex XSOAR

.

The Cortex XSOAR interface opens in a new browser window.

Click

Settings

in the left navigation menu, search for

forescout

to locate it among other instances.


Create an integration instance for Forescout.
Click
Add instance
, configure the following, and leave the other settings at their default values:
Name
: Enter a name for the instance. Example:
Forescout_instance_1
Remember 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.125
Data 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, click
Run test
or
Test
.
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, click
Save & exit
to 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, click
Add instance
.
Add a job to update Forescout with custom endpoint attributes incrementally.
Copy the name of the integration instance, navigate to
Jobs
, and then click
New Job
at 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 is
Running
. When done, its status changes to
Completed
.
Name
: Enter a name for the job. Example:
Forescout - Incremental Updates
Playbook
: Choose
Incremental 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
: Select
Yes
to filter attributes that IoT Security exports to only devices with the
Forescout
tag type and the
In Scope
tag value. If you don’t want to filter exported attributes by tagged devices, leave this as
No
. 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.
Click
New Job
at 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 Export
Playbook
: Choose
Bulk 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
: Select
Yes
to filter attributes that IoT Security exports to only devices with the
Forescout
tag type and the
In Scope
tag value. If you don’t want to filter exported attributes by tagged devices, leave this as
No
. 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 click
Enable
for all the instances you created.
Export device attributes to Forescout.
Whenever you want to export device attributes from IoT Security, select
Forescout - Bulk Export
(or whatever you named the job) and then click
Run 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.