|
|
Name of Your Organization:
Shenyang Neusoft System Integration Co., Ltd
Web Site:
http://neteye.neusoft.com/en/
Compatible Capability:
NISG-IPS
Capability home page:
http://neteye.neusoft.com/en/products/index.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):
You can find CVE relevant information in the following directory of the NISG-IPS WebUI: Deep Inspection » Profile Settings » Attach Signatures » New Rule Set » search (select detailed).
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):
We have a dedicated team in charge of synchronizing the CVE information between the CVE website and our IPS WebUI and updating our IPS knowledge base each week. So users can find the up-to-date CVE information on the product WebUI.
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 update the CVE content once a week. The updating approach is: The latest information about the changes of CVE list comes from the CVE website bulletin board and MAILIST. From the information, we find the content referred in our rule database, and update the database.
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):
Our signature research team will always track CVE content changes, and will select some of them to put into the new version of signatures each week.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
We will select the CVE Identifiers that are popular in use and vital for system and applications.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Our IPS R&D group has special personnel to daily view, organize, and summarize CVE content changes.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
The latest CVE content mainly comes from CVE website bulletins and mailists.
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 product 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 following steps:
Steps:
- Select the " Deep Inspection » Profile Settings » Attach Signatures » New Rule Set.
- Input CVE name in the CVE text 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 following steps:
Steps:
- Select the "Deep Inspection » Profile Settings » Attach Signatures » New Rule Set.
- Input an ID number in the ID text box.
- Press the Search 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 NISG-IPS 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):
NISG-IPS supports full-text searches and security elements searches by using security rules. Please refer to the answers for <CR_4.2> and <CR_4.3>.
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):
Users can find security rules in a log as follows:
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):
Users can find CVE information in a log as follows:
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):
Users can find security rules on line in the following directory of the NISG-IPS WebUI: Deep Inspection » Profile Settings » Attach Signatures New Rule Set detailed.
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):
Users can find the online CVE information in the following directory of the NISG-IPS WebUI: Deep Inspection » Profile Settings » Attach Signatures New Rule Set detailed.
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):
Users can find the online CVE information in the following directory of the NISG-IPS WebUI:Deep Inspection » Profile Settings » Attach Signatures New Rule Set detailed.
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):
Users can find security rules on line in the following directory of the NISG-IPS WebUI: Deep Inspection » Profile Settings » Attach Signatures New Rule Set detailed.
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):
Users can find CVE information in a log like followings:
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 html format (online help), 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):
Users can look through the relationship between a CVE name and a security rule.
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_4.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):
Please refer to the answer for <CR_4.2>.
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: Bin Cao
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: Bin Cao
Title: General Manager