Name of Your Organization:
SAINT Corporation
Web Site:
Adopting Capability:
SAINT Security Suite
Capability home page:
http://www.saintcorporation.com/products/saint-security-suite/
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 Security Suite's Scan Policy page under the Scan tab; Analysis tab; Tutorials and Reports.
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):
The SAINT/CVE cross-reference table included in the product and the Customer "mySAINT" portal states the CVE version number with which SAINT products are compatible.
Map Currency Update Approach <CR_5.2>
Indicate how often you plan on updating the mappings to reflect the current CVE content and describe your approach to keeping reasonably current with the CVE content when mapping them to your repository (required):
Mappings are updated twice every week if new CVEs are available. New CVE lists are downloaded and compared with current lists, and new entries are added to the mapping if relevant to SAINT Security Suite.
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 newly available CVE content (required):
The SAINT Corporation website, user guide and knowledgebase articles state that product updates are available twice a week. These updates include CVE updates.
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 User Guide, which is included with the product is also available on the website at http://www.saintcorporation.com/resources/documentation/help/saint8_help/saint_help.html
See Glossary of Terms.
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):
http://www.saintcorporation.com/resources/documentation/help/saint8_help/saint_help.html
See User Guide - Using SAINT - Scan Policies, Analysis, Tutorials and Reporting sections.
See Glossary of Terms.
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):
http://www.saintcorporation.com/resources/documentation/help/saint8_help/saint_help.html
See User Guide - Using SAINT - Scan Policies, Analysis, Tutorials and Reporting sections.
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):
Login to the Customer portal - mySAINT - at https://my.saintcorporation.com/cgi-bin/secure/customer/logon.pl
Click on Vulnerabilities link under Vulns and Exploits section.
CVEs are organized by calendar year. Scroll alphabetically down to CVE.
Type-Specific Capability Questions
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 Scan Policies page under the Scan Tab provides a data grid that includes a column which maps the CVE name to the associated SAINT vulnerability check ID. The explanation is included in the User Guide, under the Scan tab - Scan Policies.
For example, a user who searches the grid for CVE-2014-1776 will discover that this Internet Explorer Remote Code Execution vulnerability is detected by the win_patch_ie_kb2963983 check.
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 Security Suite's basic HTML reporting, each vulnerability appears beside a dot like this:
* [TOP-20] host1 - possible vulnerability in mountd (CVE-1999-0002)
In reports, 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.
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):
On the Information (i) page in the Scan Policy data grid, every vulnerability check is hyperlinked to an information page which includes a list of related CVE entries.
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):
On the Scan Policy page, the user would search, check or uncheck CVEs listed for an associated scan policy. The user would then create a custom scan policy to be used in executing a scan job.
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, CSV, PDF, or XML. Any of these formats can be searched using a browser, reader or editor.
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 Security Suite internally identifies vulnerabilities by their vulnerability check IDs.
These IDs are cross-referenced with CVE names in the SAINT/CVE cross-reference table.
See Glossary of Terms.
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/resources/documentation/help/saint8_help/saint_help.html
See Scan tab - Scan Policies.
See Analyze tab - All Scan Results.
See Analyze tab - Vulnerability DB.
See Reports tab.
See Glossary of Terms.
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 Security Suite's vulnerability categories by CVE name by:
- User logs into the software and selects the Scan tab - Scan Policies submenu.
- Page refreshes to show all vulnerability checks mapped to their CVE.
If default doesn't display CVE column, it can be added quickly through Column selector.
Each data grid provides support column search - including by CVE.
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: 1) In report output, 2) in vulnerability tutorials, and 3) in the Scan Policy VulnID to CVE mapping. 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 Scan Policy page is in tabular format.
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):
SAINT reporting provides output in HTML, text, CSV, PDF, or XML 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 and XML formats can be exported to a database that also can be used for searching.
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: Randall Laudermilk
Title: Director, Product Management
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: Randall Laudermilk
Title: Director, Product Management
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: Randall Laudermilk
Title: Director, Product Management
