Name of Your Organization:
H3C Technologies Co., Limited
Web Site:
www.h3c.com.cn
Compatible Capability:
SecBlade IPS
Capability home page:
http://www.h3c.com.cn/Products%5F%5F%5FTechnology/Products/IP%5FSecurity/IPS/
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):
Vulnerability information is available within the management Web page.
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):
We provide CVE detail information by a link to related CVE page.
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 promise our customers that we will update the CVE mapping at most once a month.
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):
Our signature research team will always track CVE content changes, and will select some of them to put into the new version of signatures.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
That is mainly according to which contained in the vendors' vulnerability information.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
If the CVE content changes, it will reflect on CVE webpage. So, we provide CVE detail information by a link to related CVE page, which will make our users see the changes directly on the page.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
First, find the corresponding CVE Id according to published vulnerability information from vendors, and then find the corresponding relevant Web site on 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):
http://www.h3c.com/portal/Technical%5FSupport%5F%5F%5FDocuments/Technical%5FDocuments/Security%5FProducts/H3C%5FSecBlade%5FIPS%5FCard/Configuration/User%5FManual/04%2DIPS/
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):
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):
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):
Users can look for "CVE-2007-2218", for example, by visiting the manage IP via web: open the page "IPS > IPS Rules", fill the CVE name (or a part of the CVE name) in the right place, and click the 'Query' button, then they can locate tasks in the tool.
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):
When users browse the reports in the web page, they can click the 'Attack ID' or 'Attack Name' to get the details of the individual security elements, including the associated CVE names.
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, which include all the related CVE names. Users can use "find" and "search" function in it.
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):
We have provided full CVE names in the report.
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 refer to the answer for <CR_A.2.1>
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):
in the web page 'IPS > IPS Rules', using the CVE name, we can select the associated security elements .click "Attack ID " or "Name", we get another web page ,and obtain the mapping between CVE entries and the capability's elements.
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: Gong Yibin
Title: Product Manager
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: Gong Yibin
Title: Product Manager
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: Gong Yibin
Title: Product Manager
