CWE

Common Weakness Enumeration

A Community-Developed List of Software & Hardware Weakness Types

2021 CWE Most Important Hardware Weaknesses
CWE Top 25 Most Dangerous Weaknesses
Home > Compatibility > CWE-Compatible Products and Services  
ID

Name of Your Organization:

Synopsys Inc.

Web Site:

https://www.synopsys.com/software-integrity.html

Compatible Capability:

Coverity

Capability home page:

https://www.synopsys.com/software-integrity/security-testing/static-analysis-sast.html

General Capability Questions

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 can be deployed in an on-premise, air-gapped environment, or in the cloud. Customers use Coverity Connect — Coverity’s UI — to view and triage issues found by Coverity’s analysis.

Mapping Questions

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 CWE coverage capabilities are continuously updated here:

https://www.synopsys.com/software-integrity/security-testing/static-analysis-sast/coverity-cwe.html

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 include new security checkers to find more CWEs in more programming languages.

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, which happens once in the Spring and once in the Fall. Customers have grown to understand an expect this.

Documentation Questions

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

Section 2.2.4 of the Coverity Connect Use and Administration Guide introduces CWE support as a useful tool in understanding the impact of a defect:

Coverity’s CWE capability mapping is published on our public web site at: https://www.synopsys.com/software-integrity/security-testing/static-analysis-sast/coverity-cwe.html

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

Section 2.4.2.1.1. of the Coverity Connect Use and Administraton Guide describes how to filter defects by various fields including the CWE ID:

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

Please see CR_5.1 – 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 and every defect report screen.

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

Tool 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 of Coverity. 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, and save view. The view can now be viewed by the current user and other users who have had the view shared with them.

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

The Coverity Security Report shows the highest impact security weaknesses identified in the analyzed project. Each finding includes the associated CWE identifier as well as issue severity, description, and remediation advice:

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 can obtain a listing of all of the CWE identifiers Coverity can find from the Synopsys Software Integrity website at: https://www.synopsys.com/software-integrity/security-testing/static-analysis-sast/coverity-cwe.html

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 that users can use to understand how Coverity’s findings map to specific CWE identifiers.

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 the “+” button to create a new report

Step 2: Select desired CWE-IDs from CWE filter

Enter 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.

Media Questions

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

Users can obtain a listing of all of the CWE identifiers Coverity covers on the Synopsys Software Integrity website at: https://www.synopsys.com/software-integrity/security-testing/static-analysis-sast/coverity-cwe.html

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

See <CR_B.3.1>

Graphical User Interface (GUI) Questions

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 <CR_5.2> and <CR_A.2.7>

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 <CR_5.2> and <CR_A.2.7>

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

N/A

Questions for Signature

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: Director of Product Management, Coverity

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: Director of Product Management, Coverity

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: Director of Product Management, Coverity

More information is available — Please select a different filter.
Page Last Updated: May 21, 2019