Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Anban Information Technology Co., Ltd

Web Site:

https://www.anban.tech/

Compatible Capability:

Yishi Firmware Supply Chain Security Management System

Capability home page:

https://www.anban.tech/details/yishiDynamic

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 Yishi Firmware Supply Chain Security Management System supports users to detect CWE defects in firmware and retrieve corresponding CWE details through a knowledge base. Users can perform corresponding CWE analysis and retrieval work in the firmware scanning analysis and knowledge base modules.

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 will provide firmware CWE analysis capabilities in the firmware scanning analysis and analysis strategy module of the product, and the latest CWE information retrieval capabilities in the knowledge base module.

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

Our product will iterate on a quarterly basis, and users can use the new version of the product and data services through the new authorization code during the transition period.

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

In the last week of each quarter, we will release new products and notify users of updates to corresponding content and data. Users can view new technical docs and user manuals to use the product.

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

Description of CWE and CWE compatibility could be found in Chapter 4.4 Knowledge base services - CWE of the user technical doc, see screenshot.

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

Users can upload firmware in the firmware scanning and analysis module for CWE defect detection, and view CWE related detection information in the online report.

In the knowledge base, corresponding CWE information can be quickly queried.

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

The user manual shows the associated risk type and CWE identifiers for each recorded attack event, as shown in the following figure:

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

By downloading the firmware scan analysis report, detailed information on CWE defects can be viewed in the offline report.

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 enter the corresponding CWE number in the knowledge base, click on the scope of influence field on the search results page, and view the firmware scanning tasks associated with that CWE.

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

In the online report of firmware scanning tasks, corresponding CWE information can be viewed,the CWE identifier corresponding to each task can be checked.

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

By downloading the firmware scan analysis report, detailed information on CWE defects can be viewed in the offline report.

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

Electronic documents are provided in Word and PDF formats. The full-text search function is available in ordinary Word viewers and PDF viewers and can CWE related text information in the generated report.

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

In the vulnerability list table of the electronic document, the CWE identifier related to the security element is described:

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

In the knowledge base, enter the CWE identifier you want to filter in the CWE identifier filter box，you can view detailed information and associated tasks related to CWE.

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

See answer to <CR_A.2.2>.

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: Wang Yi

Title: CEO

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: Wang Yi

Title: CEO

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: Wang Yi

Title: CEO