Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

SECURITY-DATABASE

Web Site:

http://www.security-database.com/

Compatible Capability:

Security-Database Web Services

Capability home page:

http://www.security-database.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):

Available through different pages (examples):

http://www.security-database.com/cwe.php (list)
http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)
http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

Map Currency Indication <CR_6.1>

Describe how and where your capability indicates the most recent CWE content used to create or update its mappings (required):

CWE 1.8, which will be updated soon to 2.1 (for our CWE Listing: http://www.security-database.com/cwe.php) but we use up-to-date information to publish information on every alerts.

Map Currency Update Approach <CR_6.2>

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

Mapping is updated for every alert in our repository each time a modification is made on the alert. All information’s on each alert are dynamic and based on MITRE/NVD Repository.

Example: http://www.security-database.com/detail.php?alert=CVE-2007-1133

MAP CURRENCY UPDATE TIME <CR_6.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 CWE content (required):

SECURITY-DATABASE publishes information on each alert when they are modified.

For Mapping in Alerts here is an example:
http://www.security-database.com/detail.php?alert=CVE-2007-1133
We use a Last Modification (Ex: 2007-03-02)

CWE AND COMPATIBILITY DOCUMENTATION <CR_5.1>

Provide a copy, or directions to its location, of where your documentation describes CWE and CWE compatibility for your customers (required):

Documentation is provided on http://www.security-database.com/about.php?type=cwe

DOCUMENTATION OF FINDING ELEMENTS USING CWE IDENTIFIERS <CR_5.2>

Provide a copy, or directions to its location, of where your documentation describes the specific details of how your customers can use CWE identifiers to find the individual security elements within your capability's repository (required):

As we rely on Web technologies to supply information, CVEs could be reached by several techniques:

http://www.security-database.com/about.php?type=cwe (Doc)
http://www.security-database.com/cwe.php (list)
http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)
http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)
http://www.securty.database.com/search.php (for search engine)

DOCUMENTATION OF FINDING CWE IDENTIFIERS USING ELEMENTS <CR_5.3>

Provide a copy, or directions to its location, of where your documentation describes the process a user would follow to find the CWE identifiers associated with individual security elements within your capability's repository (required):

As we rely on Web technologies to supply information, users could use the search option: http://www.security-database.com/search.php

However, other direct ways are permitted:

http://www.security-database.com/about.php?type=cwe (Doc)
http://www.security-database.com/cwe.php (list)
http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)
http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

DOCUMENTATION INDEXING OF CWE-RELATED MATERIAL <CR_5.4>

If your documentation includes an index, provide a copy of the items and resources that you have listed under "CWE" in your index. Alternately, provide directions to where these "CWE" items are posted on your web site (recommended):

An example is seen at these locations:

http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)
http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)

http://www.security-database.com/about.php?type=cwe (Doc)
http://www.security-database.com/cwe.php (list)
http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)

Type-Specific Capability Questions

FINDING TASKS USING CWE IDENTIFIERS <CR_A.2.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CWE identifier (required):

User can find additional information with the search option at: http://www.security-database.com/search.php

FINDING CWE IDENTIFIERS 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 CWE identifier for the individual security elements in the report (required):

Each Alert that has a CWE will be displayed under CWE paragraph:

http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.2.3>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that the owner claims the tool is effective at locating in software (required):

Same as <CR_A.2.2>, include the search function, and cwe listing.

FINDING TASKS USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CWE identifier (required):

Each Alert that has a CWE will be displayed under CWE paragraph:

http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

User can find additional information using the search function at: http://www.security-database.com/search.php

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the tool allows the user to determine the associated CWE identifier for the individual security elements in the report (required):

Please see answer to <CR_A.2.2>. Access to the list of CWE, http://www.security-database.com/cwe.php (( Menu: Solution -> Security Classification -> CWE))
And directly to a CWE: http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.3.3>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that the owner claims the tool is effective at locating in software (required):

Please see answer to <CR_A.3.3>.

