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-SCA

Capability home page:

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

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-SCA, 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-SCA".
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):

After logging in to the system, users can view all the mapping informationbetween CWE and the system vulnerability database in the "Data Retrieval"-> "CWE Retrieval" tab page of the navigation bar, and can use the "CWE" keyword search function to index the mapping between relevant CWE identifiersand vulnerability libraries. At present, looking for starling open sourcecomponent test management system has collected more than 2000 CVE defect data,which has a mapping relationship with CWE identification.

Step1: Click "Data Retrieval" in the menu to expand the "Data Retrieval" menu.
Step2: Click the "CWE Search" tab to open the CWE identification mapping database that has been included in the product.
Step3: Enter the CWE keyword to be searched (the query keyword is not case sensitive, such as: CWE100, CWE 100, CWE-100, CWE id 100, etc.).
Step4: Click the "Search" button, and the page will display the CWE identification information that matches the keyword.

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

Users can click "Username" -> "Help" -> "Download CWE Compatibility Instruction Manual" to get the CWE Compatibility Document, which describes in detail how the product meets the CWE compatibility requirements.

Step 1: Log in to ZBG-SCA, 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):

After logging in to the product workbench, users can view the mapping relationship between the detected vulnerabilities and CWE in the open source component test result set, and use the CWE identification search function in the product support vulnerability list (knowledge base). The test result set audit page also supports CWE keyword search to query the associated vulnerability.

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

Step 1:Log in to ZBG-SCA, click and expand the "Project detection" tab.
Step 2:Click the "Task Detection" tab to open the open source component test task list page.
Step 3:Find test tasks that completed successfully.
Step 4:Click the "Results" button to open the test result set page.

(2)On the test result set page, the "CWE ID" column details the CWE identifier mapped to each open source component vulnerability, and the CWE identifier can be directly linked to the official description page by clicking.

(3) The test result set page supports the vulnerability set search function of CWE keyword; users enter the CWE ID in the search box and click the "Search" button to filter the result data. The CWE ID search keyword includes and is not limited to cwe100, cwe100, cwe-100, cwe id 100 and other formats.

Step 1:Enter the CWE ID keyword in the search bar, such as "CWE79".
Step 2:Click the "Search" button to filter the test result data.
Step 3:The data matched with the search keyword identification will be displayed on the page, and you can clearly find the desired identification in the CWE identification column.
Step 4:Click the "Details" button will jump to the detailed vulnerability description page about this open source component, see the next step.

(4) Click the "Details" button in the search result set to open the detailed description page of the open source components with known vulnerabilities. On this page, the CVE vulnerabilities in the open source components and the CWE identifiers mapped to each vulnerability are listed in detail.

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 test result set page, the "CWE ID" column details the CWE identification mapped to each open source component vulnerability, and the CWE identification can be directly linked to the official description page by clicking.

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

After logging in to the system, users can view all the mapping information between CWE and the system vulnerability database in the "Data Retrieval" -> "CWE Retrieval" tab page of the navigation bar, and can use the "CWE" keyword search function to index the mapping between relevant CWE identifiers and vulnerability databases.Refer to the operation steps of <CR_6.1>.

After successfully logging in, users can view the mapping relationship between detected vulnerabilities and CWE in the open source component test result set, which is consistent with the CWE logo search function in the product support vulnerability list (knowledge base). The test result set audit page also supports CWE keyword search to find 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):

On the test result set page, the "CWE ID" column details the CWE identifier mapped to each open source component vulnerability, and the CWE identifier can be directly linked to the official description page by clicking.

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 logging in to the system, users can view all the mapping information between CWE and the system vulnerability database in the "Data Retrieval" -> "CWE Retrieval" tab page of the navigation bar, and can use the "CWE" keyword search function to index the mapping between relevant CWE identifiers and vulnerability databases.

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

On the test result set page, the "CWE ID" column details the CWE identifier mapped to each open source component vulnerability. And the mapping relationship between each CVE tag and CWE tag will also be displayed on the detailed description page containing known open source component vulnerabilities.

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 successfully logs in, click "Project Detection" -> "Task Detection" to open the open source component project test task list page, and click the "Result" button of the completed test task to open the test result set page (refer to <CR.5.2>).On the right side of the testresult set page, click the "Report" button to open the report configuration page. The user needs to specify the name of the report and the name of the organization to which it belongs, and specify the output format of the report.In the report of the format supported by the product, the user can easily find the required data through the CWE identification keyword. Here, the HTML report will be used to demonstrate the description.

Step 1:On the right side of the test result set page, click the "Export Report" button to open the report configuration page.
Step 2:Users needs to enter the current report name.
Step 3:Users need to enter their organization or company name.
Step 4 : Select the report format, in order to facilitate the demonstration of the subsequent steps, select "HTML" here.
Step 5 : Click the "OK" button after the configuration is complete, the browser will automatically download the HTML report file later, and the user can directly open the report file in the browser.

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 352", 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 methods 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 the report in the format supported by the product, each type of vulnerability and its CWE identification information with a mapping relationship are listed.

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

In the report in the format supported by the product, each type of vulnerability and its CWE identification information with a mapping relationship are listed.Users can view reports in HTML and PDF formats created by the product through browsers, PDF readers, and through the "Search" function carried by these tools, users can easily find the required CWE ID and the corresponding vulnerability information. 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