Set up IoT Security and XSOAR for Cisco WLAN Controllers
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 Cisco WLAN Controllers
IoT Security
and XSOAR for Cisco WLAN ControllersSet up
IoT Security
and Cortex XSOAR
to integrate with
Cisco WLAN controllers.To set up
IoT Security
to integrate through
Cortex XSOAR
with a Cisco WLAN controller, you must add an XSOAR
engine to your network.You must also configure
Cortex XSOAR
with a Cisco WLAN controller integration instance and a job to periodically
collect device data from the controller. To do this, you need the
IP address or hostname of your Cisco WLAN controller and the username
and password of the read/write user account that the XSOAR engine
will use when forming a secure connection with it.Cortex XSOAR Engine Installation
Cortex XSOAR
Engine InstallationAn on-premises XSOAR engine facilitates communications
between the
Cortex XSOAR
cloud and Cisco WLAN controllers. 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 SSH connections
to your Cisco WLAN controllers. By default, SSH uses TCP port 22.
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 from there access Cisco WLAN controller settings inCortex XSOAR.
- Log in toIoT Securityand then clickIntegrations.
- IoT SecurityusesCortex XSOARto integrate with Cisco WLAN controllers, 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 forcisco wlanto locate it among other instances.
- Configure the Cisco WLAN Controller (WLC) integration instance.
- ClickAdd instanceto open the settings panel.
- Enter the following settings:Name: Use the default name of the instance 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 device data from the controller in this instance.Cisco WLC IP or Hostname: Enter the IP address or hostname of the wireless controller.Username: Type the name of the user account that you previously created for the XSOAR engine to use when connecting to the WLAN controller.Password: Type the password associated with the user account.Run on Single engine: Choose the XSOAR engine that you want to communicate with this Cisco WLAN controller.
- 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.
- Create a job for XSOAR to query the Cisco WLAN controller for details about currently active devices and send them toIoT Security.IoT Securityonly updates attributes for devices that are in its database and whose MAC address matches that returned by the controller. If your network has static IP devices without MAC addresses, they will not be updated.
- Copy the name of the instance you just created, navigate to Jobs, 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 poll the controller for device details.Every: Enter a number and set the interval value (Minutes, Hours, Days, or Weeks) and select the days on which to run the job. This determines how often XSOAR queries the controller for details about active devices. For example: 15 minutes.Name: Enter a name for the job.Playbook: ChooseImport Cisco WLC devices to PANW IoT cloud.Integration Instance Name: Paste the instance name you copied a few moments ago.
- ClickCreate new job.The job appears in the Jobs list.
- Enable the job and run it.
- Check the Job Status for the job you created. If it’s Disabled, select its check box and then clickEnable.
- After you enable it, keep the check box selected and clickRun now. The Run Status changes from Idle to Running. In addition, running a job in XSOAR triggers the referenced integration instance to appear on the Integrations page in theIoT Securityportal.At the defined interval, XSOAR begins querying the Cisco WLAN controller for client details, which it then forwards to theIoT Securitycloud.
- If you created more integration instances for multiple Cisco WLAN controllers, add more jobs as necessary.Each Cisco WLAN controller instance requires a separate job.Run each job you create at least once to populate the Integrations page with all the integration instances you’re using in XSOAR.
- When done, return to theIoT Securityportal and check the status of the Cisco WLAN Controller integration.An integration instance can be in one of the following four states, whichIoT Securitydisplays in the Status column on the Integrations page:
- Disabledmeans that either the integration was configured but intentionally disabled or it was never configured and a job that references it is enabled and running.
- Errormeans that the integration was configured and enabled but is not functioning properly, possibly due to a configuration error or network condition.
- Inactivemeans that the integration was configured and enabled but no job has run for at least the past 60 minutes.
- Activemeans that the integration was configured and enabled and is functioning properly.
When you see that the status of an integration instance isActive, its setup is complete. At the defined interval, XSOAR begins the job by first requesting an active device list fromIoT Securityand then using that list to query a Cisco WLAN controller for client details, which it forwards to theIoT Securitycloud.