|
|
Name of Your Organization:
DragonSoft Security Associates, Inc.
Web Site:
http://www.dragonsoft.com
Compatible Capability:
DragonSoft Vulnerability DataBase
Capability home page:
http://vdb.dragonsoft.com/
1) 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):
The Dragonsoft Vulnerability DataBase can be accessed online with a standard web browser.
4) 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):
The CVE version number DragonSoft Vulnerability DataBase mapped to is displayed on the top left corner of the home page.
5) 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 (recommended):
Vulnerability technicians are responsible for update database content upon notification of a new CVE version. The CVE version information on the web site is updated after the content correctness is validated.
6) 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 a newly released CVE version (recommended):
The update process after a new CVE version released takes no longer than 5 working days.
7) 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):
The information about CVE is provided by direct link to official CVE web page. On the home page of DragonSoft Vulnerability DataBase, users can clink on the CVE version number to navigate to the about CVE web page on MITRE web site.
8) 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):
Users can find individual security element with CVE name using the search function on the web page of DragonSoft Vulnerability DataBase. The interface is straitforward, no explicit document is provided.
9) 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):
Users can find individual security element with vulnerability name, desciption or BugTraq/X-Force ID number. The CVE name is showned in the detail information of an element, no explicit document is provided.
11) Candidates Versus Entries Indication <CR_6.1>
If CVE candidates are supported or used, explain how you indicate that candidates are not accepted CVE entries (required):
The CVE candidates are used as well as accepted entries in the capability. Customers can distinguish CVE candidates from accepted CVE entries according to the prefixes of entry names (CAN- for candidates, CVE- for accepted entries). The CVE name and associate link to MITRE CVE web page is provided. Customers can use the link to check further information about the specific entry.
13) Candidate to Entry Promotion <CR_6.3>
If CVE candidates are supported or used, explain your policy for changing candidates into entries within your capability and describe where and how this is communicated to your customers (recommended):
When new CVE version is released, the candidates that change into accepted entries are updated in the repository. The name of such an entry is changed according to the new version. Customers can identify the change through entry name prefix.
Type-Specific Capability Questions
26) 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):
On the database home page, users can find a text box adjacent to the label "Search". Type in the complete CVE name (or candidate name) and click the "GO" button on the right, the security elements associate to the name are displayed in a list.
29) 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):
When the information of an security element is displayed, the corresponding CVE name is listed in the "CVE ID:" field.
30) 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
37) 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: Ming-Jye Tsai
Title: CEO
38) 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: Ming-Jye Tsai
Title: CEO
39) 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: Ming-Jye Tsai
Title: CEO