Set up IoT Security and XSOAR for Tenable Integration
Set up IoT Security and Cortex XSOAR to integrate with
Tenable.
- Log in to IoT Security and from there access Tenable settings in Cortex XSOAR.
- Log in to IoT Security and then clickIntegrations.
- IoT Security uses Cortex XSOAR to integrate with Tenable, 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 fortenableto locate it among other instances.
- Edit the settings for PANW IoT 3rd Party Tenable Integration Instance.
- Click the active integration instance settings icon (
) to open the
settings panel. - Enter the following settings and leave the others at their default values:Name: Use the default name of the integration instance.Do not change the default integration instance name. The XSOAR jobs that support vulnerability scans from the Device Details page in the IoT Security portal rely on XSOAR playbooks that refer to this integration instance name specifically.URL:https://cloud.tenable.comAccess Key: Paste the access key text string that you previously copied and saved.Secret Key: Paste the secret key text string that you previously copied and saved.
- 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 Tenable Integration Instance, clickEnable.
- Return to the IoT Security portal and check the status of the Tenable integration instance.XSOAR automatically runs a preconfigured job for Tenable integration 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 as shown 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 the Tenable instance has changed fromDisabledtoActive, its setup is complete.
For more information about Tenable vulnerability scans, see Get Vulnerability Scan Reports from Tenable.
