Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Suresoft Technologies Inc.

Web Site:

http://www.suresofttech.com

Compatible Capability:

CodeScroll STATIC

Capability home page:

https://www.suresofttech.com/en/tool/code_static.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):

CodeScroll STATIC is a licensed software, we can send a product package under contract. After customers installed our tool on his/her server, 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 STATIC embeds explanation about mapping CWE IDs and defects which can be detected by it. CWE mapping information is displayed on the CWE Mapping page of STATIC's Help page.(see Figure 1). CWE version information is shown in this view as Figure 1.

Figure 1. CWE mapping information in help page of CodeScroll STATIC

For each rule of CodeScroll STATIC, CWE ID mapping is displayed as a rule label. (see Figure 2)

Figure 2. CWE ID mapping(Rule label) for each rule

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 STATIC, 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 out 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 STATIC provides online documents about CWE and CWE mapping which is embedded in our tool. Users can find an access link to CWE description in an online help of our tool. (see Figure 3) Through the link they can reach description page about CWE program.

Figure 3. CWE and CWE compatibility in online help

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 STATIC provides a description about CWE in online help. Using the CWE-ID on the Rule Settings page of CodeScroll STATIC, you can search for the appropriate description and find the mapping information between CWE-ID and CWE capability.(see Figure 4) If you click on the CWE rule label, you can view the CWE rule description page of the CWE official site.

Figure 4. CWE mapping

And CWE mapping information is displayed on the CWE Mapping page of STATIC's Help page.(see Figure 1)

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

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

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 STATIC found a potential problem (we call it as “defect”), users can see the relationships between defects and CWE-IDs with following steps.

1. Filter the defect by entering CWE-ID in the Label filter on the "Defects" page.(see Figure 5 (1))
2. You can see that the Label contains the CWE-ID entered in the filtered item. (see Figure 5 (2))
3. Selecting the label links to the description page of the CWE-ID of the CWE site.

Figure 5. How to look for CWE-IDs in defects page

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

In the "Defects" page list, you can see that the Label contains the CWE-ID associated with Defects.(See Figure 6)

Figure 6. Security elements and associated CWE identifiers

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 CodeScroll STATIC's Help page displays a complete list of CWE-IDs supported by STATIC.(see Figure 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):

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

Defects page of CodeScroll Static displays the CWE-IDs associated with the detected item.(see Figure 6)

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

On the Defects page of CodeScroll STATIC, enter the CWE-ID in the Label filter to see the associated detection items.(see Figure 7)

Figure 7. Filter the defects(tasks) with CWE-ID

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

Refer to <CR_A.2.7>

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

The results of CodeScroll STATIC analysis are provided as a web-based GUI, so you can use the browser search function on all pages.

1. View of CWE mapping information (see Figure 1)
   1. Select [Help] menu at the top right of CodeScroll Static
   2. Select [CWE Mapping] from the menu list on the left to view CWE Mapping information.
2. On Rule setting pages, Display CWE ID and link to CWE rule description page of CWE site
   1. Select [Rule] menu on administration page
   2. Selecting the CWE-ID rule label links to the description page of the CWE-ID of the CWE site.(see Figure 8)

      
      Figure 8. Link to CWE page from CWE-ID rule label

   3. On Rule description pages, display the related CWE-ID information.(see Figure 9)

      
      Figure 9. Related Link information of CodeScroll STATIC Rule description

3. On Defects pages, Display CWE ID and link to CWE rule description page of CWE site. (Figure 10)

   
   Figure 10. Related CWE-ID link of label of defect

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

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

Refer to <CR_B.3.1>.

Back to top

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

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

Refer to <CR_A.2.2>. And also in a tool rule setting page, users can check CWE ID with CWE-ID label for each rule.

Figure 11. CWE mapping by CWE-ID label

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

Refer to <CR_B.3.1>.

Back to top

Questions for Signature

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

Back to top

More information is available — Please edit the custom filter or select a different filter.