Configuring Nessus for Centrify Vault

To configure Nessus for Centrify Vault, perform the following steps:

• To configure the Nessus Manager with Centrify Privileged Access Service for Windows
• Configuring Nessus for Centrify (SSH).

Requirements

• Nessus Manager account.
• Centrify Privileged Access Service account.

• Required User Role: Standard, Administrator, or System Administrator.

To configure the Nessus Manager with Centrify Privileged Access Service for Windows

To configure Nessus Manager with Centrify PAS using Windows credentials, complete the following steps:

1. Log into Nessus Manager. Click Scans. The My Scans page appears.

3. Click + New Scan. The Scan Templates page appears:

2. Select a scan template. The selected scan template Settings page appears.
3. In the Name field, enter a name for the scan.
4. In the Targets field, enter an IP address, hostname, or range of IP addresses.
5. (Optional) Add a description, folder location, scanner location, and specify target groups.
6. Click the Credentials tab. The Credentials options appear. By default, the Categories drop-down box displays Host.

7. In the left menu, select Windows. The Windows settings appear.
8. In the Windows settings, click the Authentication method drop-down box. The Authentication method drop-down box options appear.

9. Select Centrify. The Centrify options appear.
10. Configure the Windows credentials.

Option	Default Value
Centrify Host	(Required) The Centrify IP address or DNS address. Note: If your Centrify installation is in a subdirectory, you must include the subdirectory path. For example, type IP address or hostname/sub- directory path.
Centrify Port	The port on which Centrify listens.
API User	(Required) The API user provided by Centrify
API Key	(Required) The API key provided by Centrify.
Tenant	The name of a specified team in a multi-team environment.
Authentication URL	The URL Nessus Manager uses to access Centrify.
Password Engine URL	The name of a specified team in a multi-team environment.
Username	(Required) The username to log in to the hosts you want to scan.
Checkout Duration	The length of time, in minutes, that you want to keep credentials checked out in Centrify. Configure the Checkout Duration to exceed the typical duration of your Nessus Manager scans. If a password from a previous scan is still checked out when a new scan begins, the new scan fails. Note: Configure the password change interval in Centrify so that password changes do not disrupt your Nessus Manager scans. If Centrify changes a password during a scan, the scan fails.
Use SSL	If enabled, Nessus Manager uses SSL through IIS for secure communications. You must configure SSL through IIS in Centrify before enabling this option.
Verify SSL	If enabled, Nessus Manager validates the SSL certificate. You must con- figure SSL through IIS in Centrify before enabling this option.

11. Click Save. The credential saves and the My Scans page appears.

To verify the integration is working:

1. On the My Scans page, click Launch to initiate an on-demand scan.
2. Once the scan completes, select the completed scan and look for the following message - Microsoft Windows SMB Log In Possible: 10394. This result validates that authentication was suc- cessful.

Configuring Nessus for Centrify (SSH)

Perform the following steps to configure Nessus with Centrify PAS using SSH.

Requirements

• Nessus Manager account.
• Centrify PAS account.

• Required User Role: Standard, Administrator, or System administrator.

To integrate Nessus with Centrify Privileged Access Service using SSH credentials:

1. Log into Nessus Manager. Click Scans. The MyScans page appears.

2. Click + New Scan. The Scan Templates page appears:

3. Select a scan template. The selected scan template Settings page appears.

4. In the Name field, type a name for the scan.
5. In the Targets field, type an IP address, hostname, or range of IP addresses.
6. (Optional) Add a description, folder location, scanner location, and specify target groups.
7. Click the Credentials tab. The Credentials options appear. By default, the Categories drop-down box displays Host.
8. In the left menu, select SSH. The SSH settings appear.
9. In the SSH settings, click the Authentication method drop-down box. The Authentication method drop-down box options appear.

10. Select Centrify. The Centrify options appear.
11. Configure the SSH credentials.

Option	Default Value
Centrify Host	(Required) The Centrify IP address or DNS address. Note: If your Centrify installation is in a subdirectory, you must include the subdirectory path. For example, type IP address or hostname/sub- directory path.
Centrify Port	The port on which Centrify listens.
API User	(Required) The API user provided by Centrify
API Key	(Required) The API key provided by Centrify.
Tenant	The name of a specified team in a multi-team environment.
Authentication URL	The URL Nessus Manager uses to access Centrify.
Password Engine URL	The name of a specified team in a multi-team environment.
Username	(Required) The username to log in to the hosts you want to scan.
Checkout Duration	The length of time, in minutes, that you want to keep credentials checked out in Centrify. Configure the Checkout Duration to exceed the typical duration of your Nessus Manager scans. If a password from a previous scan is still checked out when a new scan begins, the new scan fails. Note: Configure the password change interval in Centrify so that password changes do not disrupt your Nessus Manager scans. If Centrify changes a password during a scan, the scan fails.
Use SSL	If enabled, Nessus Manager uses SSL through IIS for secure communications. You must configure SSL through IIS in Centrify before enabling this option.
Verify SSL	If enabled, Nessus Manager validates the SSL certificate. You must con- figure SSL through IIS in Centrify before enabling this option.

12. Click Save.

To verify the integration is working:

1. On the My Scans page, click Launch to initiate an on-demand scan.
2. Once the scan completes, select the completed scan and look for Plugin ID 97993 and the cor- responding message - It was possible to log into the remote host via SSH using 'password' authentication. This result validates that authentication was successful.