Name of Your Organization:
Beijing Venustech Security Inc.
Web Site:
www.venustech.com.cn
Compatible Capability:
Venusense Intrusion Prevention System
Capability home page:
http://www.venustech.com.cn/SafeProductInfo/175/35.Html
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 IPS provides CVE compatibility in the module of Event Editor. This module provides the user CVE-related infromation in detail.
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 IPS has a hyperlink to the respective CVE page which provides a version number on the top of the event description. Our DB update application updates IPS Knowledge Base per week. If we find new important vulnerability, we will update IPS Knowledge Base as soon as possible.
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 (required):
When a new CVE version is released, all new entries will be added to the website within two weeks. Old candidates will be removed.
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):
We provide CVE update on our website by per day, per week and per month to indicate the update, and the same time update in our database, if the user doesn't update per week, there will be a message pop up on the GUI to mention the user to update the new CVE content.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
In the ADLab (active defense Lab) of Venustech, the experts have been keeping update with the CVE identifier. If the identifier refers to the system and application in China or in our customer environment, it will be added into signature database of Venusense IPS. And the user can get the CVE information in the event center.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
We list the history CVE content on our website, the user can search
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
We have the researcher keeping contact with CVE, and from the CVE website to knew the new content
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 have the researcher keeping contact with CVE, and from the CVE website to knew the new content
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 Event Editor part of our user document hereinafter:
For example:
- Input CVE-2006-2936 in the dialog box;
- 2. Select "content searching" in the middle box;
- 3. Click "search" for the respective CVE item.
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 Event Editor part of our user guide hereinafter:
From the graph above, we could clearly see that the event selected at the left :"TCP_CVS_double free_attack attempt", the reference information about the event at the right, and click the hyperlink to go to the related page about this item.
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 user can attain this goal according to the following steps:
- Select "View-> Event" from IPS Console. The "Show all" window will be displayed as illustrated.
- Select "Help->Event Help" from IPS Console. The "Event Help" window will be displayed as illustrated.
- Type the CVE number in the "Content" edit box as illustrated, and select "Search Content", then click the "Search" button, all the available information will be showed as following:
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 "View->Event" from IPS Console. The "Show all" window will be displayed as illustrated:
- Select "Help->Event Help" from IPS 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:
Or in another way, we can attain this goal, as following:
- Select "Event"->"Show All" in our IPS 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:
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 provided are in CHM format(event.chm),which includes hyperlink to the CVE web page correspond to the current selected event.
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 IPS_EVENT_ID are listed hereinafter:
please refer to the event.chm for the others.
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:
- Select "View"->"Event" from IPS Console. The "Show ALL" window will be displayed as illustrated.
- Select "Help->Event Help" from IPS 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.
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"->"Event" from IPS Console. The "Show ALL" window will be displayed as illustrated.
- Select "Help->Event Help" from IPS Console. The "Event Help" window will be displayed as illustrated.
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
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: Lidan Zhou
Title: General Manager R&D Center
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
