CWE

Common Weakness Enumeration

A Community-Developed List of Software Weakness Types

CWE/SANS Top 25 Most Dangerous Software Errors
Home > Compatibility > CWE-Compatible Products and Services  
ID

Name of Your Organization:

MathWorks, Inc.

Web Site:

http://www.mathworks.com/

Adopting Capability:

Polyspace Bug Finder

Capability home page:

http://www.mathworks.com/products/polyspace-bug-finder/

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

Licensed customers of Polyspace Bug Finder can download the product from their Account page (https://www.mathworks.com/mwaccount).

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

The version of CWE used to do the mapping is given in the tool's documentation, more precisely in the chapter "Mapping Between CWE Identifiers and Defects":

CVE and Compatibility Documentation

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

There are two product releases of Polyspace Bug Finder in a year (one in March, one in September). Updates of the mapping occur with every product release.

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

N/A

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

The chapter "Common Weakness Enumeration from Bug Finder Defects" of the Polyspace Bug Finder's user guide describes CWE, with links to the official website.

This chapter also presents CWE compatibility.

CVE and Compatibility Documentation

This chapter is available online for licensed customer at this location: http://www.mathworks.com/help/bugfinder/ug/bug-finder-defects.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):

Polyspace Bug Finder users can filter defects by CWE identifiers. The procedure is detailed in the documentation:

http://www.mathworks.com/help/bugfinder/ug/find-cwe-identifiers-from-defects.html#bud4mrj

CVE and Compatibility Documentation

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

The documentation explains how to see the CWE entries associated with a defect:

CVE and Compatibility Documentation

CVE and Compatibility Documentation

This chapter is accessible online for licensed users at this location: http://www.mathworks.com/help/bugfinder/ug/find-cwe-identifiers-from-defects.html

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 Polyspace Bug Finder 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):

Filters can be used to locate defects by CWE Identifiers. The filters can be selected from a list:

CVE and Compatibility Documentation

Or by using a text entry:

CVE and Compatibility Documentation

The filter(s) will then be applied to the list of defects:

CVE and Compatibility Documentation

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

A CWE report can be generated from the product results. A chapter lists the defects identified by the tool and gives the associated CWE identifiers:

CVE and Compatibility Documentation

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

Polyspace Bug Finder users can find the mapping in the product user's guide, on the page "Mapping between CWE Identifiers and Defects".

http://www.mathworks.com/help/bugfinder/ug/mapping-between-cwe-identifiers-and-defects.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):

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

Bug Finder's UI provides an optional column in the Results Summary window that shows, for each defect the associated CWE identifier(s), if the mapping exists:

CVE and Compatibility Documentation

CVE and Compatibility Documentation

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

N/A

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

N/A

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 Polyspace Bug Finder 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):

MathWorks provides both an online and a pdf version of the product documentation for licensed users.

The pdf version can be downloaded from the online documentation.

CVE and Compatibility Documentation

Users can search for specific CWE-related text in the online documentation thanks to a Search field, present on every page of the documentation.

CVE and Compatibility Documentation

Filters are available to refine the search by product.

CVE and Compatibility Documentation

For the pdf version, users can search the Polyspace Bug Finder User's guide for cwe-related entries.

CVE and Compatibility Documentation

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

The Bug Finder documentation provides a table that lists the security elements associated to the mapped CWE identifiers:

CVE and Compatibility Documentation

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

The same table as the one described in the answer to <CR_B.3.2> can be used to know the mapping from Polyspace Bug Finder defects to CWE-IDs.

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

Users can export the Bug Finder results into a specific CWE report:

CVE and Compatibility Documentation

Users will find in this report the list of defects and their associated CWE-IDs:

CVE and Compatibility Documentation

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: Patrick Munier

Title: Development 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: Patrick Munier

Title: Development 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: Patrick Munier

Title: Development Manager


More information is available — Please select a different filter.
Page Last Updated: January 17, 2017