Name of Your Organization:
SoftRun, Inc.
Web Site:
www.softrun.com
Compatible Capability:
Inciter Vulnerability Manager
Capability home page:
http://www.softrun.com/en/vulnerability_info.asp
General Capability Questions
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):
Inciter Vulnerability Manager is available from our web site
http://www.softrun.com/en/vulnerability_info.asp.
Mapping Questions
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):
At Inciter Vulnerability Manager, the most recent CVE version can be
found in "Information" tab.
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):
The CVE mapping will be updated once a month. Whenever updates are
released, the latest CVE version will be used to
create the mapping.
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):
Softrun, Inc. is publicizes that the vulnerability pattern including
the CVE mapping is updated at least once a
month in the product homepage.
Documentation Questions
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):
The documentation can be found in "CVE" chapter of the help file
which can be opened by pressing "Help" tab in
Inciter Vulnerability Manager.
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):
Users can find details in "CVE" chapter of the help file. It is
explained in "CVE Search" section.
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):
Users can find details in "CVE" chapter of the help file. It is
explained in "CVE Output" section.
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):
"CVE" chapter of the help file include the followings:
- CVE Compatible
- CVE ID
- Entry and Candidate
- CVE Search
- CVE Output
Type-Specific Capability Questions
Tool Questions
11) 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):
Inciter Vulnerability Manager provides the search function in
"Configuration" tab.
Enter the CVE name in the edit box and click "Search" button.
12) 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):
After executing a scan, detected vulnerabilities are displayed in the
list.
Double-click individual elements in the list to obtain the
associated CVE names.
CVE names will be provided as a combo box.
13) 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):
Inciter Vulnerability Manager provides the list of all CVE names that
are associated with the tool's tasks in
"Configuration" tab.
Enter "cve" in the edit box and click "Search" button.
15) 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):
Users can select tasks using individual CVE names in "Configuration"
tab by check the checkboxes next each elements
in the list or using "Select All", "Check", "Uncheck" buttons.
16) 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):
Inciter Vulnerability Manager notifies the users by displaying a
message box.
Media Questions
30) 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):
Users can export the scan results to text files by clicking
"Export(txt)" button. Search function of notepad can be
used to search CVE-related text.
31) 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):
Exported reports of Inciter Vulnerability Manager list security
elements with their details.
Graphical User Interface (GUI)
33) 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):
Inciter Vulnerability Manager provides the search function in
"Configuration" tab.
Enter the CVE name in the edit box and click Search button.
34) 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):
After executing a scan, detected vulnerabilities are displayed in the
list.
Double-click individual elements in the list to obtain the
associated CVE names.
CVE names will be provided as a combo box.
35) 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):
Users can export the scan results to text files by clicking
"Export(txt)" button. Search function of notepad can be
used to search CVE-related text.>
Questions for Signature
36) 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: Sung-Hak Choi
Title: CTO
37) 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: Sung-Hak Choi
Title: CTO
38) 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: Sung-Hak Choi
Title: CTO
|
