|
|
Name of Your Organization:
eEye Digital Security
Web Site:
http://www.eeye.com/
Compatible Capability:
Retina® Network Security Scanner
Capability home page:
http://www.eeye.com/retina
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):
Information stored in Retina® is available to users of the product during scanning, reporting and remediation; and for lookup directly from the auditing screen.
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):
Each audit file carries the database version number. The version number is also displayed in the product about box.
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):
eEye has a dedicated research team that maintains the audits database. Within a few hours of vulnerability announcement Retina® audits will be updated; CVE versions are updated with each of our 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):
eEye Digital Security releases updates on a daily basis as vulnerabilities are discovered, we update our audits. Changes to the CVE database are updated in the same manner.
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):
CVE information is located in the product help-file under the headings Features->CVE Support, Retina Audit Wizard->Tracking Info, and Retina Audits Search.
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):
Specific instructions are in the Modifying Audit Groups section of the user manual, though, related CVE names are always shown when viewing audits.
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):
Related CVE names, with links to the CVE, are always displayed with individual security elements within our database.
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):
CVE information is located in the product help-file under the headings Features->CVE Support, Retina Audit Wizard->Tracking Info, and Retina Audits Search.
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):
The CAN- prefix is used for all candidates to differentiate them from CVE entries that have the CVE- prefix.
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):
The CVE name links directly back to the CVE online database and the Candidate information is displayed at the top of the page.
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):
We are subscribed to the CVE mailing list and update CAN/CVE listings regularly. Customers aren't specifically told as they will automatically see the new reference and be linked to the correct definition.
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):
Within the product there is a section called "Audits" from that window, the customer just enters the number portion of the name in the "Look For" box and we'll find either one.
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):
CVE candidates are supported as described in number 14.
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 CVE database number is in the "About" box for the software and the candidate information links directly back to the CVE list at Mitre.
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):
Within the product the customer selects the Audit tab and then the Audits sub-tab (or Menu->Tools->Audit Groups). At that point the customer will be presented with this screen:
The customer then types in the YYYY-NNNN portion of the name and will see the above results. From there the customer sees the category (ours), the Description of the vulnerability, our estimated risk, instructions on fixing it, links to the patch or vendor and links to both the CVE and BugTraq entries.
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 (if available) name is listed in the report for any vulnerability found on a machine. An excerpt from a remediation report is below.
Internet Explorer 6 SP1 Cumulative Patch 818529
Category:
Miscellaneous
Description:
Two critical vulnerabilities were discovered in Internet Explorer 6 SP1 and earlier that could allow an attacker to execute arbitrary code upon a victim's machine through malicious HTML. The first is a buffer overflow resulting from a specially-crafted
Risk Level:
High
How To Fix:
Install the appropriate Microsoft hotfix.
Related Links:
eEye Digital Security Advisory on Object Tag Type Bug
- http://www.eeye.com/html/research/advisories/
Microsoft Knowledge Base Article Q818529
- http://support.microsoft.com/default.aspx?scid=kb;en-us;Q818529
Microsoft Security Bulletin MS03-020
- http://www.microsoft.com/technet/security/bulletin/MS03-020.aspCVE:
CAN-2003-0344
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0344, CAN-2003-0309
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0309Affected Machines:
IP Address
Machine Name
OS
192.168.002.025
WKS003
Windows XP, Service Pack 1
19) 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 product the customer selects the Audit tab and then the Audits sub-tab (or Menu->Tools->Audit Groups). And then select the CVE sub-tab. The customer will see this screen with all available CVE names and their descriptions:
Alternatively, the customer could follow the steps in 17 and enter the problem, such as DCOM and would be presented with a list of audits, each one containing the CVE name and link in addition to the other required information. As below:
20) 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):
As in 19 above, the customer can select the desired tasks from the list of CVE names or search for each required CVE name and select the associated task from there (17).
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):
Follow the steps in 19 and select/deselect the desired CVE tasks.
22) 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):
As a scanner, the task is an audit, which is always performed. If access to perform an audit is not available, the user is notified in the product scan log. Otherwise the scan is performed and the user is notified of any problems.
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):
There is not a separate document for CVE-related text. The CVE names and links are available in all tasks and reports. In addition, there is a complete list (see figure in 19) of the CVE names and descriptions in the product. The audit file used by the product is either an Access database (4.x) or an XML file (5.x) that can also be searched with a text 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):
CVE names are listed for each element in the interface and reports as shown in 17, 18, and 19. An individual audit (see 19) is shown here:
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):
The CVE names and links are available in all tasks and reports. See 19 and 32.
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):
Within the product the customer selects the Audit tab and then the Audits sub-tab (or Menu->Tools->Audit Groups). At that point the customer will be presented with this screen:
The customer then types in the YYYY-NNNN portion of the name and will see the above results. From there the customer sees the category (ours), the Description of the vulnerability, our estimated risk, instructions on fixing it, links to the patch or vendor and links to both the CVE and BugTraq entries.
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):
In all reports and audits the customer will see the Description of the vulnerability, our estimated risk, instructions on fixing it, links to the patch or vendor and links to both the CVE and BugTraq entries.
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):
There is not a separate document for exporting CVE-related data. This information is linked within each security element. However, the audit database is either an Access database or an XML file, both of which have many available tools for searching.
37) 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: Robert S. Stull
Title: Retina Product Manager
38) 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: Robert S. Stull
Title: Retina Product Manager
39) 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: Robert S. Stull
Title: Retina Product Manager