|
|
Name of Your Organization:
VirtuStream, Inc.
Web Site:
Compatible Capability:
Analytic Continuous Monitoring Engine (ACE)
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):
The information is made available in the Analytic Continuous Monitoring Engine (ACE) application the main feature that provides this information is the vulnerability management feature which can be accessed on demo.virtustream.com.
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 most recent CVE content used is displayed in ACE's Vulnerability Management - CVE Search Capability the CVE Published and Update date is displayed.
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):
The CVE updating capability allows any frequency of updates based on the end user organization's CVE currency requirement, e.g., Daily, Weekly, or other.
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):
The frequency is user/organization defined.
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 ID is utilized to correlate the relevant CVE based on ingested vulnerability discovery scan data from vulnerability scanning software used to scan system assets this correlation is used to identify risk level for each vulnerability discovery.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
The answer in question #3 is the mechanism that a user can use to see when the CVE has been updated and content changed.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
Our users are directed to download the xml file(s) for all or updates from: https://cve.mitre.org/data/downloads/
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):
This is provided in the product in the form of CVE references in the reports, user manual, description, and database.
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):
Section 1.12.2 Search CVE in ACE's User Guide describes the process to search the CVE database. See the user guide "VTACE-USG004 ACE - User Guide Volume - I Build 02072014.pdf".
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):
Section 1.12.2 Search CVE in ACE's User Guide describes the process to search the CVE database. See the user guide "VTACE-USG004 ACE - User Guide Volume - I Build 02072014.pdf".
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):
Yes in the documentation index. See the user guide "VTACE-USG004 ACE - User Guide Volume - I Build 02072014.pdf".
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can find associated elements in the capability by looking for their associated CVE name (required):
In the ACE screen shot shown below a user can associate/find CVE-2005-1794 with a given asset SAP-CRM-DB-Server in their information system boundary.
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):
Using ACE's Custom Vulnerability Reports capability an end user is able to query and report on any security element for all assets in the information system described in Section 3.5.1 Custom Vulnerability Reports of the user guide: "VTACE-USG005 ACE - User Guide Volume - II Build 02072014.pdf".Example Search:
Example report:
Getting a List of CVE Names Associated with Tasks <CR_A.5.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 capability’s tasks (recommended):
Using ACE's Custom Vulnerability Reports capability described in Item #28 or #27 will allow a user to see CVE names associated with assets and systems.
In section 1.3.17.4 Tasks Tab of the user guide "VTACE-USG005 ACE - User Guide Volume - II Build 02072014.pdf" describes how to see all the vulnerability tasks with associated CVEs.
Selecting Tasks Using Individual CVE Names <CR_A.5.6>
Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the capability by using individual CVE names (recommended):
In section 1.3.17.4 Tasks Tab of the user guide "VTACE-USG005 ACE - User Guide Volume - II Build 02072014.pdf" describes how to see and manage vulnerability tasks.
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):
ACE allows output as Excel, Word Document, or PDF.
Using ACE's Custom Vulnerability Reports capability described in Item #28 or #27 will allow a user to search for specific CVE-related text.
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):
See "CustomVulReportResult7-9-2014.pdf".
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):
ACE allows the user to search for elements by CVE name/ID:
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):
The end user is able to map a given CVE ID to their associated information assurance security control in the GUI. The format of the mapping is based on NIST 800-53 Security Control ID to CVE ID format.
See section 1.13 CVE IA Mappings of the user guide "VTACE-USG004 ACE - User Guide Volume - I Build 02072014.pdf ".
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: Gregsie Leighton
Title: Product Manager
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: Gregsie Leighton
Title: Product 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: Gregsie Leighton
Title: Product Manager