Name of Your Organization:

Black Box Corporation

Web Site:

www.blackbox.com

Compatible Capability:

Veri-NAC Appliances

Capability home page:

http://www.blackbox.com/go/veri-nac
General Capability Questions

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

Information stored in Veri-NAC is available to users of the appliance during scanning, reporting and remediation. It is also available for lookup from the built-in connection to the National Vulnerability Database (NVD).

Mapping Questions

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

Each resulting audit provides access to the database version number. The version number is also displayed in the product about box.

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

Black Box Corporation leverages a dedicated Vulnerability Research Team (VRT) that maintains the dynamic audits update engine inside the Veri-NAC appliances.

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

CVE tests are updated daily by our 7x24x365 Vulnerability Research Team (VRT).

Map Content Selection Criteria <CR_5.4>

Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):

Internally, our Audit Database uses the Common Vulnerability Scoring System (CVSS). Results are formatted to provide additional information in regards to the relevance of a CVE and the risk factor.

Map Currency Update Mechanism <CR_5.4>

Describe the mechanism used for reviewing CVE for content changes (required):

With 7x24x365 research by our Vulnerability Research Team we are able to offer extremely frequent daily updates to all Veri-NAC appliances, deployed worldwide.

Map Content Source <CR_5.5>

Describe the source of your CVE content (required):

CVE.MITRE.ORG and NVD.NIST.GOV, the National Vulnerability Database.

Documentation Questions

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

CVE compatibility is described in each report and in the secure web interface by visiting the Help -> USER GUIDE menu item, loading the PDF and browsing to pages 15, 28-29, 101-102, 129, 139, and 142-146

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

To find specific details within our CVE repository, customers need follow the instructions in the documentation by visiting the Help -> USER GUIDE menu item, loading the PDF and browsing to pages 15, 28-29, 101-102, 129, 139, and 142-146 and more quickly, by clicking Audits -> View Vulnerability Tests and Audits -> National Vulnerability Database menu items.

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

To find specific details within our CVE repository, customers need follow the instructions in the documentation by visiting the Help -> USER GUIDE menu item, loading the PDF and browsing to pages 15, 28-29, 101-102, 129, 139, and 142-146 and more quickly, by clicking Audits -> View Vulnerability Tests and Audits -> National Vulnerability Database menu items.

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

To find specific details within our CVE repository, customers need follow the instructions in the documentation by visiting the Help -> USER GUIDE menu item, loading the PDF and browsing to pages 15, 28-29, 101-102, 129, 139, and 142-146 and more quickly, by clicking Audits -> View Vulnerability Tests and Audits -> National Vulnerability Database menu items.

Type-Specific Capability Questions

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

By clicking on Workflow -> Workflow Log and then clicking on any open Report Ticket.

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

By clicking on Reports -> View Audit Results and by clicking on Query Vulnerabilities.

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

By clicking on Workflow -> Workflow Log and then clicking on any open Report Ticket. Also, by clicking on Reports -> View Audit Results and by clicking on Query Vulnerabilities.

Selecting Tasks with a List of CVE Names <CR_A.2.5>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):

By clicking on Workflow -> Workflow Log and then clicking on any open Report Ticket. Also, by clicking on Reports -> View Audit Results and by clicking on Query Vulnerabilities. Also, by clicking on Reports -> Generate Executive Reports and by clicking on Reports -> Generate Management Reports.

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

By clicking on Workflow -> Workflow Log and then clicking on any open Report Ticket.

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

Veri-NAC has a calendar and scheduling engine for all audits that are scheduled or running. If an audit cannot run, it will be logged and available under Logging -> System.

Media Questions

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

Veri-NAC appliances provide searchable HTML output, CSV, XML and PDF which can all be searched using any search tool from a google desktop to the search capability built-into Adobe Acrobat® reader.

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 CVE names are listed for each individual security element in full.

Electronic Document Element to CVE Name Mapping <CR_B.3.3>

Provide example documents that demonstrate the mapping from the capability's individual elements to the respective CVE name(s) (recommended):

The CVE names are all listed for each individual security element in full.

Graphical User Interface (GUI)

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

Click Audits -> National Vulnerability Database for specific searching (see below).

Graphical User Interface (GUI)

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 all Veri-NAC reports and audit results, the user will see the CVE description, vulnerability risk score, remediation instructions and links back to CVE.MITRE.ORG and NVD.NIST.GOV. The basic internal format used is an XML schema similar to the OVAL Schema:

GUI Element to CVE Name Mapping

With output as follows:

GUI Element to CVE Name Mapping

Which can be rendered and searched inside a web browser in both HTML and PDF formats as well as CSV and XML:

GUI Element to CVE Name Mapping

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

Veri-NAC appliances provide searchable HTML output, CSV, XML and PDF which can all be searched using any search tool from a google desktop to the search capability built-into Adobe Acrobat® reader.

GUI Export Electronic Document Format Info
Questions for Signature

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: Jim Schriver

Title: Director of New Technologies

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: Jim Schriver

Title: Director of New Technologies

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: Jim Schriver

Title: Director of New Technologies

Page Last Updated or Reviewed: April 28, 2016