Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

ValiantSec Technology Co., Ltd

Web Site:

https://www.unisca.cn/index

Compatible Capability:

UniSCA

Capability home page:

https://www.unisca.cn/use

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

1. Open the official website of CodeAnt, which is https://www.unisca.cn/index. And you should first click the button "(enterprise)" in the top red box, Fill in the information and apply for the trial，as shown in the Figure-1 .

   

   Figure-1 UniSCA's official website

2. After receiving the application, we will send the system login address, user name and user password. Click the button "(Login)" ，as shown in the Figure-2.

   

   Figure-2 Login

3. After the user can login to the Unisca system, Then the user start using our product, as shown in the Figure-3.

   

   Figure-3 UniSCA's Homepage

4. After your registrations are registered，the user can login to the UniSCA system, as shown in the Figure-2.Then the user login and start using our product, as shown in the Figure-4.

   

   Figure-4 UniSCA's dashboard

5. Click the "SCA" module to create a new project，and the user can upload the file to analysis，as shown in Figure-5.

   

   Figure-5 Start up new project

6. After the analysis is completed， the user can view the results，as shown in the Figure-6.

   

   Figure-6 Project Scan Result

7. The user can view the CWE information in the vulnerability details area， as shown in the Figure-7.

   

   Figure-7 Vulnerability details

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

We will display the latest data set updates on the "Explore" page of the UniSCA official website, including the latest CWE vulnerabilities and their details. Users can learn about the latest update scope of the UniSCA knowledge base on this page.

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 release a version every month，we will update the vulnerability database and the CWE identification information. We will try our best to update the most recent CWE content in each version.

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

UniSCA is update every month, our customers get updated mapping relations in each version. We use the CWE 4.12 version, which release date is June 29, 2023. Most rules of CWE have been described in Chinese, and the latest update date at August 01, 2023

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

