Name of Your Organization:

Tenable Network Security Inc.

Web Site:

www.tenablesecurity.com

Compatible Capability:

Passive Vulnerability Scanner

Capability home page:

http://www.tenablesecurity.com/products/pvs/

1) Product Accessibility <CR_2.4>

Provide a short description of how and where your capability is made available to your customers and the public (required):

Tenable's Security Center uses CVE identifiers for referencing vulnerabilities used by the Nessus vulnerability scanner and the Passive Vulnerability Scanner. Users of the Security Center can research vulnerabilities based on CVE name, reference them in vulnerability output and server vulnerability results based on CVE entry.

4) Map Currency Indication <CR_5.1>

Describe how and where your capability indicates the most recent CVE version used to create or update its mappings (required):

Tenable synchronizes CVE entries with National Vulnerability Database information daily. If new, missing or corrected CVE entries exist, we modify our content accordingly.

5) Map Currency Update Approach <CR_5.2>

Indicate how often you plan on updating the mappings to reflect new CVE versions and describe your approach to keeping reasonably current with CVE versions when mapping them to your repository (recommended):

Tenable synchronizes CVE entries with National Vulnerability Database information daily. If new, missing or corrected CVE entries exist, we modify our content accordingly.

6) Map Currency Update Time <CR_5.3>

Describe how and where you explain to your customers the timeframe they should expect an update of your capability's mappings to reflect a newly released CVE version (recommended):

Tenable describes our CVE usage, along with other standards, in a document available on our support site entitled "Standards Declarations". This document details how we update CVE, CVSS, XCCDF and many other standards.

7) CVE and Compatibility Documentation<CR_4.1>

Provide a copy, or directions to its location, of where your documentation describes CVE and CVE compatibility for your customers (required):

Tenable describes our CVE usage, along with other standards, in a document available on our support site entitled "Standards Declarations". This document details how we update CVE, CVSS, XCCDF and many other standards.

8) Documentation of Finding Elements Using CVE Names <CR_4.2>

Provide a copy, or directions to its location, of where your documentation describes the specific details of how your customers can use CVE names to find the individual security elements within your capability's repository (required):

Tenable describes our CVE usage, along with other standards, in a document available on our support site entitled "Standards Declarations". This document details how we update CVE, CVSS, XCCDF and many other standards and also how CVE can be used to search for specific vulnerabilities.

9) Documentation of Finding CVE Names Using Elements <CR_4.3>

Provide a copy, or directions to its location, of where your documentation describes the process a user would follow to find the CVE names associated with individual security elements within your capability's repository (required):

Tenable describes our CVE usage, along with other standards, in a document available on our support site entitled "Standards Declarations". This document details how we update CVE, CVSS, XCCDF and many other standards and also how CVE can be used to search for specific vulnerabilities.

10) Documentation Indexing of CVE-Related Material <CR_4.4>

If your documentation includes an index, provide a copy of the items and resources that you have listed under "CVE" in your index. Alternately, provide directions to where these "CVE" items are posted on your web site (recommended):

Current Tenable documentation does not have an index entry for CVE. CVE is also not mentioned on the current website except for search Nessus plugins. This link is available by visiting nessus.org, clicking on 'plugins', and then choosing a search engine. One of the search criteria is to look for vulnerabilities based on CVE name.

Type-Specific Capability Questions

11) Finding Tasks Using CVE Names <CR_A.2.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CVE name (required):

Tenable Network Security uses Common Vulnerability Enumeration nomenclature for many different processes accomplished by the Security Center.

• All vulnerabilities identified by Tenable's research group for the Nessus vulnerability scanner or the Passive Vulnerability Scanner have relevant CVE entries.
• At Nessus.org, Tenable publishes our total count of covered CVE entries as well as a public web interface that can be used to search CVE entries.
• Within the Security Center, for any vulnerability displayed in "full detail" mode, all relevant CVE links are listed and the user can click on them to have direct information displayed in the web browser from the online CVE content. This data is also displayed in the reporting and exporting via CSV content.
• Within the Security Center, the text of any CVE value can be used as a search. For example, one could enter in "CVE-2002" and would be presented with all matching vulnerabilities which had a CVE entry from the year 2002. Specific CVE entries can be used as well.
• When browsing vulnerability descriptions within the Security Center, CVE entries are also indicated.
• For vulnerability to IDS event correlation, the Security Center employs CVE as one of the correlation matrices, such that an IDS event from a non-Tenable vendor could be correlated with all discovered vulnerabilities that have the same CVE entry.

