Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Beijing Beida Software Engineering Co., Ltd

Web Site:

https://www.pkuse.com.cn

Compatible Capability:

COBOT-SCA

Capability home page:

https://www.pkuse.com.cn/multi/523.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):

The user can visit our website, in the bottom of the page with our telephone and qr code, contact us for COBOT-SCA service address and account password. as shown in figure 1. Company address:https://www.pkuse.com.cn

Figure- 1 Homepage

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

If we detect the vulnerabilities have the corresponding CWE number, we will show the page. as shown in figure 2.

Figure- 2 Corresponding CWE

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 the product homepage (click the help button in the upper right corner)as shown in figure 3. 4.

Figure- 3

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

When the detection is completed, we will list all vulnerabilities and their corresponding CWE numbers. At the same time, we also have the function of searching according to the CWE number.as shown in figure 5.

Figure- 5 Vulnerabilities page

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 list all vulnerabilities and their corresponding CWE numbers. You can click the CWE number to jump to the CWE official website. as shown in figure 6.

Figure- 6 CWE Identifier Details

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

Users can upload items and then detect them.as shown in figure 7. After the detection, on the "vulnerability list" page can view results. as shown in figure 8.

Figure- 7 Import items

Figure- 8 Vulnerabilities list 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):

After the analysis is completed, click the component details page of the project to see the vulnerability information corresponding to the analyzed third-party components.as shown in figure 9.

Figure- 9 Component details page

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

1. Check the vulnerabilities list page, you will see all vulnerabilities checked from your items. as shown in figure 10.

Figure- 10 Vulnerabilities list page

2. click the CWE number to jump to the CWE official website and get detail information. as shown in figure 11.

Figure- 11 CWE Identifier Details

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

We have a search function,if search a CWE identifiers and the function return null we will notify the user that it is an unable to work the CWE identifiers.

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 PDF or WORD. So users can easily search for specific CWE-related text by keyword searching. as shown in figure 12.

Figure- 12 search CWE text in document

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 relations in the form of table, and the documentation format is PDF. The defect items have their own numbers. The user can easily find the associated CWE ID by searching number or 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):

Please see the <CR_A.2.3>.

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 <CR_A.2.1> and <CR_A.2.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: Hua Xiao

Title: Product Manager

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: Hua Xiao

Title: Product Manager

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: Hua Xiao

Title: Product Manager