|
|
Name of Your Organization:
NileSOFT Ltd.
Web Site:
Adopting Capability:
Secuguard Web Security Explorer (WSE) Webscan
Capability home page:
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 WSE shows vulnerability assessment information from the main auditing screen, reporting, and policy manager.
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 WSE is displayed in the Policy Editor window:
Map 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):
NileSOFT updates the vulnerability database for Secuguard WSE at least once a month and provides additional updates when necessary. The vulnerability database is updated with the latest version of CVE.
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):
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 WSE and its vulnerability database support English, Korean, 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.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
The CVE content applied to Secuguard WSE is selected based on the risk of vulnerabilities and the popularity of applications.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
We check CVE content from CVE website weekly, if there is any change, we will update in our system Secuguard WSE update is performed via a secured HTTPS. After finishing the update, the updated file is verified by an integrity mechanism.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
The latest CVE content mainly comes from CVE website bulletins.
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) -> 5. Product Update -> CVE Compatibility.
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.
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.
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.
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):
Step 1) Select "Check List Management" for the search category.
Step 2) Click on the "Show as list" tab.
Step 3) "Enter the search criteria -> Select search range -> Press the search button" to view the descriptions, impact, remedy of the selected vulnerability item and apply the results to the webserver to scan for the selected vulnerability items.
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):
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.
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 WSE enter the "CVE" in the textbox and by pressing the "Search" button in the Scan Policy Editor after selecting the "Show as list" tab.
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 web using the selected policy.
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.
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 WSE notifies the user by logs that can be viewed in the GUI or by text file.
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 WSE 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.
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 WSE vulnerability entries.
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 WSE vulnerability entries.
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.
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 WSE vulnerability entries.
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.
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: Alex YoungHo Song
Title: CEO
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: Alex YoungHo Song
Title: CEO
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: Alex YoungHo Song
Title: CEO