12) Finding CVE Names Using Elements in Reports <CR_A.2.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the tool allows the user to determine the associated CVE names for the individual security elements in the report (required):

When creating a PDF report that contains vulnerability information, if the "raw vulnerability detail" chapter is enabled, it will contain CVE entries, if one or more CVE entries are available for the vulnerability in question. This can be seen in the below screen shot:

13) Getting a List of CVE Names Associated with Tasks <CR_A.2.4>

Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the tool's tasks (recommended):

• Within the Security Center, CVE identifiers can be used to search existing PVS and Nessus plugins to see if a check exists for a desired CVE entry.
• After a scan, when viewing vulnerability details, all associated CVE entries are displayed.
• CVE identifiers can be used as a filter such that only vulnerabilities related to a certain CVE will be shown.

14) Selecting Tasks with a List of CVE Names <CR_A.2.5>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):

• For each CVE, within a vulnerability policy, a user would search all available plugins for relevant CVE entries and then enable the plugins (tasks) that they desired to be included in their audit.
• This process would be repeated iteratively, each time adding more enabled plugins to the list.

15) Selecting Tasks Using Individual CVE Names <CR_A.2.6>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CVE names (recommended):

A user would simply search for a list of plugins (there may be more than one) and then create a vulnerability policy that enabled just that (or those) plugins.

16) Non-Support Notification for a Requested CVE Name <CR_A.2.7>

Provide a description of how the tool notifies the user that task associated to a selected CVE name cannot be performed (recommended):

The Security Center, Nessus and the PVS include a variety of diagnostic methods to figure out if and why a scan did not complete its audit. For example, if a CVE task required credentials to perform a patch audit, but those credentials were not supplied, an error is shown in the scan results.

20) Finding Online Capability Tasks Using CVE Names <CR_A.4.1>

Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CVE name or through an online mapping that links each element of the capability with its associated CVE name(s) (required):

• At nessus.org, there is a plugins search tool which can use CVE to search for relevant plugins.
• The PVS has a PDF document produced hourly which lists all plugins, including CVE entries. These can be used for searching within the document.

23) Finding CVE Names Using Online Capability Elements <CR_A.4.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CVE names for the individual security elements in the report. (required):

All reports and vulnerability details include any relevant CVE data, so an online mapping function of Nessus or PVS plugins to CVE entries is not required.

25) Finding Elements Using CVE Names <CR_A.5.1>

Give detailed examples and explanations of how a user can associated elements in the capability by looking for their associated CVE name (required):

Within the Security Center, the text of any CVE value can be used as a search. For example, one could enter in "CVE-2002" and would be presented with all matching vulnerabilities which had a CVE entry from the year 2002. Specific CVE entries can be used as well.

26) Finding CVE Names Using Elements in Reports <CR_A.5.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the capability allows the user to determine the associated CVE names for the individual security elements in the report (required):

In 12) an example PDF report is shown which indicates relevant CVE entries. CVE identifiers can be used as strings to search a report.

27) Getting a List of CVE Names Associated with Tasks <CR_A.5.4>

Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the capability's tasks (recommended):

The Security Center includes a description for each task. If this task also references one or more CVEs, it will be indicated. This data can be displayed by searching the vulnerability database, or linking to it when analyzing actual discovered vulnerabilities.

28) Selecting Tasks with a List of CVE Names <CR_A.5.5>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):

Please see 14)

29) Selecting Tasks Using Individual CVE Names <CR_A.5.6>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the capability by using individual CVE names (recommended):

Please see 15)

30) Electronic Document Format Info <CR_B.3.1>

Provide details about the different electronic document formats that you provide and describe how they can be searched for specific CVE-related text (required):

• Security Center reports which include vulnerability detail will have CVE entries in them. This allows users to search within a PDF file for relevant CVE data.
• If data in the Security Center's user interface includes CVE data (for example, when listing vulnerability detail information, but not when summarizing open port information), CVE information will also be included in the comma separate variable (CSV) file.

