Name of Your Organization:

SAINT Corporation

Web Site:

http://www.saintcorporation.com

Compatible Capability:

Security Administrator's Integrated Network Tool (SAINT)

Capability home page:

http://www.saintcorporation.com/products/software/saintScanner.html

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):

SAINT customers can find CVE information in SAINT's Data Analysis reports, in SAINT's vulnerabilty tutorials, and in a SAINT/CVE cross-reference table which is included in the product and available on the web site.

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):

Mappings are usually updated at least once every two weeks if new Candidate CVEs or a new CVE version is available. New CAN and CVE lists are downloaded and compared with current lists, and new entries are added to the mapping if relevant to SAINT.

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):

The SAINT Corporation web site states that product updates are available every two weeks. These updates include CVE updates.

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):

The SAINT Corporation web site states that product updates are available every two weeks. These updates include CVE updates.

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):

See the SAINT FAQ, which is included with the product and is also available on our web site.

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):

Please see our website

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):

Please see our website

11) Candidates Versus Entries Indication <CR_6.1>

If CVE candidates are supported or used, explain how you indicate that candidates are not accepted CVE entries (required):

Candidates are indicated by "CAN".

12) Candidates Versus Entries Explanation <CR_6.2>

If CVE candidates are supported or used, explain where and how the difference between candidates and entries is explained to your customers (recommended):

It is explained that Candidates are potential CVE entries but have not yet been approved, in the SAINT/CVE cross-reference list. http://www.saintcorporation.com/cgi-bin/doc.pl?document=cve

13) Candidate to Entry Promotion <CR_6.3>

If CVE candidates are supported or used, explain your policy for changing candidates into entries within your capability and describe where and how this is communicated to your customers (recommended):

When candidates become approved in a new CVE version, they are moved from the "CAN" section of the cross-reference list to the "CVE" section, and references are changed from "CAN" to "CVE" in the report output and vulnerability tutorials. Additionally, the reference is changed from an orange font type to red in the tutorials to emphasize the promotion. New CVE versions are publicized on the "SAINT Updates" web page:
http://www.saintcorporation.com/updates.html

14) Candidate and Entry Search Support <CR_6.4>

If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's ability to look for candidates and entries by using just the YYYY-NNNN portion of the CVE names (recommended):

The SAINT/CVE cross-reference list includes CAN and CVE entries on the same page, so the browser's search function can search for both CVE and CAN entries if just the YYYY-NNNN portion is entered.

15) Search Support for Promoted Candidates <CR_6.5>

If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's support for retrieving the CVE entry for a candidate that is no longer a candidate (recommended):

Not applicable. A search in the form of YYYY-NNNN will retrieve both "CVE" and "CAN" entries.

16) Candidate Mapping Currency Indication <CR_6.6>

If CVE candidates are supported or used, explain where and how you tell your users how up-to-date your candidate information is (recommended):

The SAINT version release date found in the CHANGE log or at http://www.saintcorporation.com/updates.html indicates how up-to-date the software is. The candidate information is kept up-to-date with each release of the software.

Type-Specific Capability Questions

17) 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):

The SAINT/CVE cross-reference list includes a column which maps the CVE name to the associated SAINT probe. The explanation is included at the top of the cross-reference list.

For example, a user who searches the table for CVE-1999-0002 will discover that this vulnerability is detected by the rpc.saint probe.

18) 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):

The CVE name is listed beside every reported vulnerability. In SAINT's basic HTML reporting, each vulnerability appears beside a dot like this:

* [TOP-20] host1 - possible vulnerability in mountd (CVE-1999-0002)

In reports generated by SAINTwriter, there is a column in the table in the Technical Overview report for CVE numbers, and a CVE line under each vulnerability in the Technical Details report.

21) 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):

For each CVE name, the user would check the SAINT/CVE cross-reference list for the associated SAINT probe. The user would then create a custom scan level and select each of the associated SAINT probes.

31) 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):

We provide both HTML and PDF documentation, and scan output is available as HTML, text, or CSV. Any of these formats can be searched using a browser, reader, or editor.

32) 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):

SAINT categorizes vulnerabilities by their tutorial name. Tutorial names are cross-referenced with CVE names in the SAINT/CVE cross-reference table: http://www.saintcorporation.com/cgi-bin/doc.pl?document=cve

33) 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):

http://www.saintcorporation.com/cgi-bin/doc.pl?document=cve

34) 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):

A user can find SAINT's vulnerability categories by CVE name by visiting the SAINT/CVE cross-reference list in a browser, and using the browser's search function:
http://www.saintcorporation.com/cgi-bin/doc.pl?document=cve

Example:
To search SAINT's capability for scanning CVE-1999-0002, one would visit the cross-reference table in the browser, choose "search this page" (or some equivalent option), and the browser would return a line containing the CVE name, description, SAINT category, and SAINT probe.

35) 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):

There are three ways that CVE names are listed for security elements: in report output, in vulnerability tutorials, and in the SAINT/CVE cross-reference. The report output lists vulnerabilities in either tabular or paragraph format. The vulnerability tutorials discuss vulnerabilities in paragraphs, with related CVE names listed above paragraphs. The cross-reference page is in tabular format.

36) 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):

SAINTwriter provides output in HTML, text, or CSV format, with CVE names as one of the fields in the tables. Each of these formats can be searched using a browser or text editor. The CSV format can be exported to a database that also can be used for searching.