|
|
Name of Your Organization:
Beijing Venustech Cybervision Co., Ltd.
Web Site:
Compatible Capability:
Venusense Unified Security Gateway (Venusense UTM)
Capability home page:
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 UTM provides CVE compatibility in the module of "Events Set". This module provides the user CVE-related information 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 UTM 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 UTM Knowledge Base per week. If we find new important vulnerability, we will update UTM 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):
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 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):
See answer to <CR_5.2>.
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 UTM. 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 provide CVE description information in intrusion prevent event information.
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):
Finding Elements using CVE Names in the module of "Events Set" according to the following steps:
Steps:
- Select events set » all » detail »
- Input CVE name
- Click "go" 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):
From the graph below, we could clearly see that the event selected at the left: "TCP_Backdoor_Infector_Reaction", 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):
Finding TASKS using CVE Names in the module of "Events Set". Please see answers to <CR_4.2> and <CR_4.3>.
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):
Each event in the report has a hyperlink to the event information page; this page also supplies a CVE link to the CVE Web page.
Service Coverage Determination Using CVE Names <CR_A.3.1>
Give detailed examples and explanations of the different ways that a user can use CVE names to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):
The documents we provided are in HTML format, which includes hyperlink to the CVE web page correspond to the current selected event.
Finding CVE Names in Service Reports Using Elements <CR_A.3.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CVE names for the individual security elements in the report (required):
Some of the mapping information between the CVE_ID and IPS_EVENT_ID are listed hereinafter:
Finding Online Capability Tasks Using CVE Names <CR_A.4.1>
Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CVE name or through an online mapping that links each element of the capability with its associated CVE name(s) (required):
Finding ONLINE CAPABILITY TASKS using CVE Names in the module of "Events Set". Please see answers to <CR_4.2> and <CR_4.3>.
Finding CVE Names Using Online Capability Elements <CR_A.4.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CVE names for the individual security elements in the report. (required):
Please see answers for <CR_4.2> and <CR_4.3>.
Online Capability Element to CVE Name Mapping <CR_A.4.3>
If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CVE name(s), otherwise enter N/A (required):
Please see answers for <CR_4.2> and <CR_4.3>.
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can associated elements in the capability by looking for their associated CVE name (required):
For each CVE name, our UTM 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 UTM Knowledge Base per week. If we find new important vulnerability, we will update UTM Knowledge Base as soon as possible.
Finding CVE Names Using Elements in Reports <CR_A.5.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the capability allows the user to determine the associated CVE names for the individual security elements in the report (required):
Please see answer for <CR_A.2.2>
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 HTML format, 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):
Please see answers to <CR_4.2> and <CR_4.3>.
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):
Please see answers to <CR_4.2> and <CR_4.3>.
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):
Please see answers to <CR_4.2> and <CR_4.3>.
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: Xuebao Chen
Title: PM
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: Xuebao Chen
Title: PM
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: Xuebao Chen
Title: PM