|
|
Name of Your Organization:
Beijing Venustech Security Inc.
Web Site:
www.venustech.com.cn
Compatible Capability:
Venusense Threat Detection and Intelligent Analysis System
Capability home page:
http://www.venustech.com.cn/SafeProductInfo/392/37.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):
Venusense Threat Detection and Intelligent Analysis System (TDS) provides CVE compatibility in the module of Event helper. 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, TDS 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 TDS Knowledge Base per week. If we find a new important vulnerability, we will update TDS 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 publicize the CVE updates on our web site. In the "Security Bulletin" of our homepage, we provide the update information by per day, per week and per month, and at the same time there is also update in our Knowledge Base by per week. The user can click "Check updates", and TDS will check if there are new updates.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
We have a professional team named ADLab to check the vendors' vulnerability information, and decide whether a signature should be added or updated.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
When updating signature, ADLab reviews CVE website for content changes.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
CVE website: https://cve.mitre.org/
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 Event helper.
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 helper part of our user document hereinafter:
For example:
- Input CVE-2003-0015 in the dialog box;
- 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 Helper hereinafter:
From the graph above, we could clearly see that the event selected at the left: "TCP_SHOUTcat_1.9.4_....", 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:
- Click the "Helper" in left navigator bar
- Click the "Event Helper"
- Input CVE name in the search box
- 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 appendix of report is detail information about the events which list CVE name shown below:
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 a chm file for events shown below:
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):
There is a line include CVE name in the detail information of each event, shown below:
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:
- Click the "Helper" in left navigator bar
- Click the "Event Helper"
- Input CVE name in the search box
- Click the "search" button
- All the available information will be showed as following:
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):
We cite the Event Helper hereinafter:
We could clearly see that the event selected at the left: "TCP_SHOUTcat_1.9.4_....", the reference information about the event at the right, and click the hyperlink to go to the related page about this item.
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