Name of Your Organization:
Beijing Anpro Information Technology Co. LTD
Xshark RASP Self-Adaptive Threat Immunity 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):
Xshark RASP(Runtime Application Self-Protection) enables applications to gain self-immunity against attacks after launching, including common network attacks, malicious Web Shell exploits, and 0-Day attacks. It can provide customers with the built-in capability of application security without modifying the existing application source code, and implement the default security of the application.
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 Xshark RASP 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 5 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):
As specified in the user manual, when the application is found to be maliciously attacked, the user clicks [event analysis] and searches for the corresponding CWE identifier, displays the vulnerability information mapped to the CWE identifier. Click the hyperlink of the vulnerability name to view 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):
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
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):
Xshark RASP provides the supported attack types and their corresponding CWE identifiers in the user manual. You can view the CWE mapping of related weaknesses, vulnerability descriptions and recommendations in the user manual.
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):
When an attack event is recorded by Xshark RASP, the CWE identifier corresponding to the attack event can be viewed in the event analysis, or related events can be retrieved according to the CWE identifier.
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 list of attack event in Xshark RASP, the CWE identifier corresponding to each attack event can be checked.
In the detailed description of the attack event, you can also check the corresponding CWE identifier and its link address on the CWE official website.
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):
The current coverage of CWE by Xshark RASP can be found in the user manual.
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:
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):
In the attack event, enter the CWE identifier you want to filter in the CWE identifier filter box, and click the "Filter" button to display all attack events matching this identifier on 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>.
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
More information is available — Please select a different filter.