Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Shanghai Feiyu Technology Co.,Ltd.

Web Site:

www.feysh.com

Compatible Capability:

Corax

Capability home page:

http://feysh.com

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 apply for a trial account of corax by visiting www.feysh.com, or by sending an email to contact@feysh.com To apply for a trial account, usually, the product access address and trial account information assigned to the applicant will be replied by email within two working days.

Step 1: visit "www.feysh.com", move the mouse to the "technical support" button on the home page, and click "contact us" to fill in the trial application information.

Step 2: enter your organization or company name (required)

Step 3: enter your position (optional)

Step 4: enter your area (optional)

Step 5: enter your email address to receive email replies from the product access address and trial account assigned by the applicant (required)

Step 6: enter your contact information (required)

Step 7: enter the channel through which you know this product (required)

Step 8: enter the products you are interested in (required)

Step 9: click the "submit" button, and we will receive your application information through email.

Users can use the login information received to log in to the corax system

1. Click "create project" on the home page to create a new project, as shown in Figure 1;
2. In the project list, view the created project, as shown in Figure 2;
3. Create the corresponding sweeping task in the project, as shown in Figure 3;
4. After the test is completed, you can view the corresponding test results in the task list, as shown in Figure 4 and figure 5

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

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 "standard" - > "tag" in the navigation bar to view the detailed CWE mapping information, including the CWE rule number corresponding to the detailed vulnerability, the corresponding rule name, and the link to the official CWE description page. At the same time, on the "standard" - > "data source" page, you can view the CWE profile and the CWE official website address.

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

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

1.After logging into the system, the user can select the "standard" module in the "standard" menu, click any item under the "label" to enter the details page, and display the corresponding CWE ID rules and details. As shown in Figure 1; Figure 2

2.After logging in to the system, the user selects the "data source" module in the "standard" menu. On this page, the user can view the CWE official profile and the CWE official website URL link. As shown in Figure 3

Figure 1

Figure 2

Figure 3

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

The user clicks the "Project" page in the navigation bar to enter the item list. After selecting an item, click to enter the scanning task list page. Click again to enter the defect details page. Search through CWE ID in the upper right corner of the defect list. After clicking to enter, the corresponding CWE ID rules are displayed.

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

By clicking the "filter" button in the defect list page, the user can filter the corresponding CWE ID by rules or by tags. As shown in Figure 1 ，Figure 2 and Figure 3

Figure 1

Figure 2

Figure 3

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_6.1> Users can click "standard" - > "tag" in the navigation bar to view the detailed CWE mapping information, including the CWE rule number corresponding to the detailed vulnerability, the corresponding rule name, and the link to the official CWE description page. At the same time, on the "standard" - > "data source" page, you can view the CWE profile and the CWE official website

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

Refer to <CR_6.1> Users can click "standard" - > "tag" in the navigation bar to view the detailed CWE mapping information, including the CWE rule number corresponding to the detailed vulnerability, the corresponding rule name, and the link to the official CWE description page. At the same time, on the "standard" - > "data source" page, you can view the CWE profile and the CWE official website

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

By clicking the "project" page in the navigation bar, the user enters the project list. After selecting an item, the user enters the task list page. After clicking the scanned task, the user clicks enter in the defect list page to display the specific defect details. See <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):

Refer to <CR_6.1> Users can click "standard" - > "tag" in the navigation bar to view the detailed CWE mapping information, including the CWE rule number corresponding to the detailed vulnerability, the corresponding rule name, and the link to the official CWE description page. At the same time, on the "standard" - > "data source" page, you can view the CWE profile and the CWE official website

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

We don’t provide the CCR XML document yet.

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

please refer to <CR_5.2>

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_6.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_6.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 you search for a CWE ID and there are no results, the user is notified that the task associated with the selected CWE identifier cannot be performed.

SERVICE COVERAGE DETERMINATION USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of the different ways that a user can use CWE identifiers to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):

By clicking the "project" page in the navigation bar, the user enters the project list. After selecting an item, the user enters the task list page. After clicking the scanned task, the user clicks enter in the defect list page to display the specific defect details. Please refer to<CR_2.4>

FINDING CWE IDENTIFIERS IN SERVICE REPORTS USING ELEMENTS <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CWE identifiers for the individual security elements in the report (required):

In the process of exporting reports, users can filter the export reports according to cwe-id.

SERVICE'S PRODUCT UTILIZATION DETAILS <CR_A.3.6>

Please provide the name and version number of any product that the service allows users to have direct access to, if that product identifies security elements (recommended):

Corax V2.2.4

FINDING ONLINE CAPABILITY TASKS USING CWE IDENTIFIERS <CR_A.4.1>

Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CWE identifier or through an online mapping that links each element of the capability with its associated CWE identifier(s) (required):

The user can query by searching cwe-id in "defect list"; after entering the details, the user can view the specific defect details displayed under this ID

ONLINE CAPABILITY INTERFACE TEMPLATE USAGE <CR_A.4.1.1>

Provide a detailed description of how someone can use your "URL template" to interface to your capability's search function (recommended):

The user can enter the corresponding cwe-id page by clicking the following link http://192.168.50.196:9006/#/rule/cweTag/tagDetails?id=1&tag_standard=1

ONLINE CAPABILITY CGI GET METHOD SUPPORT <CR_A.4.1.2>

If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):

Y

FINDING CWE IDENTIFIERS USING ONLINE CAPABILITY ELEMENTS <CR_A.4.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CWE identifiers for the individual security elements in the report (required):

Please refer to <CR_A.3.2>

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.4.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 online capability’s repository covers (required):

In the "tab" page of the left navigation bar, the user can query all cwe-id related lists

ONLINE CAPABILITY ELEMENT TO CWE IDENTIFIER MAPPING <CR_A.4.5>

If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CWE identifier(s), otherwise enter N/A (required):

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

The export formats we support are PDF, word, Excel and HTML. Users can easily search specific CWE related text through keyword search. For example, we open the exported excel document and press "Ctrl + F" to search for "CWE", as shown in the following figure "search diagram"

PDF

Excel

Figure

HTML

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 in the form of tables. For example, the document format is PDF. Users can easily find the relevant CWE ID by searching the serial number or keyword.

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

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

please refer to <CR_B.3.1>

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: Joy Bian

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: Joy Bian

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: Joy Bian

Title: Product Manager