Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Beijing Anpro Information Technology Co. LTD

Web Site:

https://www.xmirror.cn/

Compatible Capability:

Xmaze AI Pen-Testing Extension

Capability home page:

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

Xmaze AI Penetration Testing Extension ("Xmaze PTE"), as the threat detection and exploitation platform of CI/CD pipeline in Xmirror Security's DevSecOps Smart Threat Management System, empowers traditional IT practitioners with full-scene traffic analysis technologies, such as heuristic crawler, endpoint traffic proxy/VPN, traffic manager (host traffic sniffing, bypass traffic mirroring), and original AI penetration-inspired technologies to intelligently schedule penetration strategies and freely select attack paths based on AI decision engine.It has a wealth of attack components, which can support external network, internal network and local attacks. In the post-penetration stage, the platform can perform data search based on the feature dictionary and collect supporting data for further penetration. The platform can carry out all-round security testing not only for system security application vulnerabilities, but also for system business logic vulnerabilities, and issue professional security repair recommendations, and provide users with multi-format, professional and compliant penetration test reports.

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 CWE standards used and cited are given in the user manual. There is a chapter in the user manual about CWE, which describes which weaknesses the Xmaze BAS rule detection solves, and declares the CWE version cited.

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

The offline update changes the update frequency according to the risk level: Generally, the vulnerability database is updated every 2 weeks and the mapping relationship is updated at the same time; if a high risk is found, the vulnerability database should be updated in a timely manner within 3 hours, and the mapping relationship should be 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 of 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, the user clicks [Threat Detection-Intelligence Infiltration-Vulnerability Management] and searches for the corresponding CWE number, and the vulnerability information mapped to the CWE number is displayed. Click the hyperlink of the vulnerability name to view 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 related CWE signs discovered by the tool after each execution of the test, as shown in the 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):

The vulnerability knowledge base list function module of the Xmaze BAS platform displays the CWE identifier, and the CWE number of the related vulnerability can be viewed in the corresponding data.

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 Xmaze BAS completes the threat detection task, click the task details to view the CWE identifier mapped to the vulnerability in the vulnerability list, as shown in the figure:

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 [Vulnerability List - Vulnerability Name - Vulnerability Details] Vulnerability Details GUI page, you can check the specific location of the vulnerability and the associated CWE identifier information:

Vulnerability List：

Vulnerability Details：

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

On the [Vulnerability Knowledge Base] page, click the input box and enter "CWE" to view the CWE identification coverage list on the GUI interface:

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

Click the input box on the [Vulnerability Knowledge Base] page to search for the corresponding CWE identifier, and you can find the detailed information of 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