Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

GYSecurity Technology Co., Ltd

Web Site:

https://www.gysecurity.cn

Compatible Capability:

Swift Fuzzer Testing Tool

Capability home page:

https://www.gysecurity.cn/fuzzer.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 Swift Fuzzer: https://www.gysecurity.cn/fuzzer.html, Click on the “Get Demo” button, as shown in the figure below.

   

2. Enter the application information and click the “Get Demo” button to submit the application.

   

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

4. The user can log in to the Swift Fuzzer system with the login information received.

   

5. Click the "Quick Test" button, select the protocol suite to be tested, and then click the "Start" button to enter the configuration and rule selection interface of the testing device. Execute the fuzzy test until the task is completed and view the results.

   

6. In the test suite supported by the Swift fuzzer tool, each test rule supports CWE associated vulnerability information that can be displayed and viewed.

   

   

7. Clicking on the supported CWE vulnerability number will redirect to the official CWE website link.

   

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 the support for CWE vulnerability database through the product homepage.

We release our product twice every year. And we will add the most recent CWE content to the "CWE Mapping Relations" in each new version. The user can review it.

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 download the component's CWE vulnerability in real time every day and update it to the local database. We release our products twice a year, and each release will update the 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 release our product twice every year. The user can get updated mapping relations in each release.

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

For detailed information, please refer to Chapter 6.1 of the Swift_ Fuzzer User Manual- V2.28, as shown in the following figure. At the same time, in CWE Documentation CR_6.1.

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 fuzz testing task is completed, you can view the list of CWE vulnerability issues affected in the evaluation.

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

Sections 1.2 and 1.3 located in the Fuzzy Testing Report file.

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

Please refer to section CR_6.1.

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

Please refer to section CR_5.2.

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

In the test suite supported by the Swift fuzzer tool, 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.

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

Users can search and locate specific CWE IDs on the 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 test rule entry of the Swift fuzzer tool, corresponding to different CWE lists, the mapping relationship can be queried by clicking.

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 testing is completed, the user can choose to generate a test report in HTML or PDF or Word 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: Chao Tan

Title: CPO

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 Tan

Title: CPO

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 Tan

Title: CPO