Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Kiuwan Software S.L

Web Site:

www.kiuwan.com

Compatible Capability:

Kiuwan Application Security platform

Capability home page:

www.kiuwan.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):

Kiuwan is a SaaS solution readily available for all from www.kiuwan.com. Anyone can sign up for a 15-day free trial. There is also an on-premise version available.

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

Kiuwan includes the Kiuwan and CWE page in its documentation, where it is clearly stated the CWE version used for the latest mapping.

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

As stated in the Kiuwan and CWE documentation page, Kiuwan team does a review and applies the required changes to the CWE mappings before every release (roughly every 3 months) to reflect the latest possible CWE version.

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

Again, all the information regarding the CWE is in the Kiuwan and CWE documentation page. The timing depends on the Kiuwan major release calendar (once a year minimum).

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

In the Kiuwan and CWE documentation page you can see Kiuwan’s policy for compatibility and updates.

In the application itself, the vulnerability report clearly states the mapping with the correspondent CWE with every vulnerability found. In every case the report includes a link to the CWE site with the detailed information.

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

There are 2 places in Kiuwan where users can use CWE identifiers to find security elements:

• Models Management. This is where users define the software models to use when analyzing applications. Here there are over 3,000 rules that detect defects and vulnerabilities, 623 of which are directly related to security vulnerabilities, these are the security elements in Kiuwan’s repository. Among other filtering and search criteria, users can use the CWE identifier to find rules and use them in their models. Models Management documentation page.
• Vulnerabilities report. For every analysis executed in Kiuwan, users have all the details about the vulnerabilities found in the Vulnerabilities report. Here users can easily filter and search the application results by CWE identifier. Since the CWE identifier is explicitly displayed as a column in the results the complete list can be sorted by CWE identifier as well. Vulnerabilities documentation page.

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

Again, there are 2 places in Kiuwan where users can use security elements and their association with CWE identifiers:

• Models Management. This is where users define the software models to use when analyzing applications. Here there are over 3,000 rules that detect defects and vulnerabilities, 623 of which are directly related to security vulnerabilities, these are the security elements in Kiuwan’s repository. Every security element has one or more tags specifying the mapping with one or more CWE identifiers. Models Management documentation page.
• Vulnerabilities report. For every analysis executed in Kiuwan, users have all the details about the vulnerabilities found in the Vulnerabilities report. Here the CWE identifier associated with every security element (vulnerability found)is explicitly displayed as a column in the results. The complete list can be sorted by CWE identifier. Additionally the displayed description of every security element displays the tags associated to it including the ones for the associated CWE identifiers. Vulnerabilities documentation page.

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

The afore mentioned Kiuwan and CWE documentation page contains all the CWE information, and links to other pages mentioning CWE.

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

In this context, tasks in Kiuwan are each and every rule (check) that is executed when analyzing applications and produce defects and vulnerabilities (security elements).

Rules are grouped in software models. Kiuwan’s Model Management allows users to find rules using CWE identifiers to search and select them to include them in the different models. These models are later used to analyze applications applying the rules in them.

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

In the vulnerabilities report, the user can see all the vulnerabilities found in their applications. If a given vulnerability has an associated CWE identifier mapping, the users can see it immediately in the CWE column in the results. Additionally, in the description of the vulnerability they see the associated CWE identifiers as tags.

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

Kiuwan has a rule repository with over 3,000 rules available for the users to build the models they used to analyze applications. To see the list of CWE identifier coverage, the users just have to go to Models Management > Rules Management and filter the list by the CWE tag and only the rules with an associated CWE identifier will be displayed. The list is also available on the Kiuwan 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):

Kiuwan does not provide a CCR document in XML format. However, you can export any filtered list of rules in Rules Management to a CSV file.

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

In this context, tasks in Kiuwan are each and every rule (check) that is executed when analyzing applications and produce defects and vulnerabilities (security elements).

In Kiuwan’s Model Management For every rule you can see the complete list of CWE identifiers mapped associated with it. When searching in the tag field you can see the list of all CWE identifiers the rules in the repository have and use them to search for specific rules.

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

Kiuwan does not support reading a file with identifiers and select corresponding vulnerabilities in one or more action plans, the containers of what we can consider tasks in Kiuwan.

However, in the Models Management, users can provide a list of different CWE identifiers to filter the list of found rules.

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

In this context, tasks in Kiuwan are each and every rule (check) that is executed when analyzing applications and produce defects and vulnerabilities (security elements).

In Kiuwan’s Model Management you can search and filter rules by an individual CWE identifier or by a list of identifiers. The user can then select/deselect each rule with the radio button in the Active column.

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 filtering the list of rules in Kiuwan Models Management, if the provided CWE identifier does not match any rule in the repository, the user sees an empty list with a message explaining that the filter didn’t match any existing rules.

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

Kiuwan is a SaaS, therefore available online. All the answers for the tools questions apply exactly the same for the correspondent questions in this section. Refer to CR_A.2.1

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

Examples:

• http://www.example.com/cgi-bin/db-search.cgi?cweid=XXX
• http://www.example.com/cwe/xxx.html

Kiuwan provides a RESTful API to retrieve information about rules (tasks) used in a model the key for the search is the internal Kiuwan rule identifier.

Example:

GET https://api.kiuwan.com/doc/rule?application={application}&modelId={modelid}&code={rulecode}

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

Kiuwan provides a RESTfull API, it is not strictly implemented with CGI programs. It supports the GET method.

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

Kiuwan is a SaaS, therefore available online. All the answers for the tools questions apply exactly the same for the correspondent questions in this section.

Refer to CR_A.2.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):

Kiuwan is a SaaS, therefore available online. All the answers for the tools questions apply exactly the same for the correspondent questions in this section.

Refer to CR_A.2.3

USING CCR TO PROVIDE CLAIMED CWE IDENTIFIER COVERAGE <CR_A.4.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 online capability’s repository covers (recommended):

Kiuwan is a SaaS, therefore available online. All the answers for the tools questions apply exactly the same for the correspondent questions in this section.

Refer to CR_A.2.4

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

Kiuwan automatically generates documents in PDF and CVS formats with all kinds of information related to the rules in the Model that look for vulnerabilities and the vulnerabilities themselves found in a specific application after analysis. These documents include all the CWE related information and can be easily searched and filtered when opened with the appropriate application.

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

Every Kiuwan vulnerabilities (security elements) list can be exported to CSV files. One of the exported columns is the CWE identifier mapped with the vulnerability. Beside the description text and references column are searchable as well. When opened with spreadsheet software you can filter and search for CWE related text and columns.

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 accompanying file (34163_2017-02-08 14-08-44.0_DefectsTable_rfc_4180.csv) is a direct export of a vulnerabilities list from Kiuwan. The second column shows the CWE identifier/s mapped to each vulnerability.

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

Kiuwan offers full search and find capabilities based on CWE identifiers in the whole rule repository.

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 Kiuwan’s rule repository available to build your analysis models the mapping of every rule with their associate CWE identifiers is directly in the description of the individual security elements (rules).

In the analysis results, every found vulnerability, besides having the CWE identifier in the description of the vulnerability, it has a column with the mapped CWE identifier. Clicking on the identifiers Kiuwan takes you the correspondent CWE page for that identifier.

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

Kiuwan automatically generates documents in PDF and CVS formats with all kinds of information related to the rules in the Model that look for vulnerabilities and the vulnerabilities themselves found in a specific application after analysis. These documents include all the CWE related information and can be easily searched and filtered when opened with the appropriate application.

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: Javier Salado

Title: Director

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: Javier Salado

Title: Director

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: Javier Salado

Title: Director