To configure Tenable Vulnerability Management with CyberArk using Windows integration:
- Log in to Tenable Vulnerability Management.
In the upper-left corner, click the button.
The left navigation plane appears.
In the left navigation plane, click Settings.
The Settings page appears.
Click the Credentials widget.
The Credentials page appears. The credentials table lists the managed credentials you have permission to view.
Click the button next to the Credentials title.
The credential form plane appears.
In the Host section, click Windows.
The selected credential options appear.
In the Authentication Method drop-down, select CyberArk.
The CyberArk options appear.
Configure the CyberArk credentials.
Option Description Required
The IP address or FQDN name for the CyberArk AIM Web Service. This can be the host, or the host with a custom URL added on in a single string.
The port on which the CyberArk API communicates. By default, Tenable uses 443.
The Application ID associated with the CyberArk API connection.
Client Certificate The file that contains the PEM certificate used to communicate with the CyberArk host.
Client Certificate Private Key The file that contains the PEM private key for the client certificate.
yes, if private key is applied
Client Certificate Private Key Passphrase The passphrase for the private key, if required.
yes, if private key is applied
Kerberos Target Authentication
If enabled, Kerberos authentication is used to log in to the specified Linux or Unix target.
Key Distribution Center (KDC)
(Required if Kerberos Target Authentication is enabled.) This host supplies the session tickets for the user.
The port on which the Kerberos authentication API communicates. By default, Tenable uses 88.
The KDC uses TCP by default in Linux implementations. For UDP, change this option. If you need to change the KDC Transport value, you may also need to change the port as the KDC UDP uses either port 88 or 750 by default, depending on the implementation.
(Required if Kerberos Target Authentication is enabled.) The domain to which Kerberos Target Authentication belongs, if applicable.
Get credential by
The method with which your CyberArk API credentials are retrieved. Can be Username, Identifier, or Address.
Note: The frequency of queries for Username is one query per target. The frequency of queries for Identifier is one query per chunk. This feature requires all targets have the same identifier.
Note: The Username option also adds the Address parameter of the API query and assigns the target IP of the resolved host to the Address parameter. This may lead to failure to fetch credentials if the CyberArk Account Details Address field contains a value other than the target IP address.
(If Get credential by is Username) The username of the CyberArk user to request a password from.
The CyberArk safe the credential should be retrieved from.
no Address The option should only be used if the Address value is unique to a single CyberArk account credential. no Account Name (If Get credential by is Identifier) The unique account name or identifier assigned to the CyberArk API credential. no
If enabled, the scanner uses SSL through IIS for secure communications. Enable this option if CyberArk is configured to support SSL through IIS.
Verify SSL Certificate
If enabled, the scanner validates the SSL certificate. Enable this option if CyberArk is configured to support SSL through IIS and you want to validate the certificate.
Caution: Tenable strongly recommends encrypting communication between your on-site scanner and the CyberArk AIM gateway using HTTPS and/or client certificates. For information on securing the connection, refer to the Tenable.io User Guide and the Central Credential Provider Implementation Guide located at cyberark.com (login required).
- Click Save.
To verify the integration is working, click the Launch button to initiate an on-demand scan.
After the scan completes, click the scan to view the results.
Look for Plugin ID 10394. This validates that the authentication was successful. If the authentication is not successful, refer to the Debugging CyberArk Issues section of this document.