Name of Your Organization:

Critical Watch

Web Site:

www.criticalwatch.com

Compatible Capability:

FusionVM Managed Service

Capability home page:

http://www.criticalwatch.com

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):

Critical Watch's FusionVM Managed Service vulnerability management solution is delivered as a remote managed service with deployable internal FusionVM appliances for scanning private networks. The FusionVM Portal interface is accessed through a secure Web Browser.

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 FusionVM solution is updated daily from continual streams of vendor updates, advisories and other information feeds such as OSVB & NVDB and cve.mitre.org. As a result of this daily dynamic process, the FusionVM Vulnerability Database is always up-to-date.

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 FusionVM solution is updated daily from continual streams of vendor updates, advisories and other information feeds such as OSVB & NVDB and cve.mitre.org. As a result of this daily dynamic process, the FusionVM Vulnerability Database is always up-to-date.

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):

The FusionVM Vulnerability Database is always up-to-date, which is documented in the FusionVM Technical Specification Document.

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):

Chapter 5 of the FusionVM User Guide, located in the online Help section of the application, details the definition of CVE, the compatibility standards, how users can search by and access CVE information, as well as an explanation of how FusionVM utilizes CVE.

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):

Chapter 5 of the FusionVM User Guide, located in the online Help section of the application, details the definition of CVE, the compatibility standards, how users can search by and access CVE information, as well as an explanation of how FusionVM utilizes CVE.

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):

Chapter 5 of the FusionVM User Guide, located in the online Help section of the application, details the definition of CVE, the compatibility standards, how users can search by and access CVE information, as well as an explanation of how FusionVM utilizes CVE.

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 FusionVM User Guide details CVE in the index:

CVE Compatibility

How does FusionVM use CVE?

This information can be found in the FusionVM User Guide found by clicking the help icon when logged into the FusionVM portal

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):

In every vulnerability report record with a CVE mapping the user has access to an html link to the correct CVE web page for that CVE record which clearly states that a record is a candidate that is under review and not yet approved. See Figure 1 and 1a below.

Figure 1

Figure 2

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):

In addition to the report detail shown in question 11 above, the FusionVM User Guide explains in Chapter 5, pg 55 the differences between candidates and entries.

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):

The FusionVM Vulnerability Database is updated on a daily basis with information from CAN to CVE which is immediately available via the FusionVM Portal.

Type-Specific Capability Questions

15) 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):

Login to FusionVM
Select "Reports"
Select "By Risk" Sub-Tab
Expand a job or node
Choose a specific Exposure
The Associated CVE names are listed

16) 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):

Login to FusionVM
Select "Reports"
Select "By Risk" Sub-Tab
Expand a job or node
Choose a specific Exposure
The Associated CVE names are listed

17) 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):

Login to FusionVM
Select "Research"
Select "Exposures" Sub-Tab
Click "Get Exposures"
The Associated CVE names are listed

21) 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):

Login to FusionVM
Select "Research"
Select "Exposures" Sub-Tab
Click "Locate Exposures: CVE"
Users can search for coverage by CVE

22) 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):

Login to FusionVM
Select "Reports"
Select "By Risk" Sub-Tab
Expand a job or node
Choose a specific Exposure
The Associated CVE names are listed

24) 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):

Login to FusionVM
Select "Research"
Select "Exposures" Sub-Tab
Click "Locate Exposures: CVE"
Users can search for coverage by CVE

27) 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):

Login to FusionVM
Select "Reports"
Select "By Risk" Sub-Tab
Expand a job or node
Choose a specific Exposure
The Associated CVE names are listed

29) 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):

FusionVM users can choose to export reports from the FusionVM portal (Figure 5). The exported output (MS Excel) does include CVE name as a field. Users can search the exported MS Excel sheet for particular CVE names as well as sort by CVE names. FusionVM Users can also opt to receive offline pdf reports (Figure 5). These reports also contain the CVE names for each exposure detail that applies. Users can search the pdf document using the text search function to find specific CVE names.

Figure 5

30) 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):

32) 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):

Enter CVEID for search...

33) 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 each exposure detail the CVE name as well as an active hyperlink to the CVE website are provided for the reader.

34) GUI Export Electronic Document Format Info <CR_B.4.3>

Users can export reports in MS Excel and CSV, as well as receive encrypted pdf reports. Both of which is searchable by CVE name using text search and sorting within those programs.

35) 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: Nelson Bunker

Title: CISO & CTO

36) 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: Nelson Bunker

Title: CISO & CTO

37) 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: Nelson Bunker

Title: CISO & CTO