|
|
Name of Your Organization:
NileSOFT Ltd.
Web Site:
www.nilesoft.co.kr
Compatible Capability:
Secuguard NSE (Network Security Explorer)
Capability home page:
http://www.nilesoft.co.kr/eng/product/nse.htm
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):
Secuguard NSE® shows vulnerability assessment information from the main auditing screen, reporting, and policy manager.
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 current CVE version used by Secuguard NSE is displayed in the Policy Editor window.
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):
NileSOFT updates the vulnerability database for Secuguard NSE® at least once a month and provides additional updates when necessary. The vulnerability database is updated with the latest version of CVE.
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):
NileSOFT guarantees our customers at least one update of the vulnerability database a month and additional updates when necessary. This guarantee is stated in the Licensing Agreement given upon the purchase of the product. The latest CVE version is always updated when updating the vulnerability database. Secuguard NSE and its vulnerability database support English, Korean, Japanese, and Chinese. Due to the time necessary for translating the vulnerability items from Korean to other languages, the vulnerability database updates for languages other than Korean are one step later than the Korean database.
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):
CVE and CVE compatibility is described in detail in the help file under IV. Product Management (Scan and Report) -> 7. CVE -> CVE Compatibility.
Screenshots of the help file are attached to the email.
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):
CVE and CVE compatibility is described in detail in the help file under IV. Product Management (Scan and Report) -> 2. Scan option and category management -> 2.2 Management of scan category.
Screenshots of the help file are attached to the email.
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):
CVE and CVE compatibility is described in detail in the help file under IV. Product Management (Scan and Report) -> 2. Scan option and category management -> 2.2 Management of scan category.
Screenshots of the help file are attached to the email.
10) Documentation Indexing of CVE-Related Material <CR_4.4>
If your documentation includes an index, provide a copy of the items and resources that you have listed under "CVE" in your index. Alternately, provide directions to where these "CVE" items are posted on your web site (recommended):
The documentation (manual and help file) included in the product describes CVE-compatibility.
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 indicate that they are candidates and the CVE- prefix is used for candidates that are accepted CVE entries. Detailed explanation can be found in the online help and manual.
12) Candidates Versus Entries Explanation <CR_6.2>
If CVE candidates are supported or used, explain where and how the difference between candidates and entries is explained to your customers (recommended):
Secuguard NSE supports CVE candidates. When the user clicks on the url link for the CVE candidate, the user is directed to the CVE online database and the Candidate information is displayed at the top of the page. The difference between CVE candidates and entries are described in detail in the help file, user manual, and the product's homepage.
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):
Our vulnerability database is updated a couple times a month and more if necessary. It is our policy that the latest CAN/CVE listings are applied to every vulnerability database update. This policy is stated in the user manual.
14) Candidate and Entry Search Support <CR_6.4>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's ability to look for candidates and entries by using just the YYYY-NNNN portion of the CVE names (recommended):
When the customer uses the Scan Policy Editor feature, there is a search function where the customer can enter any portion of the CVE or CAN name (including the YYYY-NNNN portion) and view the search results. This feature is documented in the help file and manual.
15) Search Support for Promoted Candidates <CR_6.5>
If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's support for retrieving the CVE entry for a candidate that is no longer a candidate (recommended):
As mentioned in number 13 and 14, our vulnerability database maintains the latest mapping of CVE/CAN listings and can be searched using the search feature in the Scan Policy Editor.
16) Candidate Mapping Currency Indication <CR_6.6>
If CVE candidates are supported or used, explain where and how you tell your users how up-to-date your candidate information is (recommended):
The Scan Policy Editor shows the version information for the CVE database number used in Secuguard NSE. The user manual states that the NileSOFT applies the latest CVE listings in every vulnerability definition update, which is updated at least once a month.
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):
In the Scan Policy Editor, the user can search for any portion for the CVE name and view the results. By clicking on the CVE name in interest, the user can view the detailed description of the vulnerability, the impact the vulnerability could have on the system, various methods that can be used to fix the vulnerability, links to available patches, vender, and other reference sites.
[Click on the CVE tab -> Enter the search criteria -> Select search options -> Press the search button] to view the descriptions, impact, remedy of the selected vulnerability item and apply the results to the server to scan for the selected vulnerability items.
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):
All reports generated by Secuguard NSE show the corresponding CVE names for individual security elements. The user can use the search function within the report to find the CVE name in interest.
As shown in this screenshot, the CVE ID matching the individual vulnerability item is shown. The user can search for CVE IDs using the search feature located in the report toolbar.
19) Getting a List of CVE Names Associated with Tasks <CR_A.2.4>
Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the tool's tasks (recommended):
The user can obtain the entire listing of all the CVE names supported by Secuguard NSE by pressing the View All button in the Scan Policy Editor after selecting the CVE tab.
20) Selecting Tasks with a List of CVE Names <CR_A.2.5>
Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):
The user can use the search feature of the Scan Policy Editor to search for the specific CVE names or press the View All button to view all supported CVE names. Then by clicking on the CVE name in interest, the user can view the detailed description of the vulnerability, the impact the vulnerability could have on the system, various methods that can be used to fix the vulnerability, links to available patches, vender, and other reference sites. Also, the resulting scan policy can be saved to perform a scan of the network using the selected policy.
21) Selecting Tasks Using Individual CVE Names <CR_A.2.6>
Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CVE names (recommended):
The steps for browsing and selecting are explained in number 20. Deselecting can be done by un-checking the checkbox next to the CVE name.
22) Non-Support Notification for a Requested CVE Name <CR_A.2.7>
Provide a description of how the tool notifies the user that task associated to a selected CVE name cannot be performed (recommended):
Secuguard NSE notifies the user by logs that can be viewed in the GUI or by text file.
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):
In all areas of the GUI, the customer can view the corresponding CVE names for each Secuguard NSE vulnerability entries. Electronic document formats of Word, Excel, HTML, PDF, etc. are supported. Within the Reporting section of the GUI, specific CVE text can be searched using the search feature.
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):
In all areas of the GUI including reports, the customer can view the corresponding CVE names for each Secuguard NSE vulnerability entries.
33) Electronic Document Element to CVE Name Mapping <CR_B.3.3>
Provide example documents that demonstrate the mapping from the capability's individual elements to the respective CVE name(s) (recommended):
In all areas of the GUI including reports, the customer can view the corresponding CVE names for each Secuguard NSE vulnerability entries.
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 use the search feature of the Scan Policy Editor to search for the specific CVE names or press the View All button to view all supported CVE names. Then by clicking on the CVE name in interest, the user can view the detailed description of the vulnerability, the impact the vulnerability could have on the system, various methods that can be used to fix the vulnerability, links to available patches, vender, and other reference sites. Also, the resulting scan policy can be saved to perform a scan of the network using the selected policy.
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):
In all areas of the GUI including reports, the customer can view the corresponding CVE names for each Secuguard NSE vulnerability entries.
36) GUI Export Electronic Document Format Info <CR_B.4.3>
Provide details about the different electronic document formats that you provide for exporting or accessing CVE-related data and describe how they can be searched for specific CVE-related text (recommended):
CVE-related data can be accessed by the Report Viewer included in the GUI and can be exported into Word, Excel, HTML, PDF, etc formats. The Report Viewer supports search functions where the user can search for CVE-related text. For searching within the exported documents, the respective program's search features can be used.
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: Song, Young Ho
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: Song, Young Ho
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: Song, Young Ho
Title: CEO