We will describe information related to CWE and CWE compatibility in the UniSCA white paper. You can download this white paper on our official website(https://www.unisca.cn/index). The text copy content is "CWE is a software security strategic project funded by the National Computer Security Department of the United States Department of Homeland Security, and is the world's most well-known and authoritative library of software security vulnerability patterns. The certification indicates that the product can support the detection of major international vulnerability (defect) modes, so it is widely recognized by users and security management personnel as an important level mark of the product. For example, many international frontline manufacturers and institutions such as Synopsys, Veracode, and Checkmark have passed CWE international compatibility certification for their products."

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

We will describe information related to the specific details of how your customers can use CWE identifiers to find the individual security elements in the UniSCA white paper. You can download this white paper on our official website(https://www.unisca.cn/index).The text copy content is "CWE identification retrieval allows you to view all vulnerability information in the Asset Management Vulnerability Library interface, and search for ‘CWE’ to query all numbered CWE vulnerabilities and detailed information. You can view all vulnerability information in the Asset Management Vulnerability Library interface, and click on the vulnerability details to view the CWE number and detailed information of the vulnerability on the pop-up page on the right."

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

We will describe the process a user would follow to find the CWE identifiers associated with individual security elements in the UniSCA white paper.You can download this white paper on our official website(https://www.unisca.cn/index).The text copy content is "You can view all vulnerability information in the Asset Management Vulnerability Library interface, and click on the vulnerability details to view the CWE number and detailed information of the vulnerability on the pop-up page on the right."

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

In "Asset Management" - "Security Vulnerabilities", you can view all vulnerability information in the project. Enter the CVE number in the search bar to find the vulnerability and its associated CWE number with identifier. As shown in the Figure-8.

Figure-8 "Asset Management" - "Security Vulnerabilities"

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 clicking on the vulnerability number, you can view the details of the vulnerability, including CVE number, CWE number, NVD number, CNNVD number, and other basic information. As shown in the Figure-9.

Figure-9 "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):

Users can view the specific information detected by this scanning task in the "Task Details", which includes security vulnerabilities. As shown in the Figure-10.

Figure-10 "Task Details"

Users can view all vulnerabilities detected in this task and their CWE identifiers in "Task Details" - "Security Vulnerabilities". As shown in the Figure-11.

Figure-11 "Security Vulnerabilities"

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

Users can view all vulnerabilities and their CWE identifiers within this project in "Asset Management" - "Software Assets" - "Security Vulnerabilities", and can also view the number and details of the affected projects of the vulnerability. As shown in the Figure-12.

Figure-12 "Impact items associated with vulnerability numbers"

NON-SUPPORT NOTIFICATION FOR A REQUESTED CWE IDENTIFIER <CR_A.2.9>

Provide a description of how the tool notifies the user that a task associated with a selected CWE identifier cannot be performed (recommended):

When the scanning task cannot be associated with the CWE identifier or the scanning fails, the system will automatically record and display it in the "System Feedback". As shown in the Figure-13.

Figure-13 "System feedback"

SERVICE COVERAGE DETERMINATION USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of the different ways that a user can use CWE identifiers to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):

1. Providing a list. The path is "Project Details-Task Details-Security Vulnerability". Users can view all vulnerabilities(This project) here and view all security elements of the vulnerability by clicking on the CWE identifier. As shown in the Figure-14.

   

   Figure-14 "Project Details-Task Details-Security Vulnerability"

2. Providing a list. The path is "Asset Management - Software Assets - Security Vulnerabilities". Users can view all vulnerabilities(All project) here and view all security elements of the vulnerability by clicking on the CWE identifier. As shown in the Figure-15.

   

   Figure-15 "Asset Management - Software Assets - Security Vulnerabilities"

3. By search identifier. The path is "Asset Management - Software Assets - Security Vulnerabilities - Search bar". Users can retrieve identifiers here to find corresponding vulnerabilities. As shown in the Figure-16.

   

   Figure-16 "Search Bar"

FINDING CWE IDENTIFIERS IN SERVICE REPORTS USING ELEMENTS <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CWE identifiers for the individual security elements in the report (required):

1. After clicking on a component name, users can view the component details, which includes a list of all vulnerability information for that component. As shown in the Figure-17.

   

   Figure-17 "clicking on a component name"

2. Click on a vulnerability in this list to view its details, including detailed information such as CWE identifiers. As shown in the Figure-18.

   

   Figure-18 "Click on a vulnerability in this list"

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.3.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 service is effective at locating in software (required):

Users can search for the CWE identifier in the "Security Vulnerability" search bar to obtain a list of all CWEs and their associated vulnerabilities and vulnerability details. As shown in the Figure-19.

Figure-19 "obtain a listing of all of the CWE identifiers"

SERVICE'S PRODUCT UTILIZATION DETAILS <CR_A.3.6>

Please provide the name and version number of any product that the service allows users to have direct access to, if that product identifies security elements (recommended):

Users can view all system versions, engine versions, system update logs, knowledge base details, and other information in 'About System'. If users have version update packages stored locally, they can update or rollback versions at any time. As shown in the Figure-20.

Figure-20 "About System"

FINDING ONLINE CAPABILITY TASKS USING CWE IDENTIFIERS <CR_A.4.1>

Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CWE identifier or through an online mapping that links each element of the capability with its associated CWE identifier(s) (required):

refer to <CR_A.3.3>

ONLINE CAPABILITY CGI GET METHOD SUPPORT <CR_A.4.1.2>

If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):

Yes

FINDING CWE IDENTIFIERS USING ONLINE CAPABILITY ELEMENTS <CR_A.4.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CWE identifiers for the individual security elements in the report (required):

After uploading the package online, users can click on the component in the detection results to view the vulnerability, and in the vulnerability details, they can view the CWE identifier. As shown in the Figure-21.

Figure-21 "CWE identifiers by online detection"

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.4.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 online capability’s repository covers (required):

If users use UniSCA online, they can access the knowledge base in real-time through the interface to view the basic information of all CWE identifiers and details. If users use UniSCA offline, they can update the latest knowledge base information through offline packages. UniSCA's knowledge base updates data daily from 23:00 to 24:00.

ONLINE CAPABILITY ELEMENT TO CWE IDENTIFIER MAPPING <CR_A.4.5>

If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CWE identifier(s), otherwise enter N/A (required):

If the package uploaded by the user can be successfully scanned, the detailed information of each component can be viewed, and then the CWE identifier associated with it can be viewed. If the scan fails, the system will automatically record this information and provide feedback to the UniSCA data group. We will provide user feedback within 24 hours.

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 detailed instructions on how to search for CWE identifiers and view detailed information in the UniSCA User Manual. Users can download this user manual on the UniSCA official website(https://www.unisca.cn/index). Specifically, it includes the following paths:

1. "Project Details-Task Details-Security Vulnerability".
2. "Asset Management - Software Assets - Security Vulnerabilities".
3. By search identifier. The path is "Asset Management - Software Assets - Security Vulnerabilities - Search bar".

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

1. Users can export detection reports in 'Task Details'. As shown in the Figure-22.

   

   Figure-22 "export detection reports"

2. Users can view the basic information of the scan results in the detection report, and view the vulnerability details of each component and its associated CWE identifier. As shown in the Figure-23.

   

   Figure-23 "detection reports"

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

refer to <CR_A.3.3>

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

refer to <CR_A.3.3>

GUI EXPORT ELECTRONIC DOCUMENT FORMAT INFO <CR_B.4.3>

Provide details about the different electronic document formats that you provide for exporting or accessing CWE-related data and describe how they can be searched for specific CWE-related text (recommended):

refer to <CR_B.3.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: Zhe Wang

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: Zhe Wang

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: Zhe Wang

Title: Product Manager