Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Beijing Anpro Information Technology Co. LTD

Web Site:

https://www.xmirror.cn/

Compatible Capability:

Xcheck Software Composition Analysis Platform

Capability home page:

https://oss.xmirror.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):

Xcheck SCA is used to solve the security risks of open source software and software supply chain introduced in the enterprise, which can accurately identify the third-party open source components introduced by software developers in the process of application development, and deeply excavate all kinds of security loopholes and open source protocol risks hidden in the components. Moreover, Xcheck SCA can automate the generation of a standardized machine-readable, internationally standardized software bill of materials (SBOM), which makes the supply chain assets transparent and guarantees the security of the software supply chain.

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 manual gives the CWE standards used and referenced. The user manual contains a chapter on CWE which describes which weaknesses are addressed by Xcheck SCA detection and declares the CWE version referenced.

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

Offline updates change the frequency of updates depending on the risk level: typically, the vulnerability database is updated every 2 weeks and the mapping relationships are updated at the same time. If a high risk is identified, the vulnerability database should be updated within 3 hours and the mappings updated at the same time.

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

The offline update changes the update frequency according to the risk level: Generally, the vulnerability database is updated every 2 weeks; if high risks are found, the vulnerability database should be updated in time within 3 hours. The mapping is updated every time the vulnerability database is updated.

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 about CWE and CWE compatibility could be found in Chapter 6 Common Weakness Enumeration - CWE of the user manual,see screenshot. The user manual is available for licensed users,and can be accessed directly from the tool GUI.

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

After the analysis is complete, you can view the application package analysis in [Binary Component Analysis], search for the corresponding CWE identifier, and display all vulnerabilities mapped to contain the CWE identifier. Click on the vulnerability to view the vulnerability details.

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 security vulnerabilities and associated CWE signs discovered by the tool after each execution of the test, as shown in the following figure:

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

After the Component Dependency Detection/Binary Component Analysis is complete, click on the [task details] to view the CWE identifier that the component vulnerability is mapped to, as shown in the following figure:

Component Dependency Testing

Binary Component Analysis

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

On the [Binary Component Analysis] View Analysis Results GUI page, click Components to view the component contains vulnerability information and associated CWE encoding information.

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

Click the search icon in the upper right corner and type in "CWE" to see a list of CWE logo coverage in the GUI interface.

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

See answer to CR_A.2.2.

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 available in Word/PDF/Excel format. The full text search function is available in the normal Word/PDF/Excel viewer and allows for the retrieval of textual information related to CWE 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 eDoc, the CWE identifiers associated with the security elements are 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):

Click on the search icon in the upper right corner to search for the corresponding CWE identifier and find detailed information about the CWE identifier in the GUI interface:

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: Zhang Tao

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: Zhang Tao

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: Zhang Tao

Title: CEO