IoT Security
Set up AIMS for Integration
Table of Contents
Expand All
|
Collapse All
IoT Security Docs
-
-
- Firewall Deployment Options for IoT Security
- Use a Tap Interface for DHCP Visibility
- Use a Virtual Wire Interface for DHCP Visibility
- Use SNMP Network Discovery to Learn about Devices from Switches
- Use Network Discovery Polling to Discover Devices
- Use ERSPAN to Send Mirrored Traffic through GRE Tunnels
- Use DHCP Server Logs to Increase Device Visibility
- Control Allowed Traffic for Onboarding Devices
- Support Isolated Network Segments
-
Set up AIMS for Integration
Set up AIMS for integration with IoT Security through
Cortex XSOAR.
Where Can I Use This? | What Do I Need? |
---|---|
|
One of the following Cortex XSOAR setups:
|
Set up an AIMS API configuration to define the maximum number of device records that
AIMS will provide to IoT Security and record the client ID that AIMS
generates. You will use the client ID when configuring the AIMS integration instance
in Cortex XSOAR.
These instructions are based on AIMS version 2.6.11. IoT Security supports all AIMS v2
builds but not AIMS v3.
- Log in to the AIMS system and click TransferAPI Configuration.The API Configuration dialog box appears.
- Configure the AIMS API settings.Enter the following and then click Add:Name: Enter a name for your API configuration.Type: APIRecord Limit: Set the maximum number of device records that AIMS will provide to IoT Security, keeping in mind that there is one record per device. In the following screen capture, the maximum is 2500 records. If there are more than 2500 records in the AIMS inventory that you want to import, increase the maximum to accommodate them. You can increase this as high as 100,000.
- Record the client ID for use when configuring the AIMS integration instance in Cortex XSOAR and then click Close.