Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Coverity, Inc.

Web Site:

http://www.coverity.com/

Compatible Capability:

Coverity Quality Advisor

Capability home page:

http://www.coverity.com/products/quality-advisor.html

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

Coverity Quality Advisor is available for licensed customers to download from their personal Customer Support Portal. Additional information about these products is available on http://www.coverity.com.

Coverity SCAN is an initiative that offers Coverity Quality Advisor FREE for use in a hosted environment by qualifying open source projects. For more information and qualification details please see http://scan.coverity.com/developers-faq.html.

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

Coverity’s publically available CWE mapping documents include the version of CWE used. The mapping documents are available here:

http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_cpp.pdf

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

Updates to Coverity’s CWE capability mappings occur with every product release, which typically includes two major releases per year — one in Spring and one in Fall.

Many of Coverity’s customers depend on Quality Advisor to eliminate the quality defects that can lead to security vulnerabilities, and Coverity’s Security Research Lab strives to keep as up to date with CWE content as possible.

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

Coverity’s CWE capability mapping updates occur with every major release and customers have grown to understand an expect this.

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

Chapter 1 of the Coverity Connect User’s Guide, "Coverity Connect Overview," describes CWE as a key concept for defect categorization:

Coverity’s CWE capability mapping is published on our public web site at:

C/C++: http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_cpp.pdf

Java: http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_Java.pdf

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

Filtering and prioritizing defects is a primary feature for Coverity Quality Advisor. Section 4.1 of the Coverity Connect User’s Guide, "Focusing the scope of your defect data" describes how to filter defects and lists CWE as an available filter:

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

Section 4.2 of the Coverity Connect User’s Guide, "Examining your defects," explains how to navigate the Coverity Connect UI and interpret the results. It specifically references the CWE for understanding the impact of the defect:

Further, the CWE Identifier is displayed in a prominent, intuitive location in the defect triage panel (upper right corner) and is available in the list of defects:

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

The Coverity documentation does not provide an index.

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

Filtering and prioritizing defects is a primary feature for Coverity Quality Advisor. Users can locate defects by CWE identifier by selecting the filter menu and entering the relevant CWE-IDs in the filter criteria:

Step 1: Right click the desired report in the list of reports (left side of screen) and select "Filters…" option.

Step 2: Enter the relevant CWE-IDs in the CWE filter box.

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

For an individual defect report the CWE-ID and link to CWE reference site is presented in a prominent location as part of the defect triage panel:

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

Users may obtain a listing of all CWE Identifiers covered by Coverity Quality Advisor from the Coverity web site at:

http://www.coverity.com/products/code-advisor/#CWEcoverage

USING CCR TO PROVIDE CLAIMED CWE IDENTIFIER COVERAGE <CR_A.2.4>

Give a detailed explanation of how a user can find the Coverage Claim Representation (CCR) XML document with all of the CWE Identifiers that the owner claims the tool is effective at locating in software (recommended):

Coverity Connect does not currently provide the CCR XML document.

GETTING A LIST OF CWE IDENTIFIERS ASSOCIATED WITH TASKS <CR_A.2.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):

Coverity Connect provides a UI for navigating and filtering a set of defects in a software project. The CWE-ID is an optional, available column in the list of defects.

To view all of the CWE Identifiers associated with a list of defects, the Administrator can enable the column for everyone or individual users may enable the column for their report:

Step 1: Enable the CWE-ID Column for a selected saved personal or global report

Step 2: The CWD-ID is now clearly visible for each defect reported by Coverity Quality Advisor.

SELECTING TASKS WITH A LIST OF CWE IDENTIFIERS <CR_A.2.7>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CWE identifiers (recommended):

Users may create a new personal or shared view/report using a list of CWE Identifiers. To do so a new view/report is created, and filters are specified. CWE-IDs may not be loaded from an external text file, however these reports are saved and easily reloaded.

Step 1: Click ‘+’ button to add a new view/report, and enter report name.

Step 2: Enter the desired CWE IDs.

SELECTING TASKS USING INDIVIDUAL CWE IDENTIFIERS <CR_A.2.8>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CWE identifiers (recommended):

Please see answer to <CR_A.2.7>

NON-SUPPORT NOTIFICATION FOR A REQUESTED CWE IDENTIFIER <CR_A.2.9>

Provide a description of how the tool notifies the user that a task associated with a selected CWE Identifier cannot be performed (recommended):

If a user searches for a CWE-ID that Coverity does not have a mapping for, there will simply be no defects returned. There is no indication in the UI that the ID is not covered.

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

Please see answer to <CR_A.2.1>

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

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

Reports may be exported in CSV or XML formats with CSV as a visible and searchable field.

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: James Croall

Title: Senior Product Manager

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: James Croall

Title: Senior Product Manager

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: James Croall

Title: Senior Product Manager