Name of Your Organization:

TMC y Cia

Web Site:

http://www.tmcycia.com

Compatible Capability:

FAV - Falcon Vulnerabilities Analysis

Capability home page:

http://analisisdevulnerabilidades.com

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

FAV service can be acquired contacting us by phone or mail. Also, our contact info can be reached at http://www.tmcycia.com or http://analisisdevulnerabilidades.com

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 TMC FAV DB is updated at the customer's location on a weekly basis with latest CVE vulnerability entries from the FAV Central Repository located at our data center. This is done the day after our FAV Central Repository is updated from cve.mitre.org.

Map Currency Update Approach <CR_5.2>

Indicate how often you plan on updating the mappings to reflect the current CVE content and describe your approach to keeping reasonably current with the CVE content when mapping them to your repository (required):

The FAV DB is updated at the customer's location on a daily basis with latest CVE vulnerability entries and CVSS scores from the FAV Central Repository located at our data center. This is done the next day after our FAV Central Repository is updated from nvd.nist.gov. Our software uses them to update the mappings in the FAV database.

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

When new CVE content is available at FAV, the FAV DB upgrades the CVE date field, which is printed to the Vulnerabilities Reports.

Map Content Selection Criteria <CR_5.4>

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

According with CVSS v2 score, FAV the following criteria:

CVSS LEVEL	FAV LEVEL
[ 10 ]	CRITICA
[ 7.0 - 9.9 ]	ALTA
[ 4.0 - 6.9 ]	MEDIA
[ 1.0 - 3.9 ]	BAJA
[ 0.0 - 0.9 ]	NOTA

Map Currency Update Mechanism <CR_5.4>

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

Downloading the current XML file from http://nvd.nist.gov and using it to modify the FAV content

Map Content Source <CR_5.5>

Describe the source of your CVE content, (i.e., we gather info from mailing lists, product change logs, software vendors' security bulletins...) (required):

Please see answer to <CR_5.4> The source used is the XML file with the corresponding CVE information. Also the last nvdcve-modified.xml with the last modifications to the CVE database is used in order to have the CVE information up to date.

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

Within the Credits -> CVE section of the FAV administrative console, details are provided regarding CVE and our CVE compatibility:

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

Within the FAV Enviroment -> WEB Services -> Search, our customers can search using CVE/CAN identifiers. This is also showed in the FAV Videos (Reportes Video).

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

Details can be found in the user manual video "FAVWEB" where our customers can see: In this example the tool found a vulnerability CVE-2007-0940 in the PC 10.10.0.229

So, in this case, clicking on the Reference ID, the browser will open the page http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0940

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

See answer to <CR_4.3>. Additionally, once the reports are made by FAV, the user can use the FAV reports environment, based on any internet browser.

In order to search for any CVE ID that has been found in a particular IP, the user should do the following:

In the TMC FAV web services window, from the FAV reports environment, select the data-mining window.

Select the required report.

Drill down the IP -> vulnerability -> References -> CVE number. It points directly to nvd.nist.gov.

Or, by entering the CVE ID in the text box of "web services" and clicking search.

The corresponding vulnerability will be searched and displayed on a new browser window.

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

Upon executing a scan, the scan results are displayed in the FAV reports environment. The user should click on "Reports". Analysis Reports and graphics are all based directly on CVE entries. Data-mining reports also have CVE entries as references as well.

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

Please see answer to <CR_A.2.1>

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

Please see answer to <CR_A.2.1>

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

At the FAV Web Environment, the user can click on "Reportes" -> IP address and it's possible something like:

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

At the FAV Web Environment, the user can click on "Reportes" -> segment address -> IP address -> Security Element and it's possible something like:

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

As the reports are displayed on a web browser, they can be saved as text or html.

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

There are reports including just short names. But searching the associated CVE name on the search tool, vulnerabilities are listed along with their full details:

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

Please see answer to <CR_A.5.1> and <CR_A.5.2>

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

Once the reports are made by FAV, the user can see the FAV Web environment, using any internet browser. See pictures on answers to <CR_4.2>, <CR_4.3>, <CR_A.2.1> and <CR_B.3.2>.

In order to search for any CVE ID that has been found in a particular IP, the user should do the following:

In the TMC FAV web services window, from the FAV reports environment, select the data-mining window.

Select the required report.

Drill down the IP -> vulnerability -> References -> CVE number. It points directly to nvd.nist.gov.

Or, by entering the CVE ID in the text box of "web services" and clicking search.

The corresponding vulnerability will be searched and displayed on a new browser window.

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 FAV uses the NVD database of CVE entries there is a one-to-one mapping between CVE names and the security elements associated with the database. See picture on answer to <CR_B.3.2>; also see the graphic format of that example:

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

FAV implements internal search functions on the NVD database (XML), displaying results to the user as txt.

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: Walter L Montes

Title: Director of Engineering

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: Walter L Montes

Title: Director of Engineering

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: Walter L Montes

Title: Director of Engineering