Set up IoT Security and XSOAR for AIMS 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 AIMS Integration
IoT Security
and XSOAR for AIMS IntegrationSet up
IoT Security
and Cortex XSOAR
to integrate with
AIMS.To set up
IoT Security
to integrate through
Cortex XSOAR
with an on-premises AIMS system, you must install an
XSOAR engine to your network.You must also configure the
AIMS integration instance in XSOAR and two jobs that pull data from
AIMS through XSOAR to
IoT Security
:- A facility job that periodically pulls employee and priority information
- A job that imports device data
To do this,
you need the URL of your AIMS system, the port number on which it
listens for connection requests, and the username and password of
the AIMS user account that the XSOAR engine will use when forming
a secure connection with Rapid7.
Cortex XSOAR Engine Installation
Cortex XSOAR
Engine InstallationWhen the AIMS system is on premises, you must
install an XSOAR engine to facilitate communications between the
AIMS system and
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 AIMS 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 . It’s visible in the address bar of the web page displaying the
XSOAR interface.
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 then access AIMS settings inCortex XSOAR.
- Log in toIoT Securityand then clickIntegrations.
- IoT SecurityusesCortex XSOARto integrate with AIMS, and the settings you must configure to integrate with 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 foraimsto locate it among other instances.
- Configure an AIMS integration instance.
- ClickAdd instanceto open the settings panel.
- Enter the following and leave other settings at their default values:Name: Use the default name of the instance (AIMS_instance_1) or enter a new one.Remember the instance name because you are going to use it again when creating jobs thatCortex XSOARwill run.AIMS Server (IP or hostname): Enter IP address or domain name of the AIMS server followed by the port number on which it listens for connection requests. By default, it listens on TCP port 443. For example:10.1.1.150:443Auth Token: Enter the client ID that you recorded earlier when setting up AIMS.Trust any certificate (not secure): (select)Use single engine: For cloud-based AIMS systems, chooseNo engine. For on-premises AIMS systems, choose the XSOAR engine that you previously installed.
- 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.
- To enable the AIMS integration instance, clickEnable.
- Create a job that retrieves device data from AIMS through XSOAR toIoT Security.This job regularly imports device data from AIMS throughCortex XSOARtoIoT Security.
- ClickJobsnear the bottom of the left navigation menu to open the Jobs page.
- ClickNew Jobat the top of the Jobs page.
- Enter the following, leave the other fields at their default values:Name: Type a name for the job such asAIMS device retrieval.Time triggered: (select)Recurring: (select)
- Every: Enter the number of hours, minutes, days, or weeks to check AIMS for device data. Typically, shorter intervals provide more timely updates for active networks. However, for large networks, more frequent updates might exacerbate an already heavy traffic load. Weigh the two factors of activity and size when deciding and remember that you can always edit the playbook later to adjust this setting.
- On: Select the days of the week that this job will run, or leave them unselected to run everyday.
Playbook:Export AIMS maps and devices to PANW IoTIntegration Instance Name: Enter the name of the AIMS integration instance you defined earlier. For example: - When complete,Create new job.
- Create a job that periodically retrieves work order assignee and priority lists from AIMS.This retrieves a list of employees and work order priority levels that populate fields in the Send Work Order dialog box in theIoT Securityportal. This allows theIoT Securityuser to select this information when generating AIMS work orders to investigate security incidents.
- On the Jobs list, clickNew Jobat the top of the Jobs page.
- Enter the following, leave the other fields at their default values:Name: Type a name for the job such asAIMS assignee and priority lists retrieval.Time triggered: (select)Recurring: (select)
- Every: Enter the number of hours, minutes, days, or weeks to retrieve AIMS employee and work order priority lists.
- On: Select the days of the week that this job will run, or leave them unselected to run everyday.
Playbook:Export AIMS assignee and priority list to PANW IoTIntegration Instance Name: Enter the name of the AIMS integration instance you defined earlier. For example:AIMS_instance_1
- When complete,Create new job.Run a job for each integration instance you create. The first time you run a job that references an integration instance triggers XSOAR to report the instance toIoT Security, which then displays the integration instance on the Integrations page.