Organizations
An organization is a set of distinct users and groups and the resources (e.g., scanners, repositories, and LDAP servers) they have available to them.
The organization is managed primarily by the administrator users and security manager users. The administrator user creates the organization and creates, assigns, and maintains the security manager user account. The security manager user (or any organizational user with appropriate permissions) creates other users within the organization. Groups allow you to manage users and share permissions to resources and objects among the group. For more information, see User Access.
Multiple organizations can share the same repositories, and the vulnerability data associated with the overlapping ranges is shared between each organization. Conversely, organizations can be configured with their own discrete repositories to facilitate situations where data must be kept confidential between different organizational units.
Creation of an organization is a multi-step process. After you create an organization,
To view details for any organization, see View Organization Details.
Organization Options
Option | Description |
---|---|
General |
|
Name |
(Required) The organization name. |
Description |
A description for the organization. |
Contact Information |
The relevant contact information for the organization including address, city, state, country, and phone number. |
Scanning |
|
Distribution Method |
The scan distribution mode you want to use for this organization:
For more information about scan zones, see Scan Zones. |
Available Zones |
One or more scan zones that you want organizational users to have access to when configuring scans. |
Allow for Automatic Distribution |
Enable or disable this option to specify whether you want Tenable.sc to automatically select one or more scan zones if an organizational user does not specify a scan zone when configuring a scan.
|
Restrict to Selected Zones |
If Allow for Automatic Distribution is enabled, enable or disable this option to specify the zones you want Tenable.sc to choose from when automatically distributing zones.
|
Restricted Scan Ranges | The IP address ranges you do not want users in this organization to scan. |
Analysis |
|
Accessible LCEs |
The LCEs that you want this organization to have access to. You can search for the LCEs by name or scroll through the list. |
Accessible Repositories |
The repositories that you want this organization to have access to. You can search for the repositories by name or scroll through the list. |
Accessible Agent Capable Scanners |
The Nessus scanners (with Nessus Agents enabled) that you want this organization to have access to. Select one or more of the available scanners to allow the organization to import Nessus Agent results from the selected scanner. |
Accessible LDAP Servers |
The LDAP servers that you want this organization to have access to. An organization must have access to an LDAP server in order to perform LDAP authentication on user accounts within that organization, and to configure LDAP query assets. Note: If you revoke access to an LDAP server, users in the organization cannot authenticate and LDAP query assets cannot run. |
Custom Analysis Links |
|
A list of custom analysis links provided to users within the host vulnerability details when analyzing data outside of Tenable.sc is desired. Click Add Custom Link to create a new option to type the link name and URL to look up additional data external to Tenable.sc. For example: http://example.com/index.htm?ip=%ip% The %ip% reference is a variable that inserts the IP address of the current host into the specified URI. |
|
Vulnerability Weights |
|
Low |
The vulnerability weighting to apply to Low criticality vulnerabilities for scoring purposes. (Default: 1) |
Medium |
The vulnerability weighting to apply to Medium criticality vulnerabilities for scoring purposes. (Default: 3) |
High |
The vulnerability weighting to apply to High criticality vulnerabilities for scoring purposes. (Default: 10) |
Critical |
The vulnerability weighting to apply to Critical criticality vulnerabilities for scoring purposes. (Default: 40) |
Vulnerability Scoring System | |
Scoring System |
The scoring system Note: Changing the Scoring System while Note: Changing the Scoring System does not impact historical dashboard trend data. For example, if you change the Scoring System from CVSS v2 to CVSS v3, dashboard trend data prior to the change displays CVSS v2 scores and dashboard trend data after the change displays CVSS v3 scores.
|