Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

IBM Security Systems

Web Site:

http://www.ibm.com

Compatible Capability:

IBM Security AppScan Standard

Capability home page:

http://www-01.ibm.com/software/awdtools/appscan/standard/

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

IBM Security AppScan Standard is available for purchase and free trial online. See: http://www-01.ibm.com/software/awdtools/appscan/standard/

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

Our CWE mappings are maintained by our Security Research team. Upon new CWE creation or needing to update the CWE mapping, our Security Team will release an update to AppScan that will be deployed immediately.

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

We have done extensive mappings to our tests, in any case that a mistake is found it is fixed immediately and an update is released. Upon adding new tests, they are added only with correct mappings.

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

IBM Security AppScan Updates, which also include CWE mappings, are released on a weekly basis, or upon urgent need.

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

An excerpt from our documentation:

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

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

From the excerpt above:

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

A user that would like to find a test that is mapped to a certain CWE can:

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 user that would like to find a test that is mapped to a certain CWE can:

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 readme file included with the installation includes a list of the supported CWEs.

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

The readme file included with the installation includes a list of the supported CWEs.

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 test policy is the area in which a user can select and deselect tests. It is also where a user can search for CWE-IDs. A user can search for an ID and then select the tests that were found to be mapped to that ID.

FINDING TASKS USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CWE identifier (required):

The test policy is the area in which a user can choose which tests are run. A user can search for a CWE-ID, and see which tests may be run.

After the tests are run a user can read the test’s advisory, where the CWE-ID and link to the MITRE CWE site are found.

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS <CR_A.3.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 test policy is the area in which a user can choose which tests are run. After the tests are run a user can export the results to a report, where the CWE-ID and link are found.

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.3.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 readme file included with the installation includes a list of the supported CWEs.

FINDING ONLINE CAPABILITY TASKS USING CWE IDENTIFIERS <CR_A.4.1>

Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CWE identifier or through an online mapping that links each element of the capability with its associated CWE identifier(s) (required):

Each CWE-ID is linked to the online CWE MITRE site. These links are accessible through the advisories which are displayed in the test policy, or in the issue pane, or through the exported reports.

AppScan does not support online searching of its repositories, it only supports local searching and if the CWE-ID is found a link is made available to the CWE MITRE site.

FINDING CWE IDENTIFIERS USING ONLINE CAPABILITY ELEMENTS <CR_A.4.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CWE Identifiers for the individual security elements in the report (required):

The test policy is the area in which a user can choose which tests are run. After the tests are run a user can export the results to a report, where the CWE-ID and link are found.

AppScan does not support online searching of its repositories, it only supports local searching and if the CWE-ID is found a link is made available to the CWE MITRE site.

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.4.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 online capability's repository covers (required):

The readme file included with the installation includes a list of the supported CWEs.

ONLINE CAPABILITY ELEMENT TO CWE IDENTIFIER MAPPING <CR_A.4.5>

If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CWE Identifier(s), otherwise enter N/A (required):

N/A

Details for individual security elements ARE provided, as explained above.

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

IBM Security AppScan Standard includes a User Guide (PDF Format) and help files (CHM). These documents include information and instructions as to where and how to use AppScan with CWE related functions.

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 capability’s standard electronic documents DO NOT list security elements by their short names or titles.

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

A user can search for any CWE in the test policy and find the tests mapped to it.

A search box is available, through which the user can search for many terms, among which is the CWE-ID.

Upon searching the result set in the test policy is auto-filtered to display on the tests mapped to the CWE-ID.

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

Upon searching for a CWE in the test policy, the result set is filtered to include only the relevant tests. Upon clicking a test, the user can see its advisory which includes the mapping to the CWE. The mapping behaves as a URL link to the online MITRE site to the specific ID.

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

IBM Security AppScan Standard includes a User Guide (PDF Format) and help files (CHM). These documents include information and instructions as to where and how to use AppScan with CWE related functions.

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: Yoel Eilat

Title: Senior Security Research and Temporary 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: Yoel Eilat

Title: Senior Security Research and Temporary 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: Yoel Eilat

Title: Senior Security Research and Temporary Product Manager