Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

TRINITYSOFT Co., Ltd

Web Site:

https://www.trinitysoft.co.kr

Compatible Capability:

CODE-RAY

Capability home page:

https://www.trinitysoft.co.kr

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

CODE-RAY is licensed software and allows you to send product packages according to your contract. After customers install the tool on their computer with the package, they can obtain a valid license upon 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):

For all new and updated versions, CODE-RAY uses the latest version of the CWE list provided by the "Mitre" organization.

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

CODE-RAY provides official releases at least once a quarter and updates CWE mappings for defects added or corrected when new versions are released.

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

Official releases are made quarterly, and CWE mappings are updated with each official 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):

CODE-RAY can check information with CWE-ID.

[Figure 1]

CODE-RAY can check detected vulnerabilities by CWE-ID, provides a guide corresponding to the CWE-ID, and provides a link to the cwe.mitre.org site as a reference in the guide.

[Figure 2]

CODE-RAY allows you to download Analysis Rules corresponding to the inspection criteria as an Excel file.

[Figure 3]

The Excel file maps CWE-ID and information related to analysis.

[Figure 4]

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

CODE-RAY provides “CWE Secure Coding Guide” inspection standards and provides users with CWE-IDs organized in an easy-to-find manner.

[Figure 5]

CODE-RAY allows you to download the “Analysis rule guide” as a PDF file.

[Figure 6]

Supported CW-ID information and descriptions are provided in the downloaded file.

[Figure 7]

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

See the answer to <CR_5.1>, <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):

CODE-RAY does not provide an index.

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

When CODE-RAY detects a vulnerability, you can check it on the following screen.

1. Weakness Search
   1. Select Project->Diagnose Weakness->Weakness Search.
   2. Search for CWE-ID in ID Code or check the ID Code value in the List.
   3. When you click the Source File section in the list of detected vulnerabilities, you will be moved to the detailed information screen.
   4. You can check information about the vulnerability.

   

   [Figure 8]

   

   [Figure 9]

2. Lookup Weakness Pattern
   1. Select Project->Diagnose Weakness->Lookup Weakness Pattern.
   2. It is displayed on the screen in a tree structure based on CWE-ID.
   3. If you select a detected vulnerability, you can check the source code and guide.

   

   [Figure 10]

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

CODE-RAY's report displays detected vulnerabilities in a graph and displays the number of vulnerabilities by CWE-ID.

[Figure 11]

[Figure 12]

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

CODE-RAY can check all CWE-IDs supported by the "CWE Secure Coding Guide" inspection criteria, and when downloading "Anlaysis rule download" You can check it as an Excel document.

[Figure 13]

[Figure 14]

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

CODE-RAY does not provide CCR XML documentation.

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

See the answer to <CR_A.2.3>.

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

See the answer to <CR_A.2.3>.

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

See the answer to <CR_A.2.3>.

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

Not supported

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

CODE-RAY is a web-based GUI that allows you to use the browser search function on every page.

On the security vulnerability checker screen, the CWE-ID and vulnerability checker supported for each supported language are mapped, and a search function by CWE-ID is provided.

[Figure 15]

On the checker guide screen, checkers supported for each analysis language are displayed and CWE-ID is mapped. Reference contains the web page address corresponding to the CWE-ID.

[Figure 16]

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

See the answer to <CR_B.3.1>.

ELECTRONIC DOCUMENT ELEMENT TO CWE IDENTIFIER MAPPING <CR_B.3.3>

Provide example documents that demonstrate the mapping from the capability's individual elements to the respective CWE identifier(s) (recommended):

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

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

See the answer to <CR_B.3.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):

See 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: WonYoung Kim

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 and to the best of my knowledge, there are no errors in the mapping between our capability's Repository and the CWE identifiers our capability reports, and those CWE identifiers are as specific as possible within the available CWE repository."

Name: WonYoung Kim

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 and to the best of my knowledge, normally when our capability reports a specific security element, it is generally correct and normally when an event occurs that is related to a specific security element our capability generally reports it."

Name: WonYoung Kim

Title: Chief Technical Officer