---
title: "Nessus integration"
description: "Connect Guardian to Nessus so a node scan can trigger a Nessus scan."
product: "Guardian"
edition: "Classic"
type: "workflow"
url: "https://docs.cloudhouse.com/guardian/classic/control/integrations/nessus-integration/"
---
# Nessus integration

A Nessus integration with Guardian allows you to trigger a Nessus scan after a 'Node Scanned' event to obtain a complete picture of the node's state at that point in time. Once the Nessus scan is complete, you can then view the results directly in Guardian.

Applies to: `Guardian Classic`

!!! note

    This topic focuses on setting up the Nessus integration. If you've already set up the integration and want to configure Nessus actions, see [Action: Launch a Nessus Scan](https://docs.cloudhouse.com/guardian/classic/control/events/actions/nessus-scan/index.md).

## Dependencies

To add a Nessus integration, you need the following:

- A Nessus Pro appliance.
- A standard Nessus user account – This could be an existing user account, but we recommend setting up a brand new user account named 'Guardian' for easier identification.

## Add a Nessus integration

Integrating Nessus with Guardian establishes a seamless connection to trigger a Nessus scan after a 'Node Scanned' event.

To add a Nessus integration to Guardian, complete the following:

1. In the Guardian web application, navigate to the **Integrations** tab (**Control** > **Integrations**) and click **Add Integration**. The **Add Integration** page is displayed.

    ![Addinteg](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/integrations/addinteg.png)

2. Select **Nessus** from the list of available integrations. Here, you are required to complete the following options:

    ![Nessus integration](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/integrations/nessus-integration.png)

    **Name** field
    :   The display name for the integration within Guardian. This name is how you will identify the integration among all others configured in your Guardian instance, so ensure it is descriptive.

**Nessus Instance URL** field
:   The URL of the default Nessus instance that will initiate scans. For example,`https://<NessusIP>:8834/api`.

**Username** field
:   The username of the Nessus account that will initiate the scans.

**Password** field
:   The password for the corresponding Nessus user account.

**Bypass Certificate Validation (not recommended)** checkbox
:   Option to ignore the SSL certificate check on your Nessus instance. If selected, Guardian will not consider the SSL certificate that encrypts web traffic to keep user data secure. This is not recommended unless required for troubleshooting.

**SecurityCenter Instance** checkbox
:   Option to indicate that the Nessus instance is a SecurityCenter appliance. If selected, Guardian will connect to the SecurityCenter, instead of the Nessus Pro appliance.

**Enable Verbose Logging (not recommended)** checkbox
:   Option to enable verbose integration logging. If selected, Guardian will collect extra information for troubleshooting purposes. This is not recommended unless required for troubleshooting.

3. Once you have set the correct values for each of the options displayed, click **Done** to create the Nessus integration.

If successful, a confirmation message is displayed and the Nessus integration is added to the **Integrations**tab of yourGuardian instance. If unsuccessful, an error message is displayed. Use the information displayed in the error message(s) to troubleshoot the values in your **Nessus Integration** options.

## Troubleshooting

If you are experiencing issues with your integration, try the following:

- Verify that the account credentials supplied for the integration are correct.
- To confirm the status of the integration sync, check the integration sync event in the **Events** tab (**Control** > **Events**) of your Guardian instance. For more information, see [Events](https://docs.cloudhouse.com/guardian/classic/control/events/events/index.md).