Name of Your Organization:

Skybox Security Inc.

Web Site:

http://www.skyboxsecurity.com

Compatible Capability:

Skybox View

Capability home page:

http://www.skyboxsecurity.com/products/index.html

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

For availability and sales inquiries, contact us through our web site - http://www.skyboxsecurity.com/contact/index.html

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

With each new dictionary version released to our customers, we provide a document describing the CVE version used in that dictionary (the repository).

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

An updated version of Skybox View Dictionary is released to our customers once a week. Between each Dictionary version release, our content team keeps track of latest CVE versions and updates the necessary information.

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

Skybox View customers can download the latest Dictionary version from our website once it is released.

In our SLA we are committed to release a dictionary version every two weeks (which is actually released once a week), and each new version reflects the changes between CVE versions.

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

See the three excerpts from the User Manual shown below.

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

See the second User Manual excerpt shown in answer to question 7.

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

See the second User Manual excerpt shown in answer to question 7.

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

Skybox View Dictionary maintains the differentiation between CVE Candidates and accepted entries by keeping the CVE/CAN ID system – candidates appear in our dictionary as CAN IDs, while accepted entries appear as CVE IDs. When a candidate is turned into an accepted entry, we update the entry in the Dictionary.

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

At the moment there is no such explanation in the guide.

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

Skybox View content team tracks changes in CVE entries on a weekly basis, and once we discover that an entry was updated from CAN to CVE, we update the data in our Dictionary. The most recent dictionary version including the CAN to CVE changes is published weekly on our website for our customers.

14) Candidate and Entry Search Support <CR_6.4>

If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's ability to look for candidates and entries by using just the YYYY-NNNN portion of the CVE names (recommended):

The User Manual provides an explanation for basic usage of the search function, which includes this ability as well, although not specifically mentioned.

15) Search Support for Promoted Candidates <CR_6.5>

If CVE candidates are supported or used, explain where and how a customer can find the explanation of your search function's support for retrieving the CVE entry for a candidate that is no longer a candidate (recommended):

There is no such search function, since CAN entries which turn into CVE are updated in our database on a weekly basis.

16) Candidate Mapping Currency Indication <CR_6.6>

If CVE candidates are supported or used, explain where and how you tell your users how up-to-date your candidate information is (recommended):

Since Skybox View provides a weekly update of the Dictionary, it is accepted that the data we provide is as updated as the last CVE version published during that week, if there was such version. The information about the latest dictionary version installed can be viewed under the 'About Skybox View' option in the Help menu.

Type-Specific Capability Questions

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

Vulnerabilities (elements) that have CVE cross reference can be found under the Analyses tab (analyses – views of the model's data derived from the database), where for each vulnerability there are several fields displayed – textual description, SkyBox View ID, CVE Catalog ID, severity and other fields. A search function can be used on each such field, and when choosing to search by the CVE Catalog ID field, the specific vulnerability that is related to that CVE/CAN id will be displayed.

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

The CVE Catalog ID field is displayed by default for each Vulnerability (element) that is displayed in Skybox View. The CVE cross reference can be viewed either in the main display table of the analyses, or in a more detailed windows that can be opened for each vulnerability.

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

It is possible to view a list of all existing vulnerabilities (elements) in the product under the Vulnerabilities by Type analysis. One of the fields displayed in this analysis is the CVE Catalog ID reference field.

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

Reports are generated in PDF format, and provide the description and title of the vulnerability, CVE Catalog ID and severity.

Specific CVE related text can be searched using the PDF search function.

32) 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 the screen shot shown in answer to question 31.

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

A screen shot of the GUI search function is shown below, showing the Find in Table search windows, where the searched field is the CVE Catalog ID field.

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

As seen below, CVE names appear as a separate column in the table showing vulnerability types. See the screen shot shown in answer to question 34.

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

We export CVE-related data in CSV format from the analyses tab.

37) 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: Moshe Meiseles

Title: CTO and VP R&D

38) 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: Moshe Meiseles

Title: CTO and VP R&D

39) 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: Moshe Meiseles

Title: CTO and VP R&D