|
|
Name of Your Organization:
Hillstone Networks
Web Site:
Adopting Capability:
Intrusion Prevention System
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):
Hillstone is pleased to support CVE names in our network intrusion prevention system (IPS product line), as part of our commitment to embracing industry standards.
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):
Provide vulnerability assessment for customer and give out solution in vulnerability assessment report. Provide CVE ID information in the signature description form.
Map Currency Update Approach <CR_5.2>
Indicate how often you plan on updating the mappings to reflect the current CVE content and describe your approach to keeping reasonably current with the CVE content when mapping them to your repository (required):
When a new CVE version is released, we will select the focused new entries and put them be added to the database and website within two weeks. Old invalid 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 every two weeks to indicate the update, and the same time update in our signature database.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
If the identifier refers to the system and application in China or in our customer environment, it will be added into signature database of Hillstone network intrusion prevention system.
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 website, the user can search. Each new version will be listed on the top row. And for IPS device, users can search each signature CEV info through the searching function.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
We have already cooperated with the professional three party TrendMicro for the Signature and at the same time we have the professional researcher keeping contact with NVD-CVE website to know 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 CVE COMPATIBILITY in online help.
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):
The Management Client supports full-text or fuzzy searches and CVE name searches for vulnerability information. Each vulnerability with a corresponding CVE has an associated "Rule Information" page which contains relevant information for that vulnerability. Please refer to the answers forand <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):
Hillstone Intrusion Prevention System (IPS) supports full-text searches and security elements searches by using security rules. It will be same as that mentioned in
and <CR_4.3>. Each event in the report has a hyperlink to the respective vulnerability information page, this page also supplied 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):
Use CVE to search the signature information, then get the related ID (such as 305171), then click the hyperlink the detailed information could be popup.
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):
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):
http://www.hillstonenet.com.cn/services/ips/2_1_130.html
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):
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):
N/A
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can find associated elements in the capability by looking for their associated CVE name (required):
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):
In the report, we will list all the high risk level threat in a table, and list the related detailed information, as it is a pdf or html document, so user could use CTRL+F input the CVE number to search the threat info.
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):
Support the html format document:
http://update1.hillstonenet.com/support/IPS_Help/cn/SMTP/505221.html
http://update1.hillstonenet.com/support/IPS_Help/cn/TCP/705221.html
http://update1.hillstonenet.com/support/IPS_Help/cn/UDP/805221.html
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 support the fuzzy search, and could search the detailed information from short name or title then in the results we could got the CVE info and the CVE ID could hyper-link to the NVE-CVE website related information.
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):
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 signature table, users could use the CVE ID to search the related detailed information of a signature, in the result, there are signature name, risk level, protocol, category etc.
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: Peng Yao
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: Peng Yao
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: Peng Yao
Title: Product Manager