|
|
Name of Your Organization:
Venus Information Technology Inc.
Web Site:
http://www.venustech.com.cn
Compatible Capability:
Cybervision Vulnerability Assessment and Management System
Capability home page:
http://www.venustech.com.cn/products
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):
Our Vulnerability Scanner System, Policy Editor, Security Information Guider, and Vulnerability Analysis Report modules provide CVE compatibility. These modules provide the user CVE-related information in detail.
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):
For each CVE name, our Vulnerability Scanner System has a hyperlink to the respective CVE page which provides a version number on the top of the vulnerability description. Our DB update application updates Vulnerability Scanner Knowledge Base fortnightly. If we find new important vulnerability, we will update Vulnerability Scanner Knowledge Base as soon as possible.
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):
When a new CVE version is released, all new entries will be added to the web site within two weeks. Old candidates will be removed.
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):
We provide CVE description information in CVE COMPATIBILITY in User Guide.
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):
We cite the Event Search of the Security Information Guider part of our user document hereinafter:
:
:
CVE-2001-0333
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):
We cite the Event Viewing of the Security Information Guider part of our user guide hereinafter:
:
:
,
,
,
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 which have the CVE- prefix.
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 user can attain this goal according to the following steps:
- Select "Select View->Show all" from Vulnerability Scanner System Console. The "Show all" window will be displayed as illustrated
- Select "Help->Event Help" from Vulnerability Scanner System Console. The "Event Help" window will be displayed as illustrated.
- Type the CVE number in the "Contents" edit box as illustrated, and select "Search Content", then click the "Search "button, all the available information will be showed as following:
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 user can attain this goal according to the following steps:
- Select "Select View->Show all" from Vulnerability Scanner System Console. The "Show all" window will be displayed as illustrated:
- Select "Help->Event Help" from Vulnerability Scanner System. The "Security Information Guider" window will be displayed as illustrated.
- Type the CVE number in the "Contents" edit box as illustrated, and select "Search Content" , then click the "Search" button, all the available information will be showed as following:
- Click the hyperlink above the CVE NAME item, the CVE page with the respective CVE name will be opened, which includes the description and reference material of the vulnerability.
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):
The documents we provide are in CHM format, which includes hyperlink to the CVE web page correspond to the current selected vulnerability.
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):
Some of the mapping information between the CVE_ID and Scanner_ Vulnerability_ID are listed hereinafter:
---------------------------------------------------------------- Scanner_ Vulnerability_ID CVE_ID ---------------------------------------------------------------- Scanner:00040017 CVE-1999-0146 Scanner:00015089 CVE-2000-0630 Scanner:00015007 CVE-1999-0918 Scanner:000300ec CAN-1999-0660 Scanner:000300ed CAN-1999-0660 Scanner:00010147 CVE-1999-0517 Scanner:00015063 CVE-2000-0258 Scanner:00015088 CAN-2001-0777 Scanner:0004040f CVE-2000-0302 Scanner:00040410 CAN-2000-0071 ----------------------------------------------------------------Please refer to the Security Information Guider for the others.
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):
The user can attain this goal according to the following steps:
Or in another way, we can attain this goal,as following:
- Select "Select View->Show all" from Vulnerability Scanner System Console. The "Show all" window will be displayed as illustrated.
- Select "Help->Event Help" from Vulnerability Scanner System Console. The "Security Information Guider" window will be displayed as illustrated.
- Type the CVE number in the "Contents" edit box as illustrated, and select "Search Content", then click the "Search" button. All the available information will be showed as following:
- Select "View Select" -> "Show all" in our Vulnerability Scanner System controlling Center
- Then the "Show all" dialog will show as following:
- Select the event and make right click ,in the popup menu select "detail information"
Another dialog will show the detail event information as following:
- Select the checkbox "help" and the CVE-related information and description will show at the right:
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):
The user can attain this goal according to the following steps:
- Select "View Select->Show all" from Vulnerability Scanner System Console. The "Show all" window will be displayed as illustrated.
- Select "Help->Event Help" from Vulnerability Scanner System Console. The "Event Help" window will be displayed as illustrated.
- Type the CVE number in the "Contents" edit box as illustrated, and select "Search Content", then click the "Search" button. All the available information will be showed as following:
- Click the hyperlink above the CVE NAME item, the CVE page with the respective CVE name will be opened, which includes the description and reference material of the event.
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: Lidan Zhou
Title: General Manager R&D Center
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: Lidan Zhou
Title: General Manager R&D Center