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:

Klocwork, Inc.

Web Site:

http://www.klocwork.com

Compatible Capability:

Klocwork Insight

Capability home page:

http://www.klocwork.com/products/insight/?source=topnav

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

Klocwork is a commercially available product that, when purchased, can be downloaded from the Klocwork Customer Support portal (https://my.klocwork.com/).

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

Each of the Klocwork/CWE mapping pages on the documentation wiki indicates the version of CWE used.

Map Currency Indication

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

Klocwork updates the CWE mappings within its products at every product release, which usually includes one major, and one minor release per calendar year. Since many of Klocwork’s customers are using the product to find security vulnerabilities in their source code, Klocwork strives to keep as up to date with CWE content as possible, and revisits this task multiple times during each release cycle.

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

Since updates to Klocwork’s CWE capability mappings occur with every release, customers have come to expect this. In addition, we typically include a CWE compatibility update in our Product Roadmaps that are delivered to customers.

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

Klocwork provides a number of pages on its documentation wiki that describes the mapping of CWE with Klocwork Insight.

For C/C++:
http://www.klocwork.com/products/documentation/current/CWE_IDs_mapped_to_Klocwork_C_and_C%2B%2B_checkers

2011 CWE-SANS Top 25 Most Dangerous Software Errors (C/C++):
http://www.klocwork.com/products/documentation/current/2011_CWE-SANS_Top_25_Most_Dangerous_Software_Errors_mapped_to_Klocwork_checkers

2010 CWE-SANS Top 25 Most Dangerous Software Errors (C/C++):
http://www.klocwork.com/products/documentation/current/2010_CWE-SANS_Top_25_Most_Dangerous_Software_Errors_mapped_to_Klocwork_checkers

For Java:
http://www.klocwork.com/products/documentation/current/CWE_IDs_mapped_to_Klocwork_Java_checkers

2011 CWE-SANS Top 25 Most Dangerous Software Errors (Java):
http://www.klocwork.com/products/documentation/current/2011_CWE-SANS_Top_25_Most_Dangerous_Software_Errors_mapped_to_Klocwork_checkers

2011 CWE-SANS Top 25 Most Dangerous Software Errors (Java):
http://www.klocwork.com/products/documentation/current/2010_CWE-SANS_Top_25_Most_Dangerous_Software_Errors_mapped_to_Klocwork_checkers

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

See question <5.1> above.

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

See question <5.1> above.

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

While CWE isn’t specifically listed in the main documentation wiki’s index, it can be found when the Reference item in the main index is selected. See screenshot below:

DOCUMENTATION INDEXING OF CWE-RELATED MATERIAL

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

Users are able to locate specific instances of CWE rules by using the ‘search’ feature within Klocwork Review (the reporting portal within Klocwork Insight). To do this, users would navigate to the Issue Management page, then within the Search field, enter taxonomy:CWE. This will show all of the CWE instances and the corresponding rule number(s) within that specific project.

FINDING TASKS USING CWE IDENTIFIERS

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

Klocwork Review is a powerful reporting tool that allows users to create custom reports on a variety of criteria. In this case, users are able to create a report (see screenshot below) that shows all of the CWE identifiers available, and in bar graph form, the number of instances they are found for each identifier within that project. Users can then drill down further by selecting whatever identifier they want to see the specific issues.

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS

In addition to this method, users are able to do a search within Klocwork Review for a specific CWE identifier. To do this, users would navigate to the Issue Management list, then enter in the search box taxonomy:cwe reference:403 (users can of course enter in any of the CWE identifiers they are interested in here, 403 was used as the example. The results they would see are shown below.

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS

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

This can be done a couple of different ways. The first way would be to consult the product documentation, which clearly shows all of the CWE rules (by development language) that are covered.

The second way to do this would be from with Klocwork Review (the reporting portal within Klocwork Insight), to navigate to the cwe.pconf.xml file in the Configuration tab. Once the cwe.pconf.xml file is opened (see screenshot below), users can clearly see what CWE rules are available. When users expand any of the CWE rules listed, they are able to see which Klocwork checkers are used to provide compatibility.

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE

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

This can be done using the same steps as identified in question <CR_A.2.1> above.

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

As mentioned in question 12, users are able to browse, select, and deselect any of the CWE identifiers through the use of Klocwork’s configuration editor. As seen in the screenshot below, users can deselect all of the Klocwork checkers for a specific CWE identifier, or only a partial set of the Klocwork checkers.

SELECTING TASKS USING INDIVIDUAL CWE IDENTIFIERS

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

Klocwork uses an online wiki-based approach for its documentation. It is within this documentation that users are able to search for specific CWE-related text.

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

Full names and titles are provided for all CWE identifiers.

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

All of the CWE identifiers in our wiki-based documentation are linked back to the actual CWE identifier page. For example, we list CWE-20 which hyperlinks to http://cwe.mitre.org/data/definitions/20.html. This behavior is consistent with all of the CWE identifiers in our documentation.

ELECTRONIC DOCUMENT ELEMENT TO CWE IDENTIFIER

In addition to this, each of our Defect pages has a section called Security Guidelines which lists all of the applicable CWE identifiers for that specific defect. Once again, the CWE identifier listed in that section is hyperlinked to its appropriate page on the mitre.org website.

ELECTRONIC DOCUMENT ELEMENT TO CWE IDENTIFIER

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

See answers to questions <CR_A.2.1> and <CR_A.2.2>.

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

CWE identifiers can be found on a number of different pages within our documentation. These pages show the mapping between CWE identifier and Klocwork defects (checkers). These pages are:

http://www.klocwork.com/products/documentation/current/CWE_IDs_mapped_to_Klocwork_C_and_C%2B%2B_checkers

http://www.klocwork.com/products/documentation/current/CWE_IDs_mapped_to_Klocwork_C_and_C%2B%2B_checkers

In addition to this, all applicable Klocwork defect pages have a section called Security Guidelines which list all of the security guidelines applicable to that defect. See question 32 for more details and screenshot.

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

.xml, .csv, and print capabilities with the appropriate print drivers (i.e., .pdf).

Questions for Signature

STATEMENT OF COMPATIBILITY <CR_2.11>

Have an authorized individual sign and date the following Compatibility Statement (required):

See answer to <CR_A.2.1> above.

"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: Alen Zukich

Title: Director of Product Management

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 specific CWE identifiers our capability reports and those CWE identifiers are as specific as possible within the available CWE repository."

Name: Alen Zukich

Title: Director of Product Management

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 and to the best of my knowledge, there are no errors in the mapping between our capability's Repository and the specific CWE identifiers our capability reports and those CWE identifiers are as specific as possible within the available CWE repository."

Name: Alen Zukich

Title: Director of Product Management


More information is available — Please select a different filter.
Page Last Updated: [an error occurred while processing this directive]