Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Beijing RedRocket Technology Co., Ltd

Web Site:

http://www.redrocket.cn/

Compatible Capability:

RedRocket SCA

Capability home page:

http://www.redrocket.cn/Home/Product_introduction/index.html?id=13

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

Users can visit the company's website to apply for trial or contact us to buy products.Company address: http://www.redrocket.cn/.

We’re very sorry that we haven’t translated our website from Chinese into English and we promise to do the job soon. So let me instruct you to use our product for cloud detection as below:

1. Open the official website http://www.redrocket.cn/, as shown in figure 1.

   

   Figure-1 Homepage

2. 2. Select SCA products and click "apply for use"，as shown in figure 1.

   

   Figure-2 Tool application trial

3. Enter the application information and click the submit button to submit the application, as shown in figure 3.

   

   Figure-3 Submit application information

4. After receiving the application, we will send the login address, user name, password and user manual to your email.

5. The user can log in to the SCA system with the login information received, as shown in Figure 4.

   

   Figure-4 System login home page

6. Click "new project" to create a new project, as shown in Figure 5.

   

   Figure-5 Create test task interface

7. After the detection, click the project name to enter the detection result query page, and click the "view vulnerability" button after the component name to query the CWE related information, as shown in Figure 6 and figure 7.

   

   Figure-6 Test results page

   

   Figure-7 Vulnerability view page

8. Click the CWE number to open the CWE official website address, as shown in Figure 8.

   

   Figure-8 CWE page

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

Users can view CWE through the product homepage (click the help button in the upper right corner, as shown in Figure 9 and 10

Figure 9 The help button

Figure-10 the CWE Documentation and CWE Mapping Relations on the page

We release our product twice every year. And we will add the most recent CWE content to the "CWE Mapping Relations" in each new version. The user can review it.

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 download the component's CWE vulnerability in real time every day and update it to the local database. We release our products twice a year, and each release will update the CWE content.

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 relations in each 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):

Our CWE Documentation describes CWE and CWE compatibility at the beginning of the article as part (I) and part (II), by quoting the description of CWE and CWE compatibility on the CWE official website. Users can view CWE through the product homepage, and click the help button in the upper right corner to view CWE mapping relations file, as shown in Figure 4 and figure 5.

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

Our CWE Documentation describes this at the part (IV) of the article, which is named "About CWE Searchable".

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

Our CWE Documentation describes this at the part (III) of the article, which is named "About CWE Output".

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

The reference is at the end of our CWE Documentation as below.

Reference

[1] http://cwe.mitre.org

[2] http://cwe.mitre.org/compatible

And the user can view CWE through the product homepage (click the help button in the upper right corner.)

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 import projects and analyze them. Click File > create project to import the project, as shown in Figure 11. After the detection, on the "vulnerability list" page, enter "cwe-310" in the "vulnerability type" text box, and click "retrieve". The results are displayed accordingly, as shown in Figure 12. You can then look at the corresponding vulnerabilities. Click the vulnerability name to view the corresponding project information, as shown in Figures 13 and 14.

Figure-11 Importing projects

Figure-12 CWE search in the context of Items

Figure-13 Vulnerability list

Figure-14 Impact projects

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 system detection is completed, the total number of project vulnerabilities is visible in the "All Vulnerabilities" column of the current project list, as shown in the following figure.

Figure-15 Project test results

Click on the hyperlink corresponding to the project name for entry to the project details page to display the open source components used by the project and the number of vulnerabilities contained in each component, as shown in the following figure.

Figure-16 All components used in the project and their number of vulnerabilities

Click the number hyperlink in the "All Vulnerabilities" column to view the details of the vulnerabilities in the current component. The "Vulnerability Type" in the component vulnerability list shows the correspondence between the current vulnerabilities and CWE vulnerabilities. If it can exactly match the CWE vulnerabilities, then Display the CWE vulnerability number in the current list, as shown in the figure below.

Figure-17 A list of vulnerabilities in a certain component

Click on the CWE number hyperlink in the figure above, and the page jumps to the description page of the CWE official website describing the current vulnerability, as shown in the following figure below：

Figure-18 CWE official website Vulnerability description 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):

Users can view CWE through the product homepage, and click the help button in the upper right corner to view CWE mapping relations file, as shown in Figure 9 and figure 10.

Product address: http://www.redrocket.cn/Home/Product_introduction/index.html?id=13.

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

Please see the answer to question 11.

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

Please see the answer to question 10.

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

Please see the answer to question 10.

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

When you search a CWE ID but there is no result, the tool notifies the user that a task associated with a selected CWE identifier cannot be performed.

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. For example, we open the CWE Mapping Relations document by Adobe Reader, and search "cwe" by pressing "Ctrl + f", as shown in figure 19.

Figure-19 search specific CWE-related text in PDF 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 relationship in the form of a table, and the document format is PDF. 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):

Please see the answer to question 10.

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 answer to question 11.

And the format of our CWE Mapping Relations file is a table in PDF.

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

Documents may be exported in XLS or PDF and the user can use their own search function by searching keyword. And the documents in XLS will have a column named "CWE" whose content is the associated CWE ID(s).

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: XiaoMeng Liu

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: XiaoMeng Liu

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: XiaoMeng Liu

Title: Product Manager