Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Anhui USTC-Guochuang High-Confidence Software Co.,Ltd

Web Site:

http://www.ustchcs.com

Compatible Capability:

USTCHCS high confidence software analysis tool suite

Capability home page:

http://www.ustchcs.com/solution.html

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

USTCHCS high confidence software analysis tool suite

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

We regularly update the component library, which contains the latest CWE compliance content. Component library updates are provided in the form of upgrade packages, which the USTCHCS Analysis Tool obtains online or offline.

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 will update weekly vulnerability database, and adopt the method of incremental updates, at the same time we will make a backup before updating the protection of historical data.

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 release our product twice every year. The user can get updated mapping relationships in each version.

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

Users can view CWE through click the help document page as shown in figure 1.

Figure 1

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

When the detection is completed, we will list all vulnerabilities and their corresponding CWE numbers. At the same time , we will be able to highlight where these vulnerabilities are in the code，as shown in figure 2.

Figure 2

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

When the detection is completed, we will automatically generate a related report. You can click the CWE number to jump to the CWE official website. as shown in figure 3.

Figure 3

Figure 4

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

Please refer to <CR.5.2>.

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

Please refer to <CR.5.3>.

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

1. Open the official website http://www.ustchcs.com/, as shown in figure 5. And click the "Trial" button on the page to open the product trial page.

   

   Figure 5

2. Enter the application information and click the submit button to submit the application.

   

   Figure 6

3. After receiving the application, we will contant with you and send installation package to your email.

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

1. Users import the project source code to be tested into VSCODE , as shown in Figure 7.

   

   Figure 7

2. Create a new project and automatically analyze the security defects in the code,as shown in figure 8.

   

   Figure 8

3. Click the “Project management” button to set the detection rules and compiler. Users can find and select the CWE rules they need , as shown in figure 9.

   

   Figure 9

4. When the detection is completed, we will list all vulnerabilities and their corresponding CWE numbers. At the same time , we will be able to highlight where these vulnerabilities are in the code，as shown in figure 10.

   

   Figure 10

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

Our electronic document format is HTML or Excel. So users can easily search for specific CWE-related text by keyword searching. For example, we open the CWE Mapping Relations document, and search "CWE" by pressing "Ctrl + f", as shown in figure 11.

Figure 11

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

We list the mapping relationship in the form of a table, and the document format is Excel. Users can easily find the relevant CWE ID by searching component serial number or component keyword.

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

Users can look for the associated CWE identifier(s) by typing CWE-related text in the blue box.

Figure 12

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 <CR.5.3>.

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: Ying Zhang

Title: Marketing specialist

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: Ying Zhang

Title: Marketing specialist

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: Ying Zhang

Title: Marketing specialist