Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

GTONE Co., Ltd.

Web Site:

http://www.gtonesoft.com

Adopting Capability:

SecurityPrism

Capability home page:

http://www.gtonesoft.com/eng/security-static-analysis-tools.php

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

SecurityPrism provides the capability to ensure secure application in the early stage of development lifecycle. SecurityPrism automatically checks your source code based on pre-defined rules about security vulnerabilities. Without configuring compiler environment or running programs, it correctly locates code lines which violate the pre-defined rules.

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 online-manual of SecurityPrism states the supported version of CWE[1].

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 provide up-to-date CWE mappings with every major release of SecurityPrism. We also plan to offer patches if there is any critical update of CWE.

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 is one major release of SecurityPrism every one or two years. We provide up-to-date CWE mappings with the major releases.

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

SecurityPrism provides an online manual. A user can access the CWE page via the table of contents in the manual[1,2]. The page describes the concept of CWE, supported CWE version, and CWE related features.

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

A user can perform CWE-related tasks using usual features of SecurityPrism. Detailed explanation of such features is available in the online manual. For instance, section 2 of the topic "Menu and Start Page" in the manual describes how to use search box to find defects using CWE identifier. A user may read the term "standard" as CWE and "rule identifier" as CWE identifier.

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 the answer to <CR_5.2>.

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 of mappings between CWE Identifiers and SecurityPrism rules is available in the CWE page in the online manual.

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

In SecurityPrism, a user can find rules and defects by using CWE identifier in various ways:

- When creating a new project, a user can find out which CWE rules are included in a ruleset by checking Related Standards column[1].
- In Category View panel, which is located on the lower left of the main window by default, a user can search CWE rules by entering CWE identifier[2].
- After analysis, a user can find detected defects associated with a CWE rule by entering the corresponding CWE identifier in the search field[3] or Advanced Search window[4].

;

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 can create a report of CWE-related defects. The report includes CWE identifiers for each CWE rules. In the report window, a user can hit Ctrl+F and enter a CWE identifier to search defects. In addition, the report can be exported to PDF or Excel documents, a user also can search and edit document by using usual applications.

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

Please see the answer to <CR_A.2.1>.

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

We don’t provide the CCR XML document yet.

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

SecurityPrism shows CWE identifiers associated with defects in Defect Info. panel and Category View panel. Please see the answer to . A user can export these data to Excel or PDF document and obtain desired information easily.

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

SecurityPrism does not provide such feature. SecurityPrism, however, offers various ways to find defects by CWE identifiers. Furthermore, a user can export most data in SecurityPrism, including a list of defects, to Excel of PDF document. So it is not difficult to perform such task. Please see the answer to <CR_A.2.1>.

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 the answer to <CR_A.2.1>.

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 gives an identifier of unsupported CWE, there will be either no data shown or a dialog saying that result does not exist. SecurityPrism does not provide a list of unsupported CWEs in the UI.

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

If a user gives an identifier of unsupported CWE, there will be either no data shown or a dialog saying that result does not exist. SecurityPrism does not provide a list of unsupported CWEs in the UI.

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

Please see the answer to <CR_A.2.2>.

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 online manual of SecurityPrism includes lists of mappings between CWE identifiers and SecurityPrism rules. Please see the answer to <CR_5.4>.

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

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:

Please see the answer to <CR_A.2.2>.

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: Simon Baeg

Title: Marketing Director

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: Simon Baeg

Title: Marketing Director

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: Simon Baeg

Title: Marketing Director