Name of Your Organization:
SECURITY-DATABASE
Web Site:
Compatible Capability:
Security-Database Web Site
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):
All of our capability is available in our Web Site at http://www.security-database.com/
Public users can access synthetic information through:
- Web server
- Dashboard page
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):
CVEs entries are always displayed with an update DATE:
Example: http://www.security-database.com/detail.php?alert=CVE-2007-1133Example: First Publication: 2007-02-26
Example: Last Modification: 2007-03-02
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):
Our update cycle are 6 hours. We update our repository based on NVD CVE XML feed. Due to a complex mapping in our database, we use fingerprint on alerts and update only when needed. We also do a full CVE update (2003-20XX) once a month to be sure we do not miss a thing.
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):
Every 6 hours we add/update new CVE alerts based on NVD XML feeds.
Map Content Selection Criteria <CR_5.4>
Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):
Due to our complex Security-Database mapping technologies, we use CVE Identifier and crosslink to all other sources that we have to be sure this CVE must be added into our repository.
Map Currency Update Mechanism <CR_5.4>
Describe the mechanism used for reviewing CVE for content changes (required):
Complex fingerprint based on NVD CVE Feeds and internal sources.
Map Content Source <CR_5.5>
Describe the source of your CVE content (required):
Gathering from NVD web site nvd.nist.gov, and other sources to be more accurate.
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):
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):
As we rely on Web technologies to supply information, CVEs could be find in the following ways:
- In the "CVE list", ones can use the search form (type directly a CVE name).
- In the search page (For a specific alert, the search engine is less powerful because of the indexation process latencies.)
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):
As we rely on Web technologies to supply content, user can find the information using http://www.security-database.com/view-all.php?date=All&sev=All&type=cve and http://www.security-database.Com/search.php
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):
An example would be:
http://www.security-database.com/detail.php?alert=RHSA-2007:0079CVEs are listed below with hypertext link to their entries:
INTERNAL SOURCES (Detail)
Name/Severity/Base Score/Impact Score/Exploit Score/Attack Range/Attack Complexity/Authentication:
- CVE-2007-0777 Critical (Critical) 9.3 10 8.6 Network Medium None Required
- CVE-2007-0981 High (High) 7.5 6.4 10 Network Low None Required
- CVE-2007-0780 Medium (Medium) 6.8 6.4 8.6 Network Medium None Required
- CVE-2007-0009 Medium (Medium) 6.8 6.4 8.6 Network Medium None Required
- CVE-2007-0008 Medium (Medium) 6.8 6.4 8.6 Network Medium None Required
- CVE-2007-0779 Medium (Medium) 6.4 4.9 10 Network Low None Required
- CVE-2007-0996 Medium (Medium) 5.8 4.9 8.6 Network Medium None Required
- CVE-2007-0778 Medium (Medium) 5.4 6.9 4.9 Network High None Required
- CVE-2006-6077 Medium (Medium) 5 2.9 10 Network Low None Required
- CVE-2007-0995 Medium (Medium) 4.3 2.9 8.6 Network Medium None Required
- CVE-2007-0800 Medium (Medium) 4.3 2.9 8.6 Network Medium None Required
- CVE-2007-0775 Low (Low) 3.7 6.4 1.9 Local High None Required
Each CVE is reached individually for more information.
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):
User can find additional information with the search option at: http://www.security-database.com/search.php
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):
In a specific CVE alert:
Example: http://www.security-database.com/detail.php?alert=CVE-2007-0219We provide related information as well as other alerts from Microsoft, Redhat, Sun, Debian...:
INTERNAL RELATED ALERTS
Source Name Severity Title
Microsoft MS07-016 (High) This update resolves several newly discovered, pub...In individual Alerts:
Example: http://www.security-database.com/detail.php?alert=RHSA-2007:0088We provide CVE alerts related to:
INTERNAL SOURCES (Detail)
Name/Severity/CVSS Base Score/Attack Range/Attack Complexity/Authentication:
- CVE-2007-0910 Critical (Critical) 10 10 10 Network Low None Required
- CVE-2007-0909 High (High) 7.5 6.4 10 Network Low None Required
- CVE-2007-0906 High (High) 7.5 6.4 10 Network Low None Required
- CVE-2007-0908 Medium (Medium) 5 2.9 10 Network Low None Required
- CVE-2007-0907 Medium (Medium) 5 2.9 10 Network Low None Required
- CVE-2007-0988 Medium (Medium) 4.3 2.9 8.6 Network Medium None Required
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):
See answer to <CR_A.2.2>. Same as in search function.
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):
User can find the information using the search function at: http://www.security-database.com/search.php
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):
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):
Web service: http://www.security-database.com
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):
As we rely on Web technologies to supply content, user can find the information using http://www.security-database.com/view-all.php?date=All&sev=All&type=cve and http://www.security-database.Com/search.php.
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):
The usual format to retrieve info about a specific CVE is given below:
http://www.security-database.com/detail.php?alert=CVE-YYYY-NNNN
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):
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):
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):
On the Web site with the search function: http://www.security-database.com/search.php
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):
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):
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):
As we rely on Web technologies to supply content, user can find the information using http://www.security-database.com/view-all.php?date=All&sev=All&type=cve and http://www.security-database.Com/search.php.
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):
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):
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: Picuira Benjamin
Title: Security-Database Core Team Leader and CEO
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: Picuira Benjamin
Title: Security-Database Core Team Leader and CEO
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: Picuira Benjamin
Title: Security-Database Core Team Leader and CEO
