Set up IoT Security and XSOAR for Cisco WLAN Controllers
Set 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
An 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 IoT Security portal and click
. It’s visible in the address bar of the web page displaying the XSOAR interface.
Launch Cortex XSOAR
To create an XSOAR engine, access the Cortex XSOAR interface (from the IoT Security portal, click
Launch Cortex XSOAR
+ Create New Engine
Shellas the type.
For installation instructions, see Install Cortex XSOAR Engines.
Configure IoT Security and Cortex XSOAR
- Log in to IoT Security and from there access Cisco WLAN controller settings in Cortex XSOAR.
- Log in to IoT Security and then clickIntegrations.
- IoT Security uses Cortex XSOAR to 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 XSOAR.The Cortex XSOAR interface 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 that Cortex XSOAR will 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 to IoT Security.IoT Security only 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.At the defined interval, XSOAR begins querying the Cisco WLAN controller for client details, which it then forwards to the IoT Security cloud.
- If you created more integration instances for multiple Cisco WLAN controllers, add more instances as necessary.Each Cisco WLAN controller instance requires a separate job.
- When done, return to the IoT Security portal and check the status of the Cisco WLAN Controller integration.One of three states can appear in the Status column on the Integrations page.
When you see that its status isActive, the setup for IoT Security/Cortex XSOAR integration with Cisco WLAN controllers is complete. At the defined interval, XSOAR begins the job by first requesting an active device list from IoT Security and then using that list to query a Cisco WLAN controller for client details, which it forwards to the IoT Security cloud.
- Disabledmeans that either the integration was never configured (its default state) or it was configured but intentionally disabled.
- Inactivemeans that the integration was configured and enabled but is not functioning properly, possibly due to a configuration error or network condition.
- Activemeans that the integration was configured and enabled and is functioning properly.
Recommended For You
Recommended videos not found.