CWE

Common Weakness Enumeration

A Community-Developed List of Software & Hardware Weakness Types

2021 CWE Most Important Hardware Weaknesses
CWE Top 25 Most Dangerous Weaknesses
Home > Compatibility > CWE-Compatible Products and Services  
ID

Name of Your Organization:

CodeForce(Beijing)Software Technology Co., Ltd

Web Site:

http://www.codeforce.com.cn

Compatible Capability:

ZBG-SAST

Capability home page:

http://www.codeforce.com.cn/#/product/ZBG_SAST

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 www.codeforce.com.cn to apply for a trial account of ZBG-SAST, or send an email to support@codeforce.com.cn to apply for a trial account directly (the name of the product to be applied for trial needs to be indicated). Generally, we will reply to the user with product access address and trial account information assigned to the applicant by email within two working days.

Step 1:Visit "www.codeforce.com.cn" and click the "Partner" button on the page to open the product trial page and fill in the trial application information at the bottom of the page.
Step 2:Enter your organization or company name.
Step 3:Enter your address.
Step 4:Enter the industry in which you work.
Step 5:Enter your name.
Step 6:Enter your correspondence number.
Step 7:Enter your email address, which is used to receive email replies from the product access address and trial account assigned by the applicant.
Step 8:Select the product to use, here select "ZBG-SAST".
Step 9:Enter the verification code.
Step 10:Click the "Submit Application" button, and our mailbox will receive your trial application information.

Mapping Questions

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 click "Knowledge Management Platform" -> "Knowledge Management" in the navigation bar to view the detailed CWE mapping information, including the CWE version corresponding to the detailed vulnerability, the relationship between the internal defect name and its related CWE identifier, and the link to the official CWE description page.

Step 1:Log in to ZBG-SAST, click and expand the "Knowledge Management" tab.
Step 2:Click the "Knowledge Management" tab to open the vulnerability list page which supported by our product.
Step 3:Enter the keyword "CWE" in the search bar to filter the list of all vulnerabilities in the product that maintain a mapping relationship with the CWE identifier.
Step 4:Click any vulnerability name, such as "command injection" to load the description of the vulnerability.The CWE identifiers that maintain a mapping relationship with the vulnerability will be displayed in a list in the reference area.
Step 5:All CWE identifiers on this page can be linked to the official CWE description page.

For example,click "CWE ID 78", the page will jump to https://cwe.mitre.org/data/definitions/78.html.

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

Every time the product is updated, we will update the vulnerability database and the CWE identification information mapped by the vulnerability.We will do everything in our power to keep the most up-to-date CWE content in each version, and we will include the CWE-ID in the relevant vulnerabilities. The main version of ZBG-SAST is released every six months.

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

Our tools and documentation will be updated every six months after the major version of the product is released, and users will be able get the most up-to-date mapping relationship in each version.

Documentation Questions

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

After the user logs in to the product, click "Username" -> "Help" -> "Download CWE Compatibility Manual" to obtain the CWE Compatibility Document, which describes in detail how the product meets the CWE compatibility requirements.

Step 1:Log in to ZBG-SAST, and click on the user name in the upper right corner to open the product's additional function bar.
Step 2:Click the "Help" button to open the product help page.
Step 3:Click "Download CWE Compatibility Manual" on the product help page to get the CWE Compatibility Manual.

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

Users can view the mapping relationship between detected vulnerabilities and CWE in the static test result set of the source code after logging in to the product, which is consistent with the search function of CWE identifiers in the vulnerability list supported by our product (knowledge base). The audit page of test result set also supports using CWE keyword search to query related vulnerabilities.

(1)After the user successfully logs in, click "Project Detection" -> "Task Management" to open the source code project test task list page, and click the "Audit View" button of the completed test task to open the audit page of test result set.

Step 1:Log in to ZBG-SAST, click and expand the "Project Detection" tab.
Step 2:Click the "Task Management" tab to open the source code project test task list page.
Step 3:Find the successfully completed test task, and click the Audit View button to open the test result set audit page.

( 2 ) Click common classified vulnerabilities on the audit page of test result set to see the CWE mapping information about the vulnerability in the reference information bar on the right side.

Step 1:On the test result set audit page, click on common vulnerabilities, such as the "Command Injection" category.
Step 2 : Click the "Reference" information bar on the right to open the reference information page.
Step 3: The CWE identification information that has a mapping relationship with the vulnerability is displayed on the vulnerability reference information page.

( 3 ) The vulnerability set search function of CWE keywords is also available on the audit page of test result set; users can click the search button to open the keyword search page. On this page, select "Industry Standard" for the condition category, and enter the desired query in the operation value column. CWE identifies a keyword and clicks the "Query" button to immediately query the associated vulnerability set. The CWE identification keyword includes but is not limited to formats such as cwe100, cwe 100, cwe-100, cwe id 100, and the like.

Step 1 : On the test result set audit page, click the search button to open the vulnerability query page.
Step 2:Condition category option, select the "Industry Standard (ID search with CWE support)" tab.
Step 3:In operation value, enter the CWE identification keyword to be queried, such as "cwe-77".
Step 4:Click the "Query" button, and the test result set audit page will refresh and only display the vulnerabilities associated with the CWE identification keywords.

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

On the audit page of test result set, click common classified vulnerabilities, and you can view the CWE mapping reference information about the vulnerability in the reference information bar on the right.There is a mapping relationship between the explanation of the vulnerability and the official information linked to the CWE identifier listed below.

