Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

IriusRisk

Web Site:

https://www.iriusrisk.com/

Compatible Capability:

IriusRisk

Capability home page:

https://www.iriusrisk.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):

IriusRisk is a SaaS solution for threat modelling available for all from www.iriusrisk.com. Anyone can try it out for free using our Community version: https://community.iriusrisk.com/ui#!login

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

We have a web page where we announce all changes when releasing a new IriusRisk version: https://support.iriusrisk.com/hc/en-us/categories/360001332031-Announcements

In these we announce new versions of our libraries, including CWE.

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

IriusRisk is constantly updating its security libraries, which contains the CWE mappings. Every release we increment the number of mappings, incluing the CWE ones.

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 timing depends on the IriusRisk minus release calendar (roughly three months between each release).

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

You can see IriusRisk's CWE documentation here: https://support.iriusrisk.com/hc/en-us/articles/360021519531-CAPEC-and-CWE

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

You can see IriusRisk's CWE documentation here: https://support.iriusrisk.com/hc/en-us/articles/360021519531-CAPEC-and-CWE

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

You can see IriusRisk's CWE documentation here: https://support.iriusrisk.com/hc/en-us/articles/360021519531-CAPEC-and-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):

You can see IriusRisk's CWE documentation here: https://support.iriusrisk.com/hc/en-us/articles/360021519531-CAPEC-and-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):

N/A

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

N/A

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

N/A

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

N/A

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

N/A

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

N/A

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

N/A

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

N/A

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

IriusRisk automatically generates documents in XLSX, XML and HTML formats with all kinds of information related to the model which shows vulnerabilities and countermeasures showed in the IriusRisk UI. 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):

Libraries and product models in IriusRisk can be exported as XML files in which users can find CWE identifiers when opened with the appropriate application.

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

Libraries and product models in IriusRisk can be exported as XML files in which users can find CWE identifiers when searching for names or descriptions when opened with the appropriate application.

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

There are multiple options to search CWE vulnerabilities:

1. Searchbox in /Products/Risks tab
2. Searchbox in /Products/Risks/Component/Threat "Find and add weakness..." option
3. Searchbox in /Libraries/RisksPatterns tab
4. Searchbox in /Libraries/RisksPatterns/Component/Threat "Find and add weakness..." option

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

When searching for weaknesses by name or description in the previously mentioned searchboxes it will appear their associated CWE identifier as the reference code for that weakness.

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

IriusRisk automatically generates documents in XLSX, XML and HTML formats with all kinds of information related to the model which shows vulnerabilities and countermeasures showed in the IriusRisk UI. 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: Steve Galache

Title: CMO

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: Steve Galache

Title: CMO

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: Steve Galache

Title: CMO