Name of Your Organization:
Huawei Technologies Co., Ltd.
Web Site:
Compatible Capability:
Huawei Network Intrusion Detection System (NIP D)
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):
As stand-alone IDS appliances, NIP2000D and NIP5000D series are publicly available for our customers to purchase. Our customers get CVE compatibility from the appliances out of the box.
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):
With each signature we release to our customer that has CVE mapping, our NIP appliances provide a hyperlink to the related CVE webpage.
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 release updates at least once a week. The update can be introducing new signatures or updating the existing ones. We’ll maintain the newly introduced content including CVE mappings. Since there’re CVE references in signature description page our customer can get latest information on vulnerabilities.
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):
The content (signatures and related information) for NIP appliances is updated at least once a week. CVE mapping is also updated through a content update. Our customer can expect CVE mapping update on each content update we release for the NIP appliances. Also, instead of copying CVE contents into the appliance, we provide a hyperlink to the CVE page. So our mapping can automatically reflects to the latest CVE content.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
When a signature is newly introduced or updated, our security team will search the CVE List. If there’s relevance to a CVE name, a reference to that CVE name will be attached to the signature description section.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Our security team reviews every single change to the content update package which includes CVE related information.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
- nvd.nist.gov
- 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):
See huawei_ipsv1r1_cd_en_cve.chm, search "CVE".
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):
See huawei_ipsv1r1_cd_en_cve.chm, search "By CVE Name".
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):
See huawei_ipsv1r1_cd_en_cve.chm, search "Advanced Searching Threat Prevention Logs".
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):
Example: Finding a signature using CVE name "CVE-2011-2462" on an NIP appliance.
STEP 1. Log into the Web GUI of an NIP appliance, navigate to the page "Application Security » Threat Prevention » Pre-Defined Signature".
STEP 2. Click on "Advanced Search".
STEP 3. In the popped window, choose "By CVE Name" as the condition and then type in the CVE Name filter "CVE-2011-2462". Click OK.
STEP 4. Now you can see a list of signatures that related to the CVE name. Click on "
" to view the details.
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):
Example: Finding CVE names using elements (security events).
STEP 1. Log into the Web UI of an NIP appliance, navigate to the page "Monitor » Log".
STEP 2. Locate an interested event and click "
STEP 3. Click to expand the "Reference" panel and you’ll see the CVE name and some cross-link references.
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 have chm- and pdf-based documentations; these formats are search friendly.
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):
Security elements (signatures) are frequently being updated, we don’t list them in documentation formats. Users can browse them through the GUI.
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):
See answer to 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):
See answer to CR_A.2.2.
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: Wu Hao
Title: Development 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: Lian Lian
Title: System Engineer
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: Lian Lian
Title: System Engineer
