Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Suresoft Technologies Inc.

Web Site:

http://www.suresofttech.com

Compatible Capability:

CodeScroll SNIPER

Capability home page:

http://www.suresofttech.com/products/sniper/

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

CodeScroll SNIPER is a licensed software, we can send a product package under contract. After customers installed our tool on his computer with the package, a valid license can be received on request.

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

CodeScroll SNIPER embeds explanation about mapping CWE-IDs and defects which can be detected by it. This explanation is provided as a view of CodeScroll SNIPER (see Figure 1). CWE version information is shown in this view as Figure 1.

Figure 1 CWE Mapping information in a view of CODESCROLL

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

Every time we release a new official version of CodeScroll SNIPER, we update all the CWE mappings. Normally we release 2 or 3 new versions in a year and they are official periodic releases. We check all changes to the CWE compared with older version and update all CWE mappings in our tool. During the release process, independent Quality Assurance team has to involve the process for checking the currency of CWE version.

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

We explain verbally that the CWE mapping will be updated every official releases and the official releases are 2 or 3 time in a year.

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

CodeScroll SNIPER provides online documents about CWE and CWE mapping which is embedded in our tool. Users can find an access link to CWE description in a title page of our tool. (See Figure 2) Through the link they can reach description page about CWE program. (See Figure 3.)

Figure 2. CWE Menu in title screen

Figure 3. Description of CWE Program

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

CodeScroll SNIPER provides web browser interface for displaying CWE online description. Thus users can utilize web browser search function by typing "Ctrl-F". With CWE-ID they can search a proper description and find a mapping information between CWE-ID and CWE capability. (See Figure 4.)

Figure 4. CWE Mapping table

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

Please refer to the answer to Refer to <CR_5.1>. We provides an index titled as "CWE" in main page.

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

Once CodeScroll SNIPER found a potential problem (we call it as “defect”), users can see the relationships between defects and CWE-IDs with following steps:

1. Input CWE-ID on a search windows in "Defect-Explorer" view (see Figure 5. (1)).
2. Check the associated defects with a given CWE-ID (see Figure 5. (2)).
3. Select a defect in the list. Then you can see the related rule description in a "Description" view (Figure 4. (3)). You can also find a link to a detailed description about the related CWE rule in CWE homepage.

Figure 5. How to look for CWE-IDs

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

"Defect Explorer" view provides a list of defects. Users can find CWE-IDs associated to listed defects with following steps.

1. Select "Rule" grouping options.
2. Select "Show Detailed Label" tool bar button.
3. Check the associated CWE-IDs.

Figure 6. Security elements and associated CWE-IDs

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

A complete table of CWE Coverage information is available on the Suresoft Technologies website:

• http://www.suresofttech.com/resource/datasheets/
• http://www.suresofttech.com/wp-content/uploads/2015/09/CWE-Compatibility.pdf

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

CodeScroll SNIPER doesn't provide a 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):

N/A

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

N/A

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

CodeScroll SNIPER provides an embedded online manual. Users can find a CWE mapping table and for searching CWE-related text they can utilize links in the mapping table. They can also use the search function (Ctrl-F) like a Web browser.

1. Select "CWE" menu on the top menus.
2. Select "CWE Mapping" menu on the main view (see Figure 7).

Figure 7. Online manual

Figure 8. CWE Mapping

3. Select CWE-ID in the mapping table for moving to CWE website or select an item on SNIPER column for moving to a local rule description page (see Figure 8, 9).

Figure 9. CWE website and SNIPER rule description page

4. You can find a link to associated CWE pages in SNIPER rule description pages.

Figure 10. SNIPER rule description page

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 refer to the answer to <CR_B.3.1>.

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

Please refer to the answer to <CR_B.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):

Please refer to 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 refer to the answer to <CR_A.2.2>. And also in a tool preference setting menu users can check CWE-ID in a "Global Rule" item.

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

Please refer to the answer to <CR_B.3.1>.

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: Seunguk Oh

Title: Chief Technical Officer

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: Seunguk Oh

Title: Chief Technical Officer

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: Seunguk Oh

Title: Chief Technical Officer