Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Hangzhou Huawei Cloud Computing Technologies Co., Ltd

Web Site:

https://www.huaweicloud.com/

Compatible Capability:

CodeArts Check

Capability home page:

https://www.huaweicloud.com/intl/en-us/product/codecheck.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):

You can go to the following website and register as member, then you can use it. English version: https://www.huaweicloud.com/intl/en-us/product/codecheck.html Chinese version: https://www.huaweicloud.com/product/codecheck.html CodeArts Check provide free and enhancement version.

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

On CodeArts Check's rule detail page, we provide the rule related CWE ID linkage to current CWE version for more detail.

CodeArts Check provide the CWE Id web link: https://cwe.mitre.org/data/definitions/[CWE ID].html to CWE website related CWE id.

Current CodeArts Check release version is follow CWE 4.11 version, and for next release will mapping to the latest version: CWE 4.12.

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

CodeArts Check updated CWE capability mappings in each new release version, typically for new checking rules.

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

CodeArts Check’s CWE capability mapping updates occur with every release, Customers have grown to understand an expect this.

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

1. In CodeArts check rule set export excel user can export the rules list as excel file. In the excel file, it will provide the CWE Id for related rule as below.

   

2. In CodeArts Check scan result export excel user can export the defects list as excel file. In the excel file, it will provide the CWE Id for related rule as below.

   

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

1. In CodeArts Check rule set export excel user can export the rules detail as excel file. In the excel file, it will provide the CWE Id for related rule as below. User can use CWE identifiers to find specified CWE id.

   

2. In CodeArts Check rule search page user can search rules by CWE ID to find specified CWE id.

   

3. In CodeArts Check rule detail page user can get the rule related CWE id and to check the specified CWE id more detail on CWE website.

   

4. CodeArts Check scan result search page user can search specified CWE ID in scan result.

   

5. Scan result output result user can export scan result as excel file. In the excel file, it will provide the CWE Id for related rule as below. User can use CWE identifiers to find specified CWE id.

   

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

Please reference CR_5.2, user can get the checking rules related CWE identifiers through:

• Rule set export excel
• Rule search page
• Rule detail page
• Scan result search page
• Scan result export excel

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

We plan to provide CodeArts Check rules specification, it will include the index per CWE

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

aaaaa

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 reference CR_5.2, user can get the checking rules related CWE identifiers through:

• Rule set export excel

  • Through excel CWE column to filter specified CWE ID

• Rule search page

  • Input specified CWE ID and press search button to get related rules.

• Rule detail page

  • Check the rule reference to get related CWE ID.

• Scan result search page

  • Input specified CWE ID and press search button to get CWE ID related scan result.

• Scan result export excel

  • Through excel CWE column to filter specified CWE ID.

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 reference CR_5.2, user can get the checking rules related CWE identifiers through

• Rule set export excel

  • Through excel CWE column to filter specified CWE ID.

• Rule search page

  • Input specified CWE ID and press search button to get related rules.

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

In rule select page, choose search item as “CWE ID”, input searched CWE Id, then press search button. If we are not supporting searched CWE Id, search result will tell you: you can get related result. The search result will as below screen cut.

SERVICE COVERAGE DETERMINATION USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of the different ways that a user can use CWE identifiers to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):

Please reference CR_5.2, user can get the checking rules related CWE identifiers through:

• Rule set export excel

  • Through excel CWE column to filter specified CWE ID.

• Rule search page

  • Input specified CWE ID and press search button to get related rules.

FINDING CWE IDENTIFIERS IN SERVICE REPORTS USING ELEMENTS <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CWE identifiers for the individual security elements in the report (required):

Please reference CR_5.2, user can get the checking rules related CWE identifiers through:

• Scan result search page

  • Input specified CWE ID and press search button to get CWE ID related scan result.

• Scan result export excel

  • Through excel CWE column to filter specified CWE ID.

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.3.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 service is effective at locating in software (required):

Please reference CR_5.2, user can get the checking rules related CWE identifiers through:

• Rule set export excel

  • It will get all supported CWE ID through excel CWE column.

• Rule search page

  • Input specified CWE ID and press search button to get related rules.

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 reference CR_5.2, user can get the checking rules related CWE identifiers through:

• Rule search page

  • Input specified CWE ID and press search button to get related rules.

• Rule detail page

  • Check the rule reference to get related CWE ID.

• Scan result search page

  • Input specified CWE ID and press search button to get CWE ID related scan result.

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 reference CR_5.2, user can get the checking rules related CWE identifiers through:

• Rule set export excel

  • Through excel CWE column to filter specified CWE ID.

• Scan result export excel

  • Through excel CWE column to filter specified CWE ID.

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 Senjun

Title: Software service domain director

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 Senjun

Title: Software service domain director

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 Senjun

Title: Software service domain director