|
|
Name of Your Organization:
Beijing Netpower Technologies Inc.
Web Site:
Adopting Capability:
Netpower Network Vulnerability Scanner (NPNS)
Capability home page:
http://www.netpower.com.cn/pro/chuantongwangluoanquanchanpin/Scanner/2014/0507/99.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):
Provide vulnerability assessment for customer and give out solution in vulnerability assessment report. CVE Compatibility information is available in vulnerability template.
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, NPNS has a vulnerability template. In this template, indicate CVE Compatibility and provide vulnerability description. Our Application Support Team updates NPNS Knowledge Base Weekly.
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):
In left section of NPNS homepage, there is an item named "升级授权" (update and authorization), click it into subpage frame, choose tab page of "漏洞库升级" (vulnerability update), NPNS can realize to update the mappings. Please refer to following chart:
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):
In left section of NPNS homepage, there is an item named "升级授权" (update and authorization), click it into subpage frame, choose tab page of "漏洞库升级" (vulnerability update), in this page, there is vulnerability updated timeframe. Please refer to following chart:
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
Please according to following steps to Find how to find NPNS capability based on CVE ID:
- Select "显示策略" (Policy Display) from webpage of the Netpower Network Vulnerability Scanner with https protocol, example: https://192.168.0.101:8888, please refer to chart 1.
- Select "全策略模板" (Total Policy Module) and click "显示漏洞列表" (vulnerability list) button to indicate total vulnerability list, please refer to chart 2.
- Press "查询" (Search) button, and Popup "查询" (Search) dialog.
- Input CVE name in CVE ID edit box, please refer to chart 3.
- Double click vulnerability item that was found in previous step, please refer to chart 4.
Chart 1
Chart 2
Chart 3
Chart 4
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
We check CVE content from CVE website weekly, if there is any change, we will update in our system.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
NPNS get CVE content from CVE website.
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 vulnerability detail information page:
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 Policy Display according to the following steps:
- Select "显示策略" (Policy Display) from webpage of the Netpower Network Vulnerability Scanner with https protocol, example: https://192.168.0.101:8888, please refer to chart 1.
- Select "全策略模板" (Total Policy Module) and click "显示漏洞列表" (vulnerability list) button to indicate total vulnerability list, please refer to chart 2.
- Press "查询" (Search) button, and Popup "查询" (Search) dialog.
- Input CVE name in CVE ID edit box, please refer to chart 3.
Chart 1
Chart 2
Chart 3
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 Policy Display according to the following steps:
- Select "显示策略" (Policy Display) from webpage of the Netpower Network Vulnerability Scanner with https protocol, example: https://192.168.0.101:8888, please refer to chart 1.
- Select "全策略模板" (Total Policy Module) and click "显示漏洞列表" (vulnerability list) button to indicate total vulnerability list, please refer to chart 2.
- Press "查询" (Search) button, and Popup "查询" (Search) dialog.
- Input CVE name in CVE ID edit box, please refer to chart 3.
- Double click vulnerability item that was found in previous step, please refer to chart 4.
Chart 1
Chart 2
Chart 3
Chart 4
Type-Specific Capability Question
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 vulnerability template supports full-text searches and CVE name searches for vulnerability information. Each vulnerability with a corresponding CVE ID has an associated explanation page which contains relevant information for that vulnerability. Please refer to the answers for question and question <CR_4.2> and question <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):
In vulnerability report, Netpower Network Vulnerability Scanner will list all vulnerability issue for customer, in section of host vulnerability distribution indicate all vulnerability event, each vulnerability ID is a hyperlink (please refer to chart 1), click it, corresponding vulnerability detail information will be indicated, which include CVE name and vulnerability detail explanation information (please refer to chart 2).
Chart 1
Chart 2
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):
The documents we provide are:
- In html format, which can be searched using the full-text search and CVE Name search mechanism in the GUI.
- In HTML, PDF, DOC, TXT, XML format (vulnerability assessment report), which includes many kinds of detail vulnerability information, like CVE name, CVE Compatibility, vulnerability explanation, and remediation method.
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 NID-ID are listed 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 "Policy Display" supports full-text searches and CVE name searches for vulnerability information. The user may search for an element using the CVE name. Please refer to the answer for question <CR_4.2>.
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 "vulnerability template" section. Please refer to the answer for <CR_4.3>.
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: Xu Wenjuan
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: Xu Wenjuan
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: Xu Wenjuan
Title: Product Manager