Set up IoT Security and XSOAR for AssetCentre 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 AirWave
- Set up Aruba AirWave for Integration
- Set up IoT Security and Cortex XSOAR for Aruba AirWave Integration
- View Device Location Information
- 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 AssetCentre Integration
IoT Security
and XSOAR for AssetCentre IntegrationSet up
IoT Security
and Cortex XSOAR
to integrate with AssetCentre.To set up
IoT Security
to integrate through Cortex XSOAR
with AssetCentre, configure
XSOAR with a Rockwell AssetCentre integration instance and jobs to import device
data. You can set the job to import device data incrementally to run at regular
intervals. The configuration requires the following information from
AssetCentre:- IP address or hostname, port number, and name of the Microsoft SQL server
- Username and password of the Windows Active Directory user account that XSOAR uses when connecting to the Microsoft SQL server
When using a cohosted XSOAR instance, a cloud-hosted XSOAR server, or an
on-premises XSOAR server that cannot reach part of the network, you must also add a
Cortex XSOAR
engine to your network.Cortex XSOAR Engine Installation
Cortex XSOAR
Engine InstallationWhen using a cohosted XSOAR instance, a cloud-hosted XSOAR server, or an
on-premises XSOAR server that cannot reach part of the network, XSOAR
communicates with AssetCentre through an on-premises XSOAR engine. 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 AssetCentre system on the TCP port on which it’s listening for
connection requests. The default port number is TCP 1433.
When using the cohosted . It’s visible in the address bar of the web page displaying the
XSOAR interface. When using a cloud-hosted Cortex server or a server deployed
on-premises with an engine, make sure the engine can reach an equivalent URL on
your server.
Cortex XSOAR
instance, intervening firewalls 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 Integrations
Launch
Cortex XSOAR
To create an XSOAR engine, access the ). Click . Choose
Cortex XSOAR
interface (from the
IoT Security
portal, click Integrations
Launch
Cortex XSOAR
Settings
Engines
+ Create New Engine
Shell
as the type.For installation instructions, see Install .
For help troubleshooting
Cortex XSOAR
engines, including installations,
upgrades, connectivity, and permissions, see Troubleshoot and Troubleshoot Integrations Running on
Engines.Configure IoT Security and Cortex XSOAR
IoT Security
and Cortex XSOAR
- Log in toIoT Securityand from there access AssetCentre settings inCortex XSOAR.
- Log in toIoT Securityand then clickIntegrations.
- IoT SecurityusesCortex XSOARto integrate with AssetCentre, and the settings you must configure to integrateIoT Securitywith it are in the XSOAR interface. To access these settings, clickLaunch.Cortex XSOARTheCortex XSOARinterface opens in a new browser window.
- ClickSettingsin the left navigation menu, search forassetcentreto locate it among other instances.
- Configure the Rockwell AssetCentre integration instance.
- ClickAdd instanceto open the settings panel.
- Enter the following and leave the other settings at their default values:Name: Either use the default name (Rockwell AssetCentre_instance_1) or enter a new one.Remember the instance name because you are going to use it again when creating a job thatCortex XSOARwill run to gather data from the SQL database specified in this integration instance.SQL Server Host/IP: Enter the domain name or IP address of the Microsoft SQL server.SQL Server Port: Enter the default TCP port number 1433 or, if a different port number is set on the SQL server, enter that.SQL Database: Enter the name of the database from which you want XSOAR to retrieve device information.Each integration instance can retrieve device information from a single database. If you want to retrieve device information from other databases, you must create additional integration instances for them.Username: Enter the name of the user account you previously configured for XSOAR to access the Microsoft SQL server.Password: Enter the password associated with the user account.Run on Single engine: Choose the XSOAR engine that you want to communicate with the Microsoft SQL server.
- When finished, clickTest.Cortex XSOARattempts to connect to the Microsoft SQL server using the connection settings and credentials you entered. 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.
- To enable the Rockwell FactoryTalk AssetCentre integration instance, clickEnable.
- Create a job for XSOAR to retrieve information about devices in the AssetCentre SQL database specified in the integration instance and then forward it toIoT Security.
- Copy the name of the integration instance and open a duplicate browser window.
- Navigate to Jobs in the new window, 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:Time triggered: (select)Recurring: Select this because you want to periodically import device information from AssetCentre.Every: Enter a number and set the interval value (Minutes, Hours, Days, or Weeks) and select the days and times on which to run the job. This determines how often and when XSOAR retrieves data from AssetCentre. Consider running the job every day or every other day at a time when network activity is light, such as late at night, to help reduce potential latency. As a general guideline, it takes approximately 20 minutes for XSOAR to import data for 10,000 devices intoIoT Security. You can see the run status of a recurring job on the Jobs page and note how long it takes. When in progress, its status isRunning. When done, its status changes toCompleted.Name: Enter a name for the job.Playbook: ChooseImport Rockwell AssetCentre devices to PANW IoT cloud.Integration Instance Name: Paste the name of the integration instance that you copied earlier.Playbook Poll Interval: If you want to import device information incrementally from AssetCentre, enter a number indicating the period of time that XSOAR polls AssetCentre for any newly discovered devices or new or different attributes for previously discovered devices. The value you enter, though unspecified, is minutes. When XSOAR runs the next job, it then imports the devices and attributes toIoT Securitythat AssetCentre discovered during this interval. 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,Cortex XSOARimports all available device attributes each time the job runs the playbook. XSOAR then uploads whatever is new or has changed since the last import toIoT Security.
- Create new job.
- OptionalCreate more integration instances and jobs to import device information from other AssetCentre databases intoIoT Security.To create more integration instances, repeat the previous steps, entering unique names for each one and different settings as appropriate for your AssetCentre databases.For each additional integration instance, create a job forCortex XSOARto run, with a similar configuration as the one you initially created. However, as you add more jobs, consider staggering their run times so that the data retrievals are spread out.