Name of Your Organization:
QI-ANXIN Technology Group Inc.
QI-ANXIN OSS Security
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 visit the homepage (https://www.qianxin.com/product/detail/pid/370) and apply for trial use of the QI-ANXIN OSS Security by clicking the "Consult" button shown below.
For paid users, they can visit the URL (https://oss.qianxin.com) or the private deployment address and enter their accounts and passwords to access and use the QI-ANXIN OSS Security.
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):
First, it’s necessary to introduce six parts in the navigation bar from left to right: Homepage, Project Management, Component Management, Vulnerability Management, Protocol Lists, Statistics & Analysis, and System Management.
When QI-ANXIN OSS Security detects CWE information associated with a vulnerability, such information will be shown in the Vulnerability Management --> Vulnerability List --> Vulnerability Detail interface as marked with the red box shown below.
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):
We update the vulnerability database (i.e., Knowledge Base) every day based on information provided by mainstream vulnerability communities around the globe and analyze associated CWEs to ensure CWE effectiveness, timeliness, and completeness.
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 online vulnerability database, i.e., the Knowledge Base of QI-ANXIN OSS Security deployed online is updated every day, and the Knowledge Base deployed offline is updated along with customers’ updating frequencies, usually, every two weeks or every one month. CWE-related information will be updated accordingly.
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):
Users can get the content of CWE-Compatibility in QI-ANXIN OSS Security’s user guide, as shown below:
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):
When detected via QI-ANXIN OSS Security, vulnerabilities will be shown in the Vulnerability Management – Vulnerability List interface. Customers can use CWE identifiers to find more information about security elements. For example, put "CWE-502" in the search box as shown below, and users will know the number of tasks affected in each project.
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):
When a vulnerability is detected, users can use associated CWE vulnerability information (e.g., put the vulnerability type of "injection" in the search box) to search and get CWE identifiers and other related information on the Vulnerability Management --> Vulnerability List --> Vulnerability Detail interface.
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):
Please refer to <CR_5.3>.
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):
Log in the QI-ANXIN OSS Security system, select Vulnerability Management --> Vulnerability List, and search vulnerabilities via CWE identifiers. Here, we put "CWE-502" in the search box.
Click the matching vulnerability in the list (here we choose the first in the list), go to the "vulnerability overview" tab, and users can see the CWE details marked with the red box shown below.
Click the "Impact Scope" tab in the details page, and users can find tasks, components, and projects affected by the CWE vulnerability, as marked with the red box shown below.
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):
After the detection process completes, go to Project Management --> All Projects –> Task List and users will see all tasks and their detection status. Select a task, click the hyperlinked task name on the left part of each task and users will see detailed detection results.
On the detailed detection results page, click the Vulnerability Information tab, you’ll see details of vulnerabilities detected and their associated CWE information (marked with the red box).
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 Management --> Vulnerability List page, users can get information about all vulnerabilities with CWE identifiers detected by QI-ANXIN OSS Security, as shown below, marked with red boxes.
Or users can go to the vulnerability details page, click the hyperlinked CWE identifiers, and they will be directed to the official CWE website for more information.
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):
In the Vulnerability Management --> Vulnerability List page, users can obtain or check all vulnerabilities associated with all tasks, including CWE-related information.
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):
We provide reports in various formats, including Word, Excel, and PDF. For example, users can search CWE-related text in the Word report by pressing Ctrl+F and typing search words.
A sample electronic report is as follows:
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):
Vulnerabilities detected by QI-ANXIN OSS Security will be shown in the "Vulnerability" Section of our electronic report, and you can find CWE-related information in the Reference sub-section.
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):
Please refer to <CR_A.2.1>.
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):
Please refer to <CR_A.2.1> and <CR_A.2.3>.
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: Liu Yan
Title: Product Manager
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: Liu Yan
Title: Product Manager
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: Liu Yan
Title: Product Manager