Windows Integration

Tenable Nessus Manager provides an option for CyberArk Windows integration. Complete the following steps to configure Tenable Nessus Manager with CyberArk for Windows.

Requirements:

• CyberArk account
• Nessus Manager account

To configure Windows integration:

1. Log in to Nessus.
2. Click Scans.

3. Click + New Scans.

   The Scan Templates page appears.

4. Select a Scan Template.

   The selected scan template appears.

5. In the Name box, type a name for the scan.

6. In the Targets box, type an IP address, hostname, or range of IP addresses.
7. (Optional) Add a description, folder location, scanner location, and specify target groups.

8. Click the Credentials tab.

   The Credentials options appear.

9. In the left-hand menu, select Windows.

10. Click Authentication method.

    A drop-down appears.

11. Select CyberArk.

12. Configure each field for Windows authentication.

    Caution: Tenable strongly recommends encrypting communication between the Nessus scanner and the CyberArk AIM gateway using HTTPS and/or client certificates. For information on securing the connection, refer to the Nessus User Guide and the Central Credential Provider Implementation Guide located at cyberark.com (login required).

    Option	Description	Required
    Port	The port on which the CyberArk API communicates. By default, Tenable uses 443.	yes
    Account Name	(If Get credential by is Identifier) The unique account name or identifier assigned to the CyberArk API credential.	no
    Address	The option should only be used if the Address value is unique to a single CyberArk account credential.	no
    AppID	The Application ID associated with the CyberArk API connection.	yes
    Client Certificate	The file that contains the PEM certificate used to communicate with the CyberArk host. Note: Customers self-hosting CyberArk CCP on a Windows Server 2022 and above should follow the guidance found in Tenable’s Community post about CyberArk Client Certification Authentication Issue.	no
    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
    CyberArk Host	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.	yes
    Domain	(Required if Kerberos Target Authentication is enabled) The domain to which Kerberos Target Authentication belongs, if applicable.	yes
    Get credential by	The method with which your CyberArk API credentials are retrieved. Can be Address, Identifier, Parameters, or Username. Note: For more information about the Parameters option, refer to the Parameters Options table. 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.	yes
    KDC Port	The port on which the Kerberos authentication API communicates. By default, Tenable uses 88.	no
    KDC Transport	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.	no
    Kerberos Target Authentication	If enabled, Kerberos authentication is used to log in to the specified Linux or Unix target.	no
    Key Distribution Center (KDC)	(Required if Kerberos Target Authentication is enabled) This host supplies the session tickets for the user.	yes
    Safe	The CyberArk safe the credential should be retrieved from.	no
    Use SSL	If enabled, the scanner uses SSL through IIS for secure communications. Enable this option if CyberArk is configured to support SSL through IIS.	no
    Username	(If Get credential by is set to Username) The username of the CyberArk user to request a password from.	no
    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.	no

    Parameters Options

    The following options can be specified when Get Credential By is set to Parameters. These request parameters allow for advanced filtering of accounts based on their properties. The options correspond to the various options supported by the CyberArk REST API, as found in CyberArk documentation. These options can be specified in many different combinations to filter account results by their properties. For example, specifying Root as the Folder option results in a REST API query containing &Folder=Root.

    Option	Description	Required
    Safe	The safe containing the credential.	no
    Address	Limit the query to accounts matching the specified address.	no
    Use Target IP Address	(Optional) When enabled, the integration appends the target address to the credential query, which limits the query to accounts matching the scan target’s address. This is ignored if Address is set.	no
    Username	The username of the credential.	no
    Account Name	The unique identifier assigned to the credential.	no
    Folder	The folder of the credential.	no
    Database	The database of the credential.	no
    Query	Specify a custom “free query” using account properties. When this method is specified, all other search criteria are ignored.	no
    Query Format	Defines the query format. allowed values are Exact and Regexp. The default is Exact. This value is ignored unless the Query option was specified.	no

    CyberArk credential field mapping to the CyberArk Accounts detail view in the CyberArk console:

    

13. Click Save.

Verification

1. To verify the integration is working, click the Launch button (highlighted below) to initiate an on-demand scan.

   

2. Once the scan has completed, select the completed scan. Look for the corresponding ID (see chart below), which validates that authentication was successful. If the authentication is not successful, refer to the Debugging CyberArk Issues section of this document.