Name of Your Organization:
Beijing Anpro Information Technology Co. LTD
Xcheck OSS threat management 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):
Xcheck OSS provides users with online download links or offline upgrade packages for database upgrades or system upgrades.
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 source authentication OSS 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.
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):
This description can be found in Chapter 11 Common Vulnerability List-CWE of the Xcheck OSS Operation Manual. See the screenshot for details. The user manual can be used for authorized 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 over, the user searches for the corresponding CWE number, displays the vulnerability information mapped to the CWE number, clicks on the vulnerability details, and enters the vulnerability details page to view the vulnerability details. Please check the screenshot.
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):
The user operation manual provides a list of each test performed by the tool and the related CWE logo (or other coding rules), as shown in the figure:
DOCUMENTATION INDEXING OF CWE-RELATED MATERIAL
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 supported CWE tags are listed in the source authentication OS data management table. Corresponding to (in the header CWE number) view the list of supported CWE identifiers.
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 application package review/runtime monitoring task is executed by the source authentication OSS, click the task details to view the CWE identifier mapped to the component vulnerability, as shown in the figure:
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):
Xcheck OSS monitors the task details GUI interface during application package review/runtime, and the obtained component vulnerability details fully map the CWE identifier, as shown in the figure:
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