Get Started With Tenable.sc Director
Use the following getting started sequence to configure and mature your Tenable.sc Director deployment. A fully configured Tenable.sc Director deployment includes one Tenable.sc Director and one or more managed Tenable.sc instances. For more information, see Tenable.sc Director Deployments.
Before you begin, learn about Tenable.sc and Tenable.sc Director, then establish a deployment plan and analysis workflow to guide your configurations.
-
Design a deployment plan by identifying your organization's objectives and analyzing your network topology. Consider Tenable-recommended best practices for your environment.
Tenable.sc Director cannot perform scans. Plan your deployment to ensure you have adequate scan coverage on the Tenable.sc instances you plan to manage from Tenable.sc Director. -
Design an analysis workflow. Identify key stakeholders in your management and operational groups, considering the data you intend to share with each stakeholder.
For more information about planning a large enterprise deployment of Tenable.sc, see the Tenable.sc Large Enterprise Deployment Guide.
Configure Managed Tenable.sc Instances
Configure the Tenable.sc instances you want to manage with Tenable.sc Director.
-
Install and fully configure Tenable.sc on your managed Tenable.sc instances, as described in Get Started With Tenable.sc in the Tenable.sc User Guide.
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 ensure that your Tenable.sc instances can connect to Tenable.sc Director, apply the required license upgrade to each managed Tenable.sc instance, as described in Update an Existing License in the Tenable.sc User Guide.
-
Generate API keys for an administrator on each managed Tenable.sc instance, as described in Generate API Keys in the Tenable.sc User Guide.
Install Tenable.sc Director and perform initial configuration.
Note: You cannot upgrade Tenable.sc to Tenable.sc Director. If you want to install Tenable.sc Director on a host where Tenable.sc is already installed, you must uninstall Tenable.sc and perform a clean installation of Tenable.sc Director on that host. For more information, see Uninstall Tenable.sc.
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.
-
Prepare for the installation, as described in Before You Install.
-
Install Tenable.sc Director, as described in Install Tenable.sc Director.
-
Perform quick setup, as described in Quick Setup. You can:
-
Apply activation codes for Nessus, NNM, and LCE to allow Tenable.sc Director to perform plugin updates
-
Connect Tenable.sc instances you want to manage with Tenable.sc Director
-
Create one organization
-
Create one administrator user account and one security manager account
-
Configure usage statistic collection
Tenable recommends following the quick setup wizard, but you can configure these features later. For example, do not configure LDAP until you have easy access to all necessary LDAP parameters.
-
-
Configure SMTP settings, as described in Mail Settings.
-
Configure remote repositories, if necessary, as described in Repositories.
-
Configure security settings (e.g., password complexity requirements and custom banners), as described in Security Settings.
-
Configure and connect additional managed Tenable.sc instances, if necessary, as described in Connect a Managed Tenable.sc Instance.
On your managed Tenable.sc instances, configure and run basic scans, as described in Getting Started with Tenable.sc in the Tenable.sc User Guide.
In Tenable.sc Director, monitor running scans and scan results to begin evaluating the effectiveness of your deployment plan and analysis workflow.
-
Monitor running scans and scanner availability using the Insights Dashboard.
-
When the scans complete, create template-based dashboards and reports, as described in Dashboards and Reports.
Tenable recommends frequently reviewing your scan results and scan coverage. You may need to modify your scan configurations to suit your organization's objectives and reach all areas of your network.
Tip: You can manage scan policy configurations for active scans on your managed Tenable.sc instances from Tenable.sc Director using the Tenable.sc Director API. For more information, see the Tenable.sc API Guide.
Configure other features in Tenable.sc Director, if necessary, and refine your existing configurations.
-
Configure audit files, as described in Audit Files.
-
Configure groups, as described in Add a Group.
-
Create a custom user role, as described in Create a User Role.
-
Create additional user accounts and share objects with users, as described in User Accounts.
-
Create dynamic assets and combination assets, as described in Add a Custom Asset. For more information about asset types, see Assets.
-
Review the plugin update schedule, as described in Edit Plugin and Feed Settings and Schedules. Consider editing the schedules to suit your needs. For example, you may want to schedule plugin and feed updates to run a few hours before your scheduled scans.
-
Add queries and use filters, as described in Add or Save a Query and Apply a Filter.
-
Create custom dashboards and reports, as described in Dashboards and Reports.
-
Configure alerts and ticketing, as described in Workflow Actions.
-
View vulnerability data and use the built-in analysis tools, as described in Vulnerability Analysis.
Review and mature your deployment plan and analysis workflow.
-
Conduct weekly meetings to review your organization's responses to identified vulnerabilities.
-
Conduct weekly management meetings to oversee your teams executing the analysis workflow.
-
Review scan automation settings on your managed Tenable.sc instances and consider revising.
-
Review your scan results and scan coverage. You may need to modify your scan configurations on your managed Tenable.sc instances to suit your organization's objectives and reach all areas of your network.
-
Optimize and operationalize your custom dashboards to meet the needs of individual user account holders.
-
Optimize and operationalize your custom reports to prepare them for distribution.
-
Consider configuring API integrations, as described in the Tenable.sc API Guide and the Tenable.sc API Best Practices Guide.