Configure Tenable Nessus for Lieberman SSH

Tenable Nessus provides an option for Lieberman SSH integration. Complete the following steps to configure Nessus with Lieberman SSH. (Any other descriptive verbiage we can add here?)

To configure Nessus for Lieberman SSH:

  1. In a browser, log in to Nessus.

  2. Navigate to the Scans section.

  3. Click the + New Scan button to configure Nessus for credentialed scans of Windows systems using Lieberman's password management solution.

  4. Select a Scan Template for the scan type required for your scan. For demonstration purposes, the Advanced Network Scan template is used.

  5. Enter a descriptive Name and the IP address(es) or hostname(s) of the scan Targets.

  6. Click on the Credentials tab.

  7. In the left-hand menu, select SSH.

  8. From the Authentication Method drop-down, select Lieberman.

  9. Configure each field for SSH authentication.

    Option Description Required
    Username The target system’s username.

    yes
    Lieberman host

    The Lieberman IP/DNS address.

    Note: If your Lieberman installation is in a subdirectory, you must include the subdirectory path. For example, type IP address or hostname / subdirectory path.

    yes
    Lieberman port The port on which Lieberman listens.

    yes
    Lieberman API URL The URL Tenable Vulnerability ManagementTenable Nessus uses to access Lieberman. no
    Lieberman user The Lieberman explicit user for authenticating to the Lieberman RED API.

    yes
    Lieberman password The password for the Lieberman explicit user.

    yes
    Lieberman Authenticator

    The alias used for the authenticator in Lieberman. The name should match the name used in Lieberman.

    Note: If you use this option, append a domain to the Lieberman user option, i.e., domain\user.

    		 no
    Lieberman Client Certificate

    The file that contains the PEM certificate used to communicate with the Lieberman host.

    Note: If you use this option, you do not have to enter information in the Lieberman user, Lieberman password, and Lieberman Authenticator fields.

    		 no
    Lieberman Client Certificate Private Key The file that contains the PEM private key for the client certificate. no
    Lieberman Client Certificate Private Key Passphrase The passphrase for the private key, if required. no
    Use SSL

    If Lieberman is configured to support SSL through IIS, check for secure communication.

    no
    Verify SSL Certificate

    If Lieberman is configured to support SSL through IIS and you want to validate the certificate, check this option. Refer to Custom CA documentation for how to use self-signed certificates.

    no
    Targets to Prioritize Credentials (missing or bad snippet) no
    System Name In the rare case your organization uses one default Lieberman entry for all managed systems, enter the default entry name.

    no
    Custom password prompt The password prompt used by the target host. Only use this setting when an interactive SSH session fails due to Tenable Vulnerability ManagementTenable Nessus receiving an unrecognized password prompt on the target host's interactive SSH shell.

    no
  1. Click Save.

What to do next:

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

  2. Once the scan has completed, select the completed scan and look for Plugin ID 97993 and the corresponding message - It was possible to log into the remote host via SSH using 'password' authentication. This validates that authentication was successful.