Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

AbsInt Angewandte Informatik GmbH

Web Site:

www.absint.com

Compatible Capability:

Astrée

Capability home page:

http://www.absint.com/astree

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 Astrée are provided download links to the latest versions of the software.

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 content used and referenced is given in the tool's user manual. The user manual contains a dedicated chapter on CWE describing which weaknesses are addressed by Astrée's rule checking. This chapter always states the referenced CWE version.

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 major releases per year; in April and October. The mappings are updated with each such major 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):

There are two major releases per year, usually in April and October. Mappings are updated at least with such a major release.

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

This description can be found in the user manual of Astrée, Chapter 7.18 Common Weakness Enumeration – CWE, see screenshot. The user manual is available for licensed users and accessible directly from the tool GUI.

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

After the analysis run, customers can go to the Rule violations tab and select (left mouse click) the CWE identifier of interest. The findings table will then show only findings mapped to the selected CWE identifier. See screenshot.

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 user manual provides list of each check the tool can perform and the associated CWE identifiers (or other coding rules) as shown below:

Listed CWE identifiers link back to their description.

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 index lists the supported CWE identifiers. This list corresponds to the list of supported CWE identifiers found at https://www.absint.com/rulechecker/compliance.htm (in tab "CWE").

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

From the Result Overview, the user can switch to the Rule violations tab and simply double click on the CWE identifier. The screenshot shows the Result Overview with the Rule violations tab active.

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

When investigating reports in the Astrée GUI, findings state the CWE identifiers of CWEs associated with the type of the finding.

In the offline HTML reports, each finding lists the CWE identifiers of violated CWEs.

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

The CWE compliance matrix accessible via Help->Compliance matrices lists for each CWE identifier the claimed Match Accuracy element defined by CWE CCR.

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

AbsInt does currently not provide the CCR XML file.

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

Astrée's GUI lists all CWE identifiers associated with a task, i.e., finding, directly with the finding in its Findings view:

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

The user can import XML files specifying which CWE identifiers are of interest to the user. The tool will then only show findings associated with these identifiers. The file format is as follows and described in detail in the Astrée user manual:

<dax ...>
  <rulechecks>
    <rules>
      <cwe_identifier_1>yes</cwe_identifier_1>
      ...
      <cwe_identifier_n>yes</cwe_identifier_n>
    </rules>
  </rulechecks>
</dax>

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

The user may provide a DAX file as described above with a single CWE identifier of interest. He may also set a filter for the Findings view of the Astrée GUI to show just the findings associated with the given identifier:

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

The analysis results always contain the analysis configuration including a list of all CWE identifiers for which findings are reported. Identifiers not listed are not checked.

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

All documentation is provided in PDF format. Full-text search functionality is available in common PDF viewers.

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

All documents show (at least) identifier plus title.

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

A mapping of checks performed by Astrée and associated CWE identifiers is given in the user manual. The format of the mapping is discussed in the answer to CR_A.3.1.

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

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

The user can generate a rule-checking report containing all CWE-related coding violations as noted in CR.A.2.2. These reports can be generated as HTML, text, and/or CSV files. Each file format can be searched by standard viewers for specific CWE identifiers.

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: Christian Ferdinand

Title: 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: Christian Ferdinand

Title: 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: Christian Ferdinand

Title: CEO