Step 1 : On the test result set audit page, click Common Vulnerabilities, such as the "Command Injection" category.
Step 2 : Click the "Reference" information bar on the right to open the reference information page.
Step 3:Click on the corresponding CWE ID in the reference material to open the official description page of the CWE identifier.
Step 4: There is a Chinese description of the vulnerability below the reference, which also refers to and translates the official description from CWE.

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

Refer to <CR_5.1>, users can download the CWE Compatibility Manual.Users can get a list of mappings between the vulnerability set and the product's CWE identifier in the appendix at the end of this manual.

Type-Specific Capability Questions

Tool 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 can click "Knowledge Management Platform" -> "Knowledge Management" in the navigation bar to view the detailed CWE mapping information, including the CWE version corresponding to the detailed vulnerability, the relationship between the defect name and its related CWE identifier, and the link to the official CWE description page. Refer to the operation steps of <CR_6.1>.

After logging in to the product, users can view the mapping relationship between detected vulnerabilities and CWE in the static test result set of the source code, which is consistent with the search function of CWE identifiers in the vulnerability list supported by our product (knowledge base). The audit page of test result set also supports using CWE keyword search to query for associated vulnerabilities.Refer to the operation steps of <CR_5.2>.

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 vulnerability security test of the source code project is completed, click common classified vulnerabilities on the audit page of test result set to view the CWE mapping reference information about the vulnerability in the reference information bar on the right.Click the corresponding CWE ID to open the official description page of the CWE identifier.User can also find the description information of the vulnerabilities in Chinese at the bottom of the reference materials, is the Chinese description information about the vulnerability. These information is translated from the official instructions from CWE.Refer to <CR_5.3>.

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 click "Knowledge Management Platform" -> "Knowledge Management" in the navigation bar to view the detailed CWE mapping information, and search for all the vulnerabilities with mapping relationships in the product by retrieving the "Common Weakness Enumeration" or "CWE" keyword search function.

USING CCR TO PROVIDE CLAIMED CWE IDENTIFIER COVERAGE <CR_A.2.4>

Give a detailed explanation of how a user can find the Coverage Claim Representation (CCR) XML document with all of the CWE Identifiers that the owner claims the tool is effective at locating in software (recommended):):

Currently we do not provide CCR XML documentation.

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

The CWE tag information associated with the vulnerability will be available for users to view in the form of reference materials on the audit page of test result set.

SELECTING TASKS WITH A LIST OF CWE IDENTIFIERS <CR_A.2.7>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CWE identifiers (recommended):

Please refer to <CR_A.2.1>.

SELECTING TASKS USING INDIVIDUAL CWE IDENTIFIERS <CR_A.2.8>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CWE identifiers (recommended):

Please refer to <CR_A.2.1>.

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 user searches for the CWE identifier but there is no result, the page will prompt "No data yet".

Media Questions

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

After the user logs in to the product, click "Project Detection" -> "Task Management" to open the source code project test task list page, select the completed test task, and click the "Report" button to open the report configuration page.The user needs to specify the report name and the name of the organization,the length and output format of the report can be specified in the following configuration.And in the detailed reports in various supported formats (the length of the complete vulnerability description), users can easily find the required data through the CWE identification keywords, and the HTML report will be used here to demonstrate the description.

Steps to export test report:

Step 1:Log in to ZBG-SAST, click and expand the "Project Detection" tab.
Step 2:Click the "Task Management" tab to open the source code project test task list page.
Step 3 : Select the completed source code security vulnerability testing task in the checkbox.
Step 4:Click the "Export" button to open the report configuration page.
Step 5:Users need to enter the current report name.
Step 6:Users need to enter the user's organization or company name.
Step 7 : Select the report format, in order to facilitate the demonstration of the subsequent steps, select "HTML" here.
Step 8 : Select the report type, the detailed report contains detailed reference information for each vulnerability, including CWE identification.
Step 9:After the configuration is complete, click the "Export button" and the browser will display the report content in a new tab later.

Search the report for the CWE identifier:

Step 1:Users can usually use the shortcut "Ctrl + F" to open the browser search window, enter CWE identification keywords, such as "CWE ID 78", the browser will automatically help users locate the content.

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

<CR_B.3.1> Configuration settings for creating various report formats are provided, and the steps required to use the CWE identifier search function in HTML detailed reports are also demonstrated. In various formats of reports (detailed reports), the product lists each vulnerability and its CWE identification information with a mapping relationship.

ELECTRONIC DOCUMENT ELEMENT TO CWE IDENTIFIER <CR_B.3.3>

Provide example documents that demonstrate the mapping from the capability’s individual elements to the respective CWE identifier(s) (recommended):):

The description of the implementation method of mapping CWE identifiers to specific vulnerabilities can be implemented through the "CWE Compatibility Instruction Manual". Refer to <CR.5.1>.

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.2>.

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

Each vulnerability and its CWE identification information with mapping relationship are listed in various formats of reports (detailed reports). Users can view reports in different formats generated by the product through browsers, PDF readers, office word, and text editors. Through the "search" function carried by these tools, users can easily find the required CWE ID and Vulnerability information corresponding to it.Refer to <CR_B.3.1>.

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: Wei 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: Wei 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: Wei Gao

Title: Product Manager

More information is available — Please select a different filter.
Page Last Updated: March 01, 2022