|
|
Name of Your Organization:
Beijing Leadsec Technology Co., Ltd.
Web Site:
www.leadsec.com.cn
Compatible Capability:
Leadsec Security Intrusion Detection System
Capability home page:
http://www.leadsec.com.cn/node/324.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):
CVE compatibility information is available in the module of Policy Editor, Event Helper and Historical Events within the LeadsecIDS management console.
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, LeadsecIDS has a hyperlink to the respective CVE page which provides a version number on the top of the event description. Our Application Support updates LeadsecIDS Knowledge Base weekly.
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):
Rule team operates internet storm center for our customers (like sans isc) and check new advisories,new exploits, new malware on a daily basis. When cve is updated, we review and update our intrusion rule descriptions.
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):
If management system is deployed in open network, system can check rule update notification and download new rule database file. (by connect to our central rule repository with secure channel.) In this case, rule database can be updated on a hourly basis. If management system is deployed in closed network (that is, auto-update check is not available), network operator should check rule update manually. In this case, timeframe depends on customer's security operation policy.
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 have description and related links. In most case, cve entry is linked to vendor's security advisory and/or public exploit code. These informations can be used to find proper cve entry for rule description.
Map Currency Update Mechanism <CR_5.4>
Describe how and where your capability indicates the most recent CVE version used to create or update its mappings (required):
We collect most recent cve entries from NIST nvd-cve xml source automatically.
When new cve entry is added or modified, rule team checks that is related with current rule.
Map Content Source <CR_5.5>
Describe the source of your CVE content, (i.e., we gather info from mailing lists, product change logs, software vendors' security bulletins...) (required):
We collect most recent cve entries from NIST nvd-cve xml source automatically.
(http://nvd.nist.gov/download/nvdcve-modified.xml)
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 online help.
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 Event Helper according to the following steps:
Steps:
- Select the Help->Event Helper menu from the LeadsecIDS Management console to open the Event Helper window;
- Input CVE name in the Searching Contents edit box under the find event tab;
- Press the Search button to complete the task.
Example:
input "CVE-2001-0500" in the Searching Contents edit box;
press the Search 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 Event Helper according to the following steps:
Steps:
- Select the Help->Event Helper menu from the LeadsecIDS Management console to open the Event Helper window;
- Double click an Event from the Event Tree View of the Event Helper;
- Display the help message of selected event on the right section of the Event helper window as illustrated;
Display the CVE names automatically when the mouse moves over the "CVE" label;
Each CVE name is a hyperlink. Click the CVE name item and the CVE page with the respective CVE name will be opened, which includes the description and reference material of the event.
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 that have not yet been promoted to a CVE name to differentiate them from CVE entries which have the CVE- prefix.
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 Event Helper supports full-text searches and CVE name searches for vulnerability information. Each vulnerability with a corresponding CVE has an associated "help" page which contains relevant information for that vulnerability. Please refer to the answers for <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 vulnerability information that is same as Event Helper in the historical Events window.
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 mdb format, which can be searched using the full-text search and CVE Name search mechanism in the GUI.
- in CHM format(online help:Manager.chm), which includes the introduction and using method of CVE Compatibility.
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 2001-0139 CVE-2000-0192 2001-0141 CAN-2000-0769 2001-0142 CVE-1999-0800 2001-0143 CVE-2000-0540 2001-0144 CVE-2000-0120 2001-0145 CVE-2000-1005 2001-0146 CVE-2000-0435 2001-0147 CVE-1999-0947 2001-0148 CVE-1999-0947
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 Event Helper 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 <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 event's help 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: yanle
Title: the engineer of IDS
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: yanle
Title: the engineer of IDS
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: yanle
Title: the engineer of IDS