Tenable.sc Director Deployments

You can use Tenable.sc Director to monitor Nessus scanners, scan zones, and scan results on multiple Tenable.sc instances. If your deployment includes several instances of Tenable.sc, Tenable recommends using Tenable.sc Director to remotely monitor your Tenable.sc instances.

A Tenable.sc Director deployment includes:

  • One Tenable.sc Director where you connect managed Tenable.sc instances. You use Tenable.sc Director to centralize and monitor data collected by your managed Tenable.sc instances.

  • Tenable.sc Director cannot perform scans. Plan your deployment to ensure you have adequate scan coverage on the Tenable.sc instances you plan to monitor from Tenable.sc Director.

  • One or more managed Tenable.sc instances. You connect managed Tenable.sc instances to collect vulnerability data that can be viewed in Tenable.sc Director.

    Note: You must run the same version of Tenable.sc on your entire Tenable.sc Director deployment, including Tenable.sc Director and all managed Tenable.sc instances that you connect to Tenable.sc Director. Tenable.sc Director cannot communicate with managed Tenable.sc instances that are running a different version of Tenable.sc.

To plan and fully configure your Tenable.sc Director deployment, see Get Started With Tenable.sc Director.

For more information, see:

Monitor Your Tenable.sc Director Deployment

After you acquire a Tenable.sc Director license, configure Tenable.sc Director, and connect one or more managed Tenable.sc instances, you can monitor the following details from Tenable.sc Director:

  • The status, version, and total number of Nessus Scanners running on each managed Tenable.sc instance
  • The Scan Zones configured on each managed Tenable.sc instance
  • The scan results of scans run on each managed Tenable.sc instance
  • A summary of plugin sets used on each managed Tenable.sc instance
  • A summary of plugin sets used by Nessus scanners on each managed Tenable.sc instance
  • The version of Tenable.sc running on each managed Tenable.sc instance

From Tenable.sc Director, you can pause, resume, and stop scans that are running on managed Tenable.sc instances. For more information, see Pause, Resume, or Stop Scans on a Managed Tenable.sc Instance.

Note: You cannot edit configurations on managed Tenable.sc instances from Tenable.sc Director. To manage Nessus scanners, scan zones, scan results, and other configurations on a managed Tenable.sc instance, log in to that instance.

Note: You cannot download Nessus scanner logs on managed Tenable.sc instances from Tenable.sc Director. To download Nessus scanner logs on a managed Tenable.sc instance, log in to that instance.

Tip: Managed Tenable.sc instances cannot share repository data. For more information about sharing repository data between Tenable.sc instances, see Tiered Remote Repositories.