Name of Your Organization:
Huawei-3Com Co. Ltd.
Web Site:
www.huawei-3com.com
Compatible Capability:
Quidway SecEngine Intrusion Detection System
Capability home page:
Quidway SecEngine Intrusion Detection System
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):
CVE compatibility information is available in the module of rule base within our Quidway SecEngine IDS Web management system.
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 Quidway SecEngine IDS has a hyperlink to the respective CVE page which provides a version number on the top of the event description. Our Application Support Team updates rule base every two weeks.
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):
You can get the documentation from our Web site.
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):
Finding Elements using CVE Names in Quidway SecEngine IDS Web management system according to the following steps:
Steps:
- Select the rule base->pre-defined menu from Quidway SecEngine IDS Web management system to open the pre-defined rule base window;
- Input CVE name in the CVE ID edit box;
- Press the Search button to complete the task.
Example :
- input "cve-2000-0138"in the CVE ID edit box;
- press the Search button to complete the task.
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):
Finding CVE Names using Elements in Quidway SecEngine Web management system according to the following steps:
Steps:
- Select the rule base->pre-defined menu from Quidway SecEngine IDS Web management system to open the pre-defined rule base window;
- press
button to view the specified information;
- Each CVE name has a hyperlink, Click the CVE name item, the CVE page with the respective CVE name will be opened.
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):
CVE candidates are not supported.
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):
Quidway SecEngine Web management system supports CVE name searches for vulnerability information.
Please refer to the answers for question 8 and question 9.
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):
Please refer to the answers for question 8 and question 9.
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 RULE_ID are listed hereinafter:
RULE_ID CVE_ID
Please refer to the rule.xls for details.
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 Quidway SecEngine Web management system supports CVE name searches for vulnerability information. The user may search for an element using the CVE name.
Please refer to the answer for question 8.
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):
CVE names are listed in the specified information of each rule.
Please refer to the answer for question 9.
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:
Title:
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:
Title:
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:
Title:
