Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Beijing Beida Software Engineering Development

Web Site:

http://www.beidasoft.com

Compatible Capability:

COBOT

Capability home page:

http://cobot.net.cn

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 purchase COBOT by clicking the website http://cobot.net.cn/presale.jsp. In addition, COBOT provides users with cloud detection on our official website http://cobot.net.cn.

1. Open the official website http://cobot.net.cn and first click the red circle “登录” in the top right corner, as shown in figure 1.

Figure-1 COBOT's Homepage

2. Enter "cobot" as the user name in the textbox on the first-line, and enter "123" as the password on the second-line, as shown in figure 2. Then click the left button and log in.

Figure-2 The Login Page

3. Click the red circle “预约” in figure 3.

Figure-3 the page after logging in

4. Click the yellow button “开始” in the middle to start the cloud detection, as shown in figure 4.

Figure-4 to start the cloud detection

5. Enter into the detection page. And then you can detect defects in projects. We have prepared a C project named “hello” on the page, as shown in figure 5.

Figure-5 the Detection Page

6. In figure 6, we import a C project named "bzip2" which is from spec2000, and detect it. And the results of detection are shown as figure 6.

Figure-6 the results of detection

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

The user can view the most recent CWE content by clicking "Help -> CWE ->  CWE Mapping Relations".

The user can also view it by clicking the website (at the bottom of the page as shown in figure 7) http://cobot.net.cn/cwe/CWE%20Mapping%20Relations.pdf.

Figure-7 the CWE Documentation and CWE Mapping Relations on the page http://www.cobot.net.cn/

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 release our product COBOT twice every year - one in winter and one in summer. We will try our best to update the most recent CWE content in each release.

And if we improve our defect items by using the code cases in CWE, we will add the CWE-ID to the relevant defect items.

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 COBOT twice every year - one in winter and one in summer. 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 (2), by quoting the description of CWE and CWE compatibility on the CWE official website.

The CWE Documentation is also available here: http://www.cobot.net.cn/cwe/CWEDocumentation.pdf

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 the "CWE Documentation" by clicking "Help -> CWE -> CWE Documentation".

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

The user can import a project and make a configuration of detection items before bug analysis. Click "File->Create a Project" for importing projects (as shown in figure 8) and then click "Detection Configuration" for configuring the detection items. The users can search related detection items by CWE identifiers. For example, in the top of "Detection Configuration", the user can enter "cwe-467" nearby the "Query" textbox and then click "Query". The results will be showed up correspondingly, as shown in figure 9. And then you can check the items which you want. Figure-8

Figure-8 Importing projects

Figure-9 CWE search in the context of configuration Items

After bug analysis, the users can also search the related defects by entering CWE identifiers in the area “Defect Results”. For example, in the top of “Defect Results”, the user can enter “cwe-119” nearby the “Query” textbox and then click “Query”. The results which are associated with “cwe-119” will be showed up correspondingly, as shown in figure 10.

Figure-10 CWE search in the context of Defect Results

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

Click "Detection Configuration" for configuring the detection items. The associated CWE identifiers are at the end of the item description as shown in figure 11.

Figure-11 Detection configuration

After detection, the results are displayed at the output area. For the description of a defect, there is a column named "CWE" in the table, at which the user can also obtain the CWE identifier(s) associated with the defect. Besides that, the CWE identifier(s) will be displayed in Description area when the corresponding defect is analyzed. You can click "cwe-XXX" to link the CWE official website, as shown in figure 12.

Figure-12 Defect Results and corresponding CWE items

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 user can view the CWE Mapping Relations by clicking "Help -> CWE -> CWE Mapping Relations" in COBOT.

The CWE Mapping Relations document is also available here:
http://cobot.net.cn/cwe/CWE%20Mapping%20Relations.pdf.

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

N/A

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 <CR_A.2.2>.

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 <CR_A.2.1>.

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 <CR_A.2.1>.

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 13.

Figure-13 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 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.

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

Please see the CWE Mapping Relations File below.

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

Please see the answer to <CR_A.2.12>.

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: Sen Ma

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 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: Sen Ma

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 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: Sen Ma

Title: Product Manager