Tenable Security Center (previously, Tenable SC) automatically discovers and assesses an environment for vulnerabilities, misconfigurations, and other cybersecurity issues.
Lucidum uses the Tenable Security Center connector to ingest data from Tenable.sc.
For more information about Tenable and Lucidum, see https://lucidum.io/tenable/.
To use the Tenable connector in Lucidum:
Before configuring the Tenable connector in Lucidum, you must first define credentials for Lucidum in the Tenable API.
You can then configure the Tenable connector in Lucidum and start ingesting data from Tenable.
Define Credentials for Lucidum in Tenable
To generate an API key in the Tenable console:
Log in to Tenable Security Center via the user interface.
Click Users > Users. The Users page appears.
Select the check box for the user for which you want to generate an API key. The available actions appear at the top of the table.
Click API Keys > Generate API Key. A confirmation window appears.
Click Generate. The Your API Key window appears, displaying the access key and secret key for the user.
Copy the new access key and secret keys to a safe location.
For details, see https://docs.tenable.com/security-center/Content/GenerateAPIKey.htm
Note: You cannot view API secret keys in the Tenable Security Center interface after initial generation. If you lose your existing secret key, you must generate new API keys.
Configuring the Tenable Connector
To configure Lucidum to ingest data from Tenable:
Log in to Lucidum.
In the left pane, click Connector.
In the Connector page, click Add Connector.
Scroll until you find the Connector for Tenable.sc. Click Connect. The Settings page appears.
In the Settings page, enter the following
Host. The hostname of the Tenable server.
Access Key. Enter the value for the API Key that you generated in the previous section.
Access Secret. Enter the value for the API Secret that you generated in the previous section.
Verify SSL. Optional. Default value is False.
True. Validate that the server certificate matches the expected certificate, usually the locally trusted root certificate used in the browser. If you are connecting to an API via HTTPS, you can select this option.
False. Do not validate the certificate.
To test the configuration, click Test.
If the connector is configured correctly, Lucidum displays a list of services that are accessible with the connector.
If the connector is not configured correctly, Lucidum displays an error message.
The Tenable connector supports these Actions:
Add IPs to Tenable Scan