Name of Your Organization:
Legendsec Technology Co. Ltd
Web Site:
www.legendsec.com
Compatible Capability:
Legendsec SecIPS 3600 Intrusion Prevention System
Capability home page:
http://www.legendsec.com/newsec.php?up=2&cid=57
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):
CVE compatibility information available in the module of Policy viewer within Our management client.
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 Rule, our IPS has a hyperlink to the respective rule page, and from the page, a hyperlink of CVE name is supplied to link the respective CVE page which provides a version number on the top of the event description. Our Application Support Team updates IPS Knowledge Base weekly.
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):
We provide CVE description information in References in Rule Information page of management client.
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):
We issue release notice to customes through emails and update information on Web site.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
Besides a professional team maintaining all necessary information, external resources deliver accurate and in-time reports as well.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
We download CVE source from https://cve.mitre.org/data/downloads/index.html and to compare.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
https://cve.mitre.org/data/downloads/index.html
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 References in Rule Information page of management client.
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 the management client according to the following steps:
- Select Rule -> Default Rules -> Tree View
- Click Search button
- Input CVE name
- Press Find Next button to complete the task.
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 the management client according to the following steps:
- Select Rule -> Default Rules -> Tree View
- Click Search button
- Input Element
- Press Find Next button to complete the task.
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 Management Client supports full-text searches and CVE name searches for vulnerability information. Each vulnerability with a corresponding CVE has an associated "Rule Information" page which contains relevant information for that vulnerability. Please refer to the answers for 4.2 and 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 in the report has a hyperlink to the respective vulnerability information page, this page also supplied a CVE link to the CVE Web page.
Service Coverage Determination Using CVE Names <CR_A.3.1>
Give detailed examples and explanations of the different ways that a user can use CVE names to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):
- Select Monitor -> Event Monitor.
- Click pause button.
- Double click on any event to complete the task.
Finding CVE Names in Service Reports Using Elements <CR_A.3.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CVE names for the individual security elements in the report (required):
- Select Report -> Event Report
- Select date.
- Double click on any event.
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):
http://www.legendsec.com/rule_info/ips/gb/R1053473.xml
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):
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):
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0311
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can associated elements in the capability by looking for their associated CVE name (required):
- Select Rule -> Default Rules -> Tree View
- Click Search button
- Input CVE name
- Press Find Next button to complete the task.
Finding CVE Names Using Elements in Reports <CR_A.5.2>
Give detailed examples and explanations of how, for reports that identify individual security elements, the capability allows the user to determine the associated CVE names for the individual security elements in the report (required):
- Select Report -> Event Report
- Select date.
- Double click on any event.
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 is in HTML format, which can be searched using the full-text search and CVE Name search mechanism in the GUI.
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 Event_ID are listed hereinafter
Event_ID CVE_ID 1052723 CVE-2006-6134 1052725 CAN-2006-5559 1052739 CVE-2006-6561 1052759 CVE-2007-0024 1052809 CVE-2007-1204 1053007 CVE-2007-4814 1052824 CVE-2006-4691 1052822 CVE-2007-1749 1052919 CVE-2007-0040
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 Management Client 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 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 "References" section of each rules's Rule Information page. Please refer to the answer for 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: LinBo
Title: General 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: LinBo
Title: General Manager
