Name of Your Organization:
Avatares Foundation
Web Site:
Adopting Capability:
Pandora-CSF
Capability home page:
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):
Pandora-CSF service can be acquired contacting us by phone or mail. Also, our contact info can be reached at http://www.avatares.co 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 Avatares Pandora-CSF DB is updated at the customer's location on a weekly basis with latest CVE vulnerability entries from the Pandora-CSF Central Repository located at our data center. This is done the day after our Pandora-CSF Central Repository is updated from http://nvd.nist.gov.
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 Pandora-CSF DB is updated at the customer's location on a daily basis with latest CVE vulnerability entries and CVSS scores from the Pandora-CSF Central Repository located at our data center. This is done the next day after our Pandora-CSF Central Repository is updated from nvd.nist.gov. Our software uses them to update the mappings in the Pandora-CSF 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 Pandora-CSF, the Pandora-CSF 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, Pandora-CSF the following criteria:
CVSS LEVEL Pandora-CSF 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 Pandora-CSF content.
Map Content Source <CR_5.5>
Describe the source of your CVE content (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 Pandora-CSF administrative console, details are provided regarding CVE and our CVE compatibility:
https://www.youtube.com/watch?v=KStRYM5bCYQ.
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 Pandora-CSF Environment -> WEB Services -> Search, our customers can search using CVE identifiers. This is also showed in the Pandora-CSF Videos (Reportes Video).
https://www.youtube.com/watch?v=KStRYM5bCYQ.
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 https://www.youtube.com/watch?v=KStRYM5bCYQ.
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):
N/A
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 Pandora-CSF, the user can use the Pandora-CSF 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 select the required report, then when the user drilldown up to the CVE Identifier, it points directly to nvd.nist.gov as shown in the video: https://www.youtube.com/watch?v=KStRYM5bCYQ.
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 Pandora-CSF 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. As shown in: https://www.youtube.com/watch?v=KStRYM5bCYQ.
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):
N/A
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):
N/A
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):
N/A
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):
N/A
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>.
Service’s Product Utilization Details <CR_A.3.4>
Please provide the name and version number of any product that the service allows users to have direct access to if that product identifies security elements (recommended):
N/A
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):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
Online Capability Interface Template Usage <CR_A.4.1.1>
Provide a detailed description of how someone can use your "URL template" to interface to your capability’s search function (recommended):
N/A
Online Capability CGI GET Method Support <CR_A.4.1.2>
If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):
N/A
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):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
Online Capability Element to CVE Name Mapping <CR_A.4.3>
If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CVE name(s), otherwise enter N/A (required):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
Finding Elements Using CVE Names <CR_A.5.1>
Give detailed examples and explanations of how a user can find associated elements in the capability by looking for their associated CVE name (required):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
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):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
Getting a List of CVE Names Associated with Tasks <CR_A.5.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 capability’s tasks (recommended):
N/A
Selecting Tasks with a List of CVE Names <CR_A.5.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):
N/A
Selecting Tasks Using Individual CVE Names <CR_A.5.6>
Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the capability by using individual CVE names (recommended):
N/A
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):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
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):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
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):
N/A
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 Pandora-CSF, the user can see the Pandora-CSF Web environment, using 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 AVATARES Pandora-CSF web services window, from the Pandora-CSF reports environment, select the data-mining window.The corresponding vulnerability will be searched and displayed on a new browser 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.
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):
Please see video at https://www.youtube.com/watch?v=KStRYM5bCYQ.
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):
N/A
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 Ortega
Title: Full stack dev
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 Ortega
Title: Full stack dev
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 Ortega
Title: Full stack dev
