|
|
Name of Your Organization:
Hangzhou DPtech Technologies Co., Ltd.
Web Site:
Compatible Capability:
DPtech IPS2000
Capability home page:
http://www.diputech.com/www_en/Products_Technology.php?id=12&m=1 (English)
http://www.diputech.com/Products_Technology.php?id=10&m=2 (Chinese)
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):
DPtech IPS2000 for network-based intrusion prevention system is available via website.
Related resources and links:
- DPtech Vulnerability Database:
http://www.diputech.com//Research.php?id=5&name=%B0%B2%C8%AB%B9%AB%B8%E6 (Chinese)- DPtech IPS2000 Software Update:
http://www.diputech.com//Soft2.php?soft_p_id=10 (Chinese)
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):
DPtech Vulnerability Database is updated on daily basis with latest vulnerability and CVE mapping information from a variety of sources including CVE.
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):
DPtech Vulnerability Database is updated on daily with latest vulnerability and CVE mapping information from a variety of sources including CVE.
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):
DPtech Vulnerability Database is always up to date, which is documented in new version of signatures.
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 User Guide.
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):
CVE names may be used as a search criterion from IPS signature manager:
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):
Security information can be searched from IPS signature manager. If the information is related to specific CVE information, then the CVE name and link to MITRE website will appear in Description section.
Detailed alert information can be searched from IPS signature via alert name or other key words. If the alert is related to specific CVE information, then the CVE name and link to MITRE website will appear in it.
The following figures show the CVE name link.
Documentation Indexing of CVE-Related Material <CR_4.4>
If your documentation includes an index, provide a copy of the items and resources that you have listed under "CVE" in your index. Alternately, provide directions to where these "CVE" items are posted on your web site (recommended):
A list of CVE-related vulnerability is available by searching "CVE" IPS signature manager.
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 utilize product’s IPS rules manager in order to find related CVEs and information about the corresponding CVE. Links to https://cve.mitre.org are also commonly available.
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):
CVE details and links are provided in most DPtech IPS2000 alerts if only corresponding CVE name is available. Each available CVE can be searched by its name in IPS signature manager.
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 .xls 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 特征管理’, using the CVE name, we can get 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: Ye qian
Title: Director of DPtech Signature Team
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: Ye qian
Title: Director of DPtech Signature Team
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: Ye qian
Title: Director of DPtech Signature Team