Name of Your Organization:

Kingnet Security, Inc.

Web Site:

www.kingnet.biz

Compatible Capability:

Kingnet Intrusion Detection System (KIDS)

Capability home page:

www.kingnet.biz/products/

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):

Our KIDS provide CVE compatibility in the module of Event Analyzer and Event Editor. These modules provide the user CVE-related information in detail.

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):

For each CVE name, KIDS has a hyperlink to the respective CVE page which provides a version number on the top of the event description. Our Application Support Team updates KIDS Knowledge Base per week.

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):

We provide CVE description information in About CVE on page 154-156 of our User Guide.

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):

We cite the Event Search of the Event Editor part of our user document hereinafter:

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):

We cite the Event Viewing of the Event Editor part of our user guide hereinafter:

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 CAN- prefix is used for all candidates to differentiate them from CVE entries which have the CVE- prefix.

Type-Specific Capability Questions

17) 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 user can attain this goal according to the following steps:

1. Select Security Management->Event Editor from KIDS Console. The Event Editor window will be displayed as illustrated.
   
   
2. Click the search button at the bottom of the Event Editor window. The Search dialog box will be displayed as illustrated.
   
   
3. In the search dialog box, select the CVE reference checkbox, which means the user want to search an event based on a CVE number.
   
4. Type the CVE number in the Searching Contents edit box as illustrated, and click the Search button.
   
   
5. The Event Editor will find the event information which corresponds to the CVE name entered previously, as illustrated.
   

18) 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):

The user can attain this goal according to the following steps:

1. Select an IP or Event or Event Type in the Tree View of KIDS Console.
   
2. Select Event Analyzer from the shortcut menu as illustrated:
   
   
3. The Event Analyzer Window is displayed.
4. In Event Tree View of the Event Analyzer Window, select a leaf node enunciated when the event occurred.
5. The information of the respective event will be displayed in the Event Information View.
6. Click the Detailed Information tab page in the Event Analyzer window. The CVE NAME item will be displayed as illustrated:
   
   
7. Click the hyperlink alongside the CVE NAME item, the CVE page with the respective CVE name will be opened, which includes the description and reference material of the event.
   
   

31) 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 CHM format (event.chm), which includes hyperlink to the CVE web page correspond to the current selected event.
• in PDF format (user guide),which includes the introduction and using method of CVE Compatibility.

32) 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 KIDS_EVENT_ID are listed hereinafter:

         ----------------------------------
         KNIDS_EVENT_ID CVE_ID
         ----------------------------------
         KIDS:1040 CVE-1999-0009
         KIDS:1044 CVE-1999-0833
         KIDS:1049 CAN-1999-0736**
         KIDS:1050 CVE-1999-0513
         KIDS:1057 CVE-1999-1011
         KIDS:1058 CVE-1999-0407
         KIDS:1059 CAN-2000-0726**
         KIDS:1060 CVE-1999-0233
         KIDS:1061 CVE-1999-0278
         KIDS:1064 CAN-2000-0302**
         ----------------------------------

Please refer to the event.chm for the others.

34) 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 user can attain this goal according to the following steps:

1. Select Security Management->Event Editor from KIDS Console. The Event Editor window will be displayed as illustrated.
   
   
2. Click the search button at the bottom of the Event Editor window. The Search dialog box will be displayed as illustrated.
   
   
3. In the search dialog box, select the CVE reference checkbox, which means the user want to search an event based on a CVE number.
   
4. Type the CVE number in the Searching Contents edit box as illustrated, and click the Search button.
   
   
5. The Event Editor will find the event information which corresponds to the CVE name entered previously, as illustrated.
   

35) 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):

KIDS Event Editor can attain this goal according to the following steps:

1. Select Security Management->Event Editor from KIDS Console as illustrated.
   
   
2. An Event Tree will be displayed in the left frame of the Event Editor window.
   
3. Find and select the event which the user wants to get its CVE compatibility information, as illustrated.
   
   
4. Click the Reference Information tab page in the right frame of he Event Editor window, as illustrated.
   
   
5. On the top of the tab page, displayed a CVE reference hyperlink and a CVE name of the respective event.
   
6. Click the CVE reference hyperlink, the CVE page with the respective CVE name will be opened, which includes the description and reference material of the event, as illustrated.
   
   

KIDS Event Analyzer can attain this goal according to the following steps:

1. Select an IP or Event or Event Type in the Tree View of KIDS Console.
2. Select Event Analyzer from the shortcut menu as illustrated:
   
   
3. The Event Analyzer Window is displayed.
   
4. In Event Tree View of the Event Analyzer Window, select a leaf nod enunciated when the event occurred.
   
5. The information of the respective event will be displayed in the Event Information View.
   
6. Click the Detailed Information tab page in the Event Analyzer window. The CVE Name item will be displayed as illustrated:
   
   
7. Click the hyperlink alongside the CVE Name item, the CVE page with the respective CVE name will be opened, which includes the description and reference material of the event.
   
   

Please refer to the answer to the 32nd question for the mapping format.

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: Dr. Qingjie Zhou

Title: GM R&D Center

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: Dr. Qingjie Zhou

Title: GM R&D Center