Name of Your Organization:
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):
Open the official website of Seczone https://www.seczone.cn/, as shown in Figure 1.
Figure-1 System Homepage
Click the "Apply for trial" button, as shown in Figure 2.
Figure-2 Tool Trial Portal
Enter the application information, click the "Submit" button to submit the application, as shown in Figure 3.
Figure-3 Submit application information
After receiving the application, we will send the system login address, user name, password and user manual to your email address.
After receiving the email, the user can login to the SAST system with the login information received, as shown in Figure 4.
Figure-4 System Login Homepage
Click [Project Management] module to create a new project, as shown in Figure 5.
Figure-5 Create Test Project Interface
After the test is completed, click the project list "View" button to enter the vulnerability information query page, and the CWE information can be viewed in the defect information area, as shown in Figure 6.
Figure-6 Project Scan Results Query Interface
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):
Users can view CWE information through the product homepage (one of the sources of tool vulnerability information is CWE), as shown in Figure 7.
Figure-7 System Version Information
Click on the vulnerability icon to jump to the CWE official website, as shown in Figure 8.
Figure-8 CWE Official Website
We release our products once a quarter, and we will add the latest CWE contents to each new version of “CWE Mapping Relations” for users to view.
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):
If the defect item we add or modify has a corresponding CWE number, we will add the CWE number to the configuration information of the defect item, so that users can view the corresponding CWE information when viewing the defect.
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):
We will release our products quarterly and users can access the updated mapping relationships in each version.
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):
Our CWE documentation describes CWE and CWE compatibility at the beginning of this article, by quoting the description of CWE and CWE compatibility on the official CWE website. Users can view CWE through the product homepage, and click View Version Information to view CWE mapping information. At the same time, users can view the defect type and CWE mapping relations in the interface of the tool, as shown in Figure 9 and Figure 10:
Figure-9 Data Source Contains CWE
Figure-10 Mapping relations between vulnerability type and CWE
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):
You’re allowed to edit the vulnerability type corresponding to each CWE Identifier, and you can modify the specific correspondence after clicking “Edit”. We will store the related information to each CWE Identifier in the database, as shown in Figure 11:
Figure-11 Edit Vulnerability Type Mapping CWE Identifier
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):
Users can view CWE information through the product homepage (one of the sources of tool vulnerability information is CWE), as shown in Figure 12.
Figure-12 System Version Information
Click on the vulnerability icon to jump to the CWE official website, as shown in Figure 13.
Figure-13 CWE Official Website
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 reference is at the end of our CWE Documentation as below.
And the user can view CWE through the product homepage (click the help button in the upper right corner.)
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):
Users click "new project" on the project list page to create a new project and automatically analyze the security defects in the code. On the create project page, enter the project name and import the project source code, as shown in Figure 14.
Figure-14 Create projects (1)
Click "Next" to select the task type, as shown in Figure 15.
Figure-15 Create projects (2)
Click "Next" to configure the task parameters, create and execute the scan task, as shown in Figure 16.
Figure-16 Create projects (3)
After the detection is completed, you can view the results, as shown in Figure 17.
Figure-17 Project details in the CWE Identifier
During the scanning results, you can click on the CWE Identifier to view the official website link to further view the details of the CWE, as shown in Figure 18:
Figure-18 CWE Identifier Details
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 detection rules configuration page, enter the CWE number to find the corresponding vulnerability, as shown in Figure 19:
Figure-19 Configuration page CWE query
The user can enter the details of the vulnerability type page to modify and edit the CWE Identifier corresponding to each vulnerability type, as shown in Figure 20:
Figure-20 CWE Identifier editing
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):
Check the scan results through the list of items, as shown in Figure 21:
Figure-21 Project details in the CWE Identifier
In the scan result page, click on the CWE Identifier, the page will jump to the official website link corresponding to the CWE Identifier, as shown in Figure 22.
Figure-22 CWE Identifier Details
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):
Our electronic document format is Excel. So users can easily search for specific CWE-related text by keyword searching. For example, we open a document, press "Ctrl + F" to search for CWE 211, as shown in Figure 23:
Figure-23 Search for specific CWE-related text in the Excel document
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):
We list the mapping relationship in the form of a table, and the document format is Excel. Users can easily find the relevant CWE ID by searching component serial number or component keyword.
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):
We will add the display of vulnerabilities in the project scan results according to the CWE Identifier, which currently supports the display according to OWASP Top 10 2021, etc., as shown in Figure 24:
Figure-24 Vulnerability Display Page
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):
In the detection rules configuration page, enter the CWE number to find the vulnerability corresponding to the specified CWE number, as shown in Figure 25:
Figure-25 Configuration Page CWE Identifier Query
The query results can display the CWE number and the corresponding vulnerability rule details, as shown in Figure 26:
Figure-26 Configuration Page CWE Query Results
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):
Documents may be exported in XLS and the user can use their own search function by searching keyword. And the documents in XLS will have a column named "CWE" whose content is the associated CWE ID(s).
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: Chao Gao
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: Chao Gao
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: Chao Gao
Title: Product Manager