Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

SecZone

Web Site:

https://www.seczone.cn/

Compatible Capability:

SFuzz

Capability home page:

https://www.seczone.cn/channels/SDL-Fuzz.html

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 SFuzz: https://www.seczone.cn/channels/SDL-Fuzz.html, as shown in the figure below.

   

2. Click on the "Apply for trial" button, as shown in the figure below.

   

3. Enter the application information, click the "Submit" button to submit the application, as shown in the figure below.

   

4. After receiving the application, we will send the system login address, user name, password and user manual to your email address.

5. Log in to the SFuzz system using username and password, as shown in the figure below

   

6. Click on the "Web API Fuzz Test" to create a new test，as shown in the figure below.

   

7. After the test is completed, enter the corresponding test details page to view the CWE number information of all defects , as shown in the figure below.

   

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

For each new release, SFuzz will use the latest version of CWE content by MITRE.

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 will release a new version every quarter. In the new version, we will synchronously update the latest CWE content.

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 a new version every quarter and send updates to our customers via email, including updates from CWE.

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

Detailed information can be found in Chapter 6, Section 2 of the SFuzz User Manual, as shown in the figure 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):

After the test, the user can search for the CWE number to find associated defect information. By clicking the "Details" button in the search results, the user can enter the defect details page to view the detailed information of the defect，as shown in the figure below.

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 have provided the URL, Description, Extended Description, and other content including CWE in the user manual, as shown in the figure below.

DOCUMENTATION INDEXING OF CWE-RELATED MATERIAL <CR_5.4>

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

N/A. The documentation of SFuzz does not have an index. However, the CWE content can be searched easily in the documentation.

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

On the Web API Fuzzing page, the user can find the test task of the defect associated with CWE by entering the CWE ID, as shown in the figure 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):

1. On the defect details page, click on "View Report" to jump to the online report page, as shown in the figure below.

   

2. On the online report page, you can click on CWE ID to view the detailed information of CWE, as shown in the figure below.

   

3. CWE information is shown in the figure below.

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

After the completion of Fuzzing, the detected defects are automatically associated with the CWE number. On the defect details page, users can click on "CWE number" to jump to the CWE details page, as shown in the figure below.

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

SFuzz users can view test reports online, and the CWE IDof each defect can be linked to the CWE website. They can search for defect information by entering the CWE ID in the search bar. We also provide electronic documents in HTML and PDF formats for users, supporting searching by their full name or CWE ID.

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 relationships of CWE in online or electronic format, The format of the document is HTML or PDF. Users can find relevant CWE information by searching for keywords.

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

1. On the defect repository page, users can search for defect information by searching for CWE ID,as shown in the figure below.

   

2. This is the defect information page containing the CWE ID,as shown in the figure below.

   

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

1. On the test details page, click the "Edit" button to open the editing window,as shown in the figure below.

   

2. In the editing window, select the CWE ID from the dropdown to establish the mapping relationship between defects and CWE,as shown in the figure below.

   

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

After the Fuzzing is completed, the user can choose to generate a test report in HTML or PDF format. The report contains CWE related details. These files can be used to find defects through a searcher,as shown in the figure below.

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: Xianfeng Huang

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: Xianfeng Huang

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: Xianfeng Huang

Title: Product Manager