Name of Your Organization:

netForensics, Inc.

Web Site:

www.netForensics.com

Compatible Capability:

nFX Open Security Platform (nFX OSP)

Capability home page:

http://www.netforensics.com/nfxosp.asp
General Capability Questions

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

The product is sold direct and thru resellers. It is also sold as OEM by Cisco as CiscoWorks SIMS.
Mapping Questions

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

Updated weekly. The version is indicated in the Administration interface when the update is applied. Updated are packaged by netForensics.

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

Weekly.

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

We say that we update CVE/ICAT data as soon as device vendors release updates to their devices with signature that map to CVE/CAN IDs.
Documentation Questions

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

The top of page 163 of the User Guide shown below addresses this question.

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

The middle of page 163 of the User Guide shown above in response to
question 7 addresses this question.

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 bottom of page 163 and top of page 164 of the User Guide shown below addresses this question.

An example of a report showing CVE names in a report, Figure 7 in the User Guide, is shown below.

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

In addition to the documentation shown above the discussion shown below addresses this question.

Candidate Support Questions

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

Candidates are used as well as proper CVEs. Candidates are shows with a CAN tag, while CVEs are shown with a CVE tag. See the top of 163 of the User Guide shown above in response to question 7.

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

Candidates are used as well as proper CVEs. Candidates are shows with a CAN tag, while CVEs are shown with a CVE tag. See the top of 163 of the User Guide shown above in response to question 7.

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

As an updated CVE is imported the CAN entries that were 'promoted' are updated, retaining the older demarcation as well.

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

Same as searching for CVEs. See the middle of page 163 of the User Guide shown above in response to question 7.

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

Same as searching for CVEs. See the middle of page 163 of the User Guide shown above in response to question 7.

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

We show the date of the last update.

Type-Specific Capability Questions

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

A user can define a filter for a report on vulnerabilities. Such filter can include scanner vendor vulnerability IDs as well as CVE/CAN IDs.

In addition, a search in the bundled vulnerability knowledge base is possible based on CVE/CAN IDs.

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

A user can define a filter for a report on vulnerabilities. Such filter can include scanner vendor vulnerability IDs as well as CVE/CAN IDs.

In addition, a search in the bundled vulnerability knowledge base is possible based on CVE/CAN IDs.

Media Questions

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

Documentation PDFs can be searched for CVEs. HTML knowledge base documents can be searched.
Graphical User Interface (GUI)

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

Same as described above; the user can search vulnerability data by CVE. See the middle of page 163 of the User Guide shown above in response to question 7.

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

Same as described above; the user can search vulnerability data by CVE. See the middle of page 163 of the User Guide shown above in response to question 7.

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 can export reports containing CVE tags into HTML, XML, CSV, PDF, etc.
Questions for Signature

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: Anton Chuvakin

Title: Security Strategist

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: Anton Chuvakin

Title: Security Strategist

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: Anton Chuvakin

Title: Security Strategist

Page Last Updated or Reviewed: April 28, 2016