Set up IoT Security and XSOAR for SIEM Integration
Set up IoT Security and Cortex XSOAR to integrate with SIEM.
To set up IoT Security to integrate through Cortex XSOAR with SIEM, you must add a Cortex XSOAR engine to your network. This engine will receive syslog notifications in CEF format from IoT Security and send them on to the SIEM server.
You must also configure the SIEM integration instance in XSOAR. To do this, you need the IP address of your SIEM server.
Cortex XSOAR Engine Installation
The Cortex XSOAR engine initiates connections to the SIEM server and to the Cortex cloud and provides the means through which they communicate with each other. 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 reach your SIEM server on UDP port 514, or whatever protocol and port for which the server is configured to listen for incoming syslog event notifications.
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.
For help troubleshooting Cortex XSOAR engines, including installations, upgrades, connectivity, and permissions, see Troubleshoot Cortex XSOAR Engines and Troubleshoot Integrations Running on Engines.
Configure IoT Security and Cortex XSOAR
- Log in to IoT Security and from there access SIEM settings in Cortex XSOAR.
- Log in to IoT Security and then clickIntegrations.
- IoT Security uses Cortex XSOAR to integrate with SIEM, and the settings you must configure to integrate with SIEM 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 forsiemto locate it among other instances.
- Configure the SIEM integration instance.
- Click the SIEM instance settings icon ( ) to open the settings panel.
- Enter the SIEM server IP address and the protocol and port number on which it listens for syslog notification messages. Choose the XSOAR engine that you want to communicate with the SIEM server and leave the other settings at their default values.
- 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 PANW IoT 3rd Party SIEM Integration Instance, clickEnable.
- Return to the IoT Security portal and check the status of the Syslog Server integration.XSOAR automatically runs a preconfigured job for SIEM integration (PANW IoT 3rd Party Integration - Syslog Sender) and reports the integration instance to IoT Security, which displays it on the Integrations page. The integration instance can be in one of the following four states, which IoT Security displays in the Status column on the Integrations page:
When you see that the status of the integration instance has changed fromDisabledtoActive, its setup is complete.XSOAR begins an automated process that sends SIEM incrementally updated data from IoT Security about changes to device attributes, new alerts, and new vulnerabilities occurring within the last 15 minutes.
- 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.
- Export the IoT device inventory from IoT Security to SIEM.Although regular, automated incremental updates are now in progress, SIEM doesn’t yet have a complete device inventory, list of currently active security alerts, or list of unresolved device vulnerabilities from IoT Security. This requires a bulk data export from IoT Security to SIEM that you initiate from the XSOAR interface at a time that’s suitable for network operations. To shorten the time required for the bulk export to complete, plan to run it during off-peak hours on a slow day such as a holiday or weekend. Exporting an inventory of 30,000-40,000 IoT devices takes up to 12 hours when a network is under normal usage. Doing this when network traffic is light can shorten the time needed to complete the job.To start the bulk export of the entire device inventory, clickLaunch Cortex Accessto return to the XSOAR interface. ClickJobs, selectPANW IoT Bulk Export to SIEM, and then clickRun now.During the bulk export and after the job completes, the automated incremental update will continue running every 15 minutes.Although it’s possible to run multiple bulk export jobs in parallel, doing so can affect the XSOAR engine performance. Therefore, we advise not running more than one at a time.
Recommended For You
Recommended videos not found.