|
|
Name of Your Organization:
Beijing Netpower Technologies Inc.
Web Site:
Adopting Capability:
Netpower Network Intrusion Detection System (NPIDS)
Capability home page:
http://www.netpower.com.cn/pro/chuantongwangluoanquanchanpin/NPIDS/2014/0507/98.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):
Our IDS provides CVE compatibility in the module of Policy Management. This module shows the user CVE-related information in detail.
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, NPIDS has a hyperlink to the respective CVE page which provides a version number on the top of the event description. Our Application Support updates NPIDS Knowledge Base monthly.
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):
We update the CVE content once a month. The updating approach is: The latest information about the changes of CVE comes from Snort website. We choose the most important rules to add our database.
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):
At the same time as the rule database is updated, its relevant CVE update files will be released in the company's website. Our customers can download it from the website and update rules in the "升级管理"，in this page, there is rules updated timeframe. Please refer to flowing 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):
CVE has description and related links. In most case, CVE entry is linked to vendor's security advisory or public exploit code. According to the information, we can find proper CVE entry for rule description.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
We check CVE content from Snort website monthly, if there is any change, we will download CVE source and choose important rules to add our system.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
The latest CVE content mainly comes from Snort website. There are related CVE names in the 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 rule 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 Management according to the following steps:
Steps:
- Select "策略管理" from webpage of the NPIDS System with https protocol, example: https://192.168.0.101:8888, please refer to chart 1.
- Press "搜索策略" button, and popup "Search" dialog.
- Input CVE name in the edit box, please refer to chart 2.
- Press the Search button to complete the task, please refer to chart 3 and chart 4.
Chart 1
Chart 2
Chart 3
Chart 4
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 Management according to the following steps:
Steps:
- Select "策略管理" and "当前规则配置" from webpage of the NPIDS with https protocol, example: https://192.168.0.101:8888, please refer to chart 1.
- Choose a rule from the Rule types (right aside) and click it, please refer to chart 2.
Chart 1
Chart 2
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 Current Rules support full-text searches and CVE name searches for rule information. Each rule with a corresponding CVE name has an associated "查看" page which contains relevant information for that rule. Please refer to the answers for and <CR_4.2> and <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):
Each event has associated rule information that is same as Current Rules in the Alarm Events window.
Steps:
- Click "报警查询"，there are events in the right aside, please refer to the flowing chart 1.
- Choose one event and click it, you can see detailed information and CVE name, 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 HTML format and PDF format. And you can see detail information in alarm inquire, like CVE name, CVE compatibility, event explanation, and remediation method, please refer to following chart:
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, click alarm name, there is related CVE ID to rule-ID, please refer to flowing chart 1 and chart 2:
Chart 1
Chart 2
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 Current Rules supports full-text searches and CVE name searches for rule information. The user may search for an element using the CVE name. Please refer to the answer for <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 under the "CVE" section of each rule's message. 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: Chen Zhenpeng
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: Chen Zhenpeng
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: Chen Zhenpeng
Title: Product Manager