Tenable.sc Director Deployments
You can use Tenable.sc Director to
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.
-
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.
Tenable.sc Director cannot perform scans. Plan your deployment to ensure you have adequate scan coverage on the Tenable.sc instances you plan to
To plan and fully configure your Tenable.sc Director deployment, see Get Started With Tenable.sc Director.
For more information, see:
- Connect a Managed Tenable.sc Instance
- Manage Your Tenable.sc Instances
- Managed Tenable.sc Instance Settings
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
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.