Name of Your Organization:
Beijing Anpro Information Technology Co. LTD
Xmaze Static Application Security Testing Platform
Capability home page:
General Capability Questions
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 use Xmaze SAST to efficiently detect security issues and program defects in software source code that may lead to serious vulnerabilities and abnormal system operation, and accurately locate the alarm, effectively help developers eliminate vulnerabilities in the code, and protect the information security of the software.
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 Vulnerability Library] under the [Knowledge Base WIKI] module of the Xmaze SAST platform will update and display the latest vulnerability-related information in CWE, which will be updated and maintained by the product manufacturer.
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 about CWE and CWE compatibility could be found in Chapter 8 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):
The user enters [Knowledge Base WIKI->CWE Vulnerability Database], then enters the list of defects detected by each project project, enters and searches the corresponding CWE identifier in the [Defect Type] box, and then the corresponding defects can be retrieved. Click the [View] operation hyperlink to view the detailed information.
DOCUMENTATION OF FINDING CWE IDENTIFIERS USING ELEMENTS
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):
Security vulnerabilities and associated CWE identifiers, as shown in the image below:
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):
Under [Project Management -> Defect List], all the defect lists related to the project are displayed. By searching the CWE identifier, you can find out the corresponding vulnerabilities and perform corresponding operations on them.
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):
There is a clear CWE identifier and other relevant information in the details interface of each vulnerability.
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):
Display the identifiers and details of all CWE vulnerabilities in [Knowledge Base WIKI->CWE Vulnerability Database].
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 privided in elsx format, and the electronic documents have a list of CWE identifiers of the vulnerabilities, which can be directly checked or searched in the search box.
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:
Graphical User Interface (GUI) Questions
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 search icon in the upper right corner to search for the relevant CWE identifier, and the detailed information of the CWE identifier can be found 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):
For each scanned vulnerability, it will list the CWE identifier and related vulnerability descriptions and repair suggestions in the vulnerability details.
Questions for Signature
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
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
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