Name of Your Organization:
Rsam
Web Site:
Compatible Capability:
Rsam Enterprise Governance, Risk and Compliance Platform
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):
Rsam’s Vulnerability Management, Assessment, and Threat Management solutions provide customers with central mechanisms to gather, management, and report on threats and vulnerabilities within the organization. Rsam’s Risk Analytics module utilizes this data to automatically assess, measure, and manage vulnerabilities. Rsam is integrated with common vulnerability sources, security intelligence feeds, inventory systems, and more.
Each of the elements listed above include CVE references. These references are used for basic association with CVE definitions, as well as to tie together disparate vulnerability sources. Customers can also declare any additional information on top of the CVE Identifiers to allow for custom-tailored handling of specific issues associated with specific CVE entries.
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):
CVE references are pulled from multiple sources.
- Data feeds (such as security intelligence feeds) that reference CVE will provide their CVE references directly.
- Vulnerability Scanners and related tools that have mapped to CVE automatically populate their references into the Rsam mappings.
- Rsam can point directly to the online CVE source hosted in the MITRE web site, or customers can download their own copy/instance and import directly into Rsam as a CVE reference library.
This information is then used for:
- Searching
- Reporting
- Linking Disparate Sources
- Automated Handling
- Risk Analytics
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):
The most common scenario is Rsam simply consumes the vulnerability mappings made by each of the customer’s vulnerability scanner/feed products.
Customers that choose to import the CVE library directly into Rsam can do this when, and as often as desired. Rsam’s OOTB mappings are updated throughout the year, but customers can also make and manage their own CVE mappings if desired.
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):
As often as the customer desires. Data can be refreshed manually or via automated import.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
CVE Identifiers are taken from sources that are the authoritative source of how CVE maps to their own product, and which CVE Identifiers are relevant. CVEs are populated from such sources automatically or directly by customers as needed.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Rsam’s import interface has a built-in capability of auto-detecting content changes. This includes mapping to the datasource via one or more identifiers, and then comparing the other fields against the current data.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
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 documented in our printed and online user-guide in under the Findings Module Import Engine. The following shows the information from this guide as shown in the 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):
See answer to Section 4.1 above.
Rsam’s search engine includes the ability to search across any attribute (including CVE) across multiple data sources. This is all included as part of the native Attribute Search capabilities.
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):
See answer to Section 4.1 above.
Rsam’s search engine includes the ability to search across any attribute (including CVE) across multiple data sources. This is all included as part of the native Attribute Search capabilities.
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):
See answer to Section 4.1 above.. The information is included in Rsam’s online help system.
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):
Rsam’s on-screen forms and search capabilities include the ability to locate/see data by CVE name. Users can enter the CVE name as a keyword in a search string, or as a filter in a list.
The following screen shows a user search for vulnerabilities by specific CVE Names:
And another approach using a direct filter on CVE Name:
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):
When running reports, customers can specify which fields are to be shown. These include any of the CVE fields.
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 following is an example of a remediation task associated with a listing of related CVE names:
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):
All screens in Rsam include the Filter options. Users can simply choose to display only specific CVE-related items in any of their views. (See answer 13 above for more information.)
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):
Rsam’s Dynamic Notification engine can trigger email messages on any task-related events. Notifications can include CVE names as well as any other CVE reference elements in the notification.
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):
The best example is through the user of vulnerability scanners/other products that return CVE references as part of their tests and findings. Rsam can import a list of CVE IDs checked, as well as the list of CVE IDs for which there were findings. This mapping of CVE IDs comes out of the box, but customers can also make their own CVE mappings.
The list can be presented in any consumable source, including a live database, delimited file, Excel sheet, XML file, API, and more.
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):
The concept of looking for a CVE element in a report is the exact same mechanism as looking for the CVE in the search.
Customers can choose to show the details in the report, or to have the details exposed via a "clickable" link.
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):
Rsam provides the ability to search through instances of vulnerabilities, as well as searching through the CVE library itself. See Section 13 for an overview of this, and screen shots for searching by CVE Name and other CVE fields.
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):
Customers can select a CVE element as a part of the report. This can simply be a reference to the CVE ID, or any field that comes from CVE. The user selection/filter was already shown in Section 13 above.
Reports can manifest as data list, page-formatted reports, dashboard charts and more. The following examples show a filter of three CVE IDs across a range of addresses.
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):
In this scenario, user can select from a searchable list of CVEs, or use can be allowed to provide any additional entry desired (for example an answer of "n/a").
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):
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):
User can select which CVE elements to include/not include in a related report. Reports can show the CVE simply as part of the data field, or as part of a chart.
Example as data field:
Example as chart:
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):
Rsam can export data to Excel, PDF, Word, HTML, and more. Customers can choose to include CVE as text/groupings in these reporting formats. The native search functionality can be used from within those tools.
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):
All reports can show short name and/or details as desired by the customer.
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):
Rsam allows users to perform a search through the Rsam GUI. This includes using keyword search criteria as well as using dynamic filter in the GUI search screens.
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):
CVE Elements appear in the GUI for each related vulnerability. Within a vulnerability the user can see the related CVE ID, and the reverse (that is, in the CVEI-D entry, see the related vulnerabilities). These mappings can be used for searching, filtering, email notification, taking action on the findings, and more.
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: Kevin Day
Title: Chief Technology Officer
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: Kevin Day
Title: Chief Technology Officer
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: Kevin Day
Title: Chief Technology Officer