GETTING A LIST OF CWE IDENTIFIERS ASSOCIATED WITH TASKS <CR_A.3.6>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that are associated with the tool's tasks (recommended):

Security-Database Web Site V4.0 - Yes (http://www.security-database.com/) Security-Database vDNA (Vulnerability DNA) 1.3beta - Yes (http://www.security-database.com/vdna.php)

FINDING ONLINE CAPABILITY TASKS USING CWE IDENTIFIERS <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 CWE identifier or through an online mapping that links each element of the capability with its associated CWE identifier(s) (required):

As we rely on Web technologies to supply content, users can find additional information using the search function at: http://www.security-database.com/search.php

Each Alert that has a CWE will be displayed under CWE paragraph:

http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

Access to the list of CWE, http://www.security-database.com/cwe.php (( Menu: Solution -> Security Classification -> CWE))
And directly to a CWE: http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)

ONLINE CAPABILITY INTERFACE TEMPLATE USAGE <CR_A.4.1.1>

Access to the list of CWE, http://www.security-database.com/cwe.php (( Menu: Solution -> Security Classification -> CWE))
And directly to a CWE: http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)

Or directly on Alerts:

http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

ONLINE CAPABILITY CGI GET METHOD SUPPORT <CR_A.4.1.2>

Yes.

FINDING CWE IDENTIFIERS USING ONLINE CAPABILITY ELEMENTS <CR_A.4.2>

Report is based on Alerts
Each Alert that has a CWE will be displayed under CWE paragraph:

http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE<CR_A.4.3>

Access to the list of CWE, http://www.security-database.com/cwe.php (( Menu: Solution -> Security Classification -> CWE))
And directly to a CWE: http://www.security-database.com/cwe.php?name=CWE-130 (CWE individual)

ONLINE CAPABILITY ELEMENT TO CWE IDENTIFIER MAPPING<CR_A.4.5>

N/A

ELECTRONIC DOCUMENT FORMAT INFO <B.3.1>

Provide details about the different electronic document formats that you provide and describe how they can be searched for specific CWE-related text (required):

http://www.security-database.com/about.php?type=cwe

ELECTRONIC DOCUMENT LISTING OF CWE IDENTIFIERS <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 CWE identifiers are listed for each individual security element (required):

http://www.security-database.com/cwe.php

ELECTRONIC DOCUMENT ELEMENT TO CWE IDENTIFIER <CR_B.3.3>

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

Each Alert that have a CWE, will be display under CWE paragraph:

http://www.security-database.com/detail.php?alert=CVE-2004-0568 (CWE in CVE Alert)
http://www.security-database.com/detail.php?alert=MS04-043 (CWE in MS Alert)

FINDING ELEMENTS USING CWE IDENTIFIERS 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 CWE identifier(s) (required):

http://www.security-database.com/cwe.php (Search option)
http://www.security-database.com/search.php (SD Search Engine)
http://www.security-database.com/cwe.php? (SD Search Engine)
http://www.security-database.com/cwe.php?name=CWE-4 (Directly)

As we rely on Web technologies to supply information, user can find additional information with the search function at: http://www.security-database.com/search.php

GUI ELEMENT TO CWE IDENTIFIER MAPPING <CR_B.4.2>

Briefly describe how the associated CWE identifiers are listed for the individual security elements or discuss how the user can use the mapping between CWE identifiers and the capability's elements, also describe the format of the mapping (required):

See answer to <CR_A.2.2>.

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 CWE-related data and describe how they can be searched for specific CWE-related text (recommended):

See answer to <CR_A.2.2>.

STATEMENT OF COMPATIBILITY <CR_2.11>

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 CWE Compatibility Requirements as well as all of the additional mandatory CWE 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 I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Picuira Benjamin

Title: Security-Database Core Team Leader and CEO

STATEMENT ON FALSE-POSITIVES AND FALSE-NEGATIVES <CR_B.2.10> and/or <CR_B.3.7>

FOR TOOLS AND SERVICES 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 I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Picuira Benjamin

Title: Security-Database Core Team Leader and CEO