Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Sparrow Co., Ltd.

Web Site:

http://www.sparrowfasoo.com

Compatible Capability:

SPARROW

Capability home page:

http://www.sparrowfasoo.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):

SPARROW is a licensed software, we can send an evaluation copy on the request. SPARROW is operated on command windows, GUI client, or Eclipse plugin. For a quick review on SPARROW, you can access SPARROW Demo Page.

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

The CWE version appears on the CWE Mapping page of the SPARROW online manual.

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 have a plan on updating the CWE mapping when testing the product before releasing the product. The engineer in charge of checker references will investigate the CWE webpage and update the modifications on the product.

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

The CWE version used in SPARROW will be updated quarterly, which conforms with the release period of our product.

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

The SPARROW online manual describes the explanation on CWE and CWE compatibility.

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

Every page of SPARROW on which CWE appears describes CWE through the SPARROW online manual.

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

See the answer to <CR_5.2>.

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

CWE mapping represents the mapping between CWE-ID and SPARROW checker name.

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

SPARROW supports filtering and searching of CWE identifiers on alarm review pages. The process is like the following:

1. You can see the list of supported CWE-ID by checking CWE on Checkers box.
2. You may choose each CWE element or groups of CWE-ID ranges.
3. You may directly search CWE-ID by typing the CWE-ID which you want.
4. The CWE-ID column can be added on the alarm list-up page.
5. The corresponding CWE-IDs are represented on the CWE-ID column for each alarm.
6. The "Defect Report" page is shown if you click a defect alarm. If you click the "More…" link, then detailed description on the selected defect will be shown.
7. Clicking a CWE-ID brings you to the corresponding CWE-ID web page.

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

The "Analysis Summary Report" page shows the number of total violated CWE IDs and the distribution on detected CWE-IDs. Clicking each bar on the graph brings you to the defect list page filtered by the corresponding CWE-ID.

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

The "Checker Group Design" page shows the whole list of CWE-IDs supported by SPARROW. The "Checker Ref." box supports searching and filtering by CWE-ID. Description frame shows the CWE-ID link. The whole list of supported CWE-IDs can be found on the SPARROW online manual.

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 have no plan 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):

See the answers to <CR_A.2.1> and <CR_A.2.3>.

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

See the answer 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):

See the answer 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):

See the answer to <CR_A.2.3>. Only supported CWE-IDs are represented.

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

SPARROW online manual shows the whole list of supported CWE-IDs.

• Searching supported CWE-IDs.
• Clicking a checker shows the full name of CWE-ID and detailed explanation on the corresponding checker.
• Clicking a CWE-ID brings you to the corresponding CWE web page.

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

See the answer to <CR_B.3.1>.

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

See the answer to <CR_B.3.1>.

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

See the answers to <CR_A.2.1> and <CR_A.2.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):

See the answers to <CR_A.2.1> and <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):

See the answer 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: Sungjin Kim

Title: Senior Engineer

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 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: Sungjin Kim

Title: Senior Engineer

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 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: Sungjin Kim

Title: Senior Engineer