31) Electronic Document Listing of CVE Names <CR_B.3.2>

If one of the capability's standard electronic documents only lists security elements by their short names or titles provide example documents that demonstrate how the associated CVE names are listed for each individual security element (required):

Please see 12) which includes a screen shot of the report that references CVE data for each unique element.

32) Electronic Document Element to CVE Name Mapping <CR_B.3.3>

Provide example documents that demonstrate the mapping from the capability's individual elements to the respective CVE name(s) (recommended):

N/A. The Security Center does not readily provide a global mapping of CVE to tasks.

33) Finding Elements Using CVE Names Through the GUI <CR_B.4.1>

Give detailed examples and explanations of how the GUI provides a "find" or "search" function for the user to identify your capability's elements by looking for their associated CVE name(s) (required):

1. For any detected vulnerability, if there is one or more CVE entries associated with it, they will be listed in the vulnerability detail view. To test this, view either the raw scan results or the cumulative database results and select raw detail. The CVE entries will be listed as in the screen shot below. The "raw detail" view is enabled by clicking on the icon in the upper right that looks like a paper with the magnifying glass in it.
2. Vulnerabilities with CVE entries can also be queried by selecting the "Vuln Filters" and then entering the specific CVE string (or partial string) into the "Search Vuln Text" box.
3. CVE data is viewable in raw CVS spreadsheet exports from the cumulative view as well.
4. In raw PDF reports, if the "vulnerability details" chapter is enabled, CVE data will also be present.

Below is a screen shot of viewing raw vulnerability information with CVE relevant information:

Below is another screen shot of the Security Center using a text field to filter matching events with specific CVE entries:

34) GUI Element to CVE Name Mapping <CR_B.4.2>

Briefly describe how the associated CVE names are listed for the individual security elements or discuss how the user can use the mapping between CVE entries and the capability's elements, also describe the format of the mapping (required):

All Nessus and Passive Vulnerability Scanner plugins receive mappings to CVE, Bugtraq and other identifiers. Although not exposed to end users, the full mapping of plugin IDs to CVE entries is listed in a directory named /opt/sc3/admin/plugins. Within the GUI, all users can search existing plugins for CVE names, including performing searches for items like "CVE-2008" which would list all CVE entries available in 2008.

Also below is a screen shot of example CVE data being listed in an available vulnerability check:

35) GUI Export Electronic Document Format Info <CR_B.4.3>

Provide details about the different electronic document formats that you provide for exporting or accessing CVE-related data and describe how they can be searched for specific CVE-related text (recommended):

The Security Center exports data three ways:

1. Within the SC3 GUI, any set of data (port summaries, vuln details, lists of IP addresses, list of vulnerabilities, .etc) can be exported via CSV. When exporting the data with all vulnerability detail, the column of "raw data" includes any CVE mappings. Spreadsheet tools such as Excel can search elements for various CVE patterns.
2. For PDF reports produced by SC3, if the "raw vulnerability chapter" is included, it will list any associated CVE mappings.
3. SC3 can also export vulnerability data in the .nessus format. When loaded into the Nessus Client, specific CVE entries can be searched for by looking for CVE strings within the data results.

36) Statement of Compatibility <CR_2.7>

Have an authorized individual sign and date the following Compatibility Statement (required):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CVE Compatibility Requirements as well as all of the additional mandatory CVE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Ron Gula

Title: CEO, Tenable Network Security

37) Statement of Accuracy <CR_3.4>

Have an authorized individual sign and date the following accuracy Statement (recommended):

"As an authorized representative of my organization and to the best of my knowledge, there are no errors in the mapping between our capability's Repository and the CVE entries our capability identifies."

Name: Ron Gula

Title: CEO, Tenable Network Security

38) Statement on False-Positives and False-Negatives <CR_A.2.8 and/or CR_A.3.5>

FOR TOOLS ONLY - Have an authorized individual sign and date the following statement about your tools efficiency in identification of security elements (required):

"As an authorized representative of my organization and to the best of my knowledge, normally when our capability reports a specific security element, it is generally correct and normally when an event occurs that is related to a specific security element our capability generally reports it."

Name: Ron Gula

Title: CEO, Tenable Network Security