Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Security Reviewer

Web Site:

https://www.securityreviewer.net

Compatible Capability:

Static Reviewer

Capability home page:

https://securityreviewer.atlassian.net/wiki/spaces/KC/pages/196633/Static+Reviewer+-+Code+Inspection

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

Security Reviewer executes code checks according most relevant Secure Coding Standards for 40+ supported programming languages. It integrates Static Analysis (SAST) and Dynamic analysis (IAST).

It can be installed 100% On Premise in several Host types, even Virtualized, as well as inside Containers, or in Cloud.

Each of Container Images have a Dockerfile, available on our GitHub space, with access reserved to existing customers.

Can fully integrated in your DevOps environment, with the support of most used CI/CD Platforms, SCM, and ITSM solutions or directly inside Programmers IDE (Eclipse, Visual Studio). The IDE plugins are Open Source and free, independent of the number of programmers that are developing.

Using built-in design 1000+ validation rules, during Code Review process highlights violations and even suggest changes that would improve the structure of the system. It creates an abstract representation of the program, based on Modules, Edges and Nodes.

The Rule Engine with its internal multi-thread, optimized state machine is the fastest in the market. It does not need any internal or external DBMS to run, and it is fully extensible via XML. Its unique capability to reconstruct an intended layering, makes it an invaluable tool for discovering the architecture of a vulnerability that has been injected in the source code.

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

Static Reviewer provides a consistent number of CWE 4.4 rules designed for detecting vulnerabilities inside source code. Each rule defines up to 12 variants and up to 50 API on which will applied, and has its own CWE™ Identifier and Description, with related MITRE™ web site link, on which you can do a Search:

You can Export the rules list in Excel CSV format with CWE™ details:

You can execute the Static Analysis with CWE™ and CWE™ SANS Top 25 ruleset:

After Static Analysis Completion, even you chose a different RuleSet, each vulnerability detected has always its own CWE™ ID with the related web link:

In the Static Analysis Reports, each rule's violation shows the related clickable CWE™ ID:

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

For each new major release, we schedule an update to our CWE content to keep it in sync with the current CWE requirements. Every month are released maintenance updates of the product. At the same time, we will continue to enhance our support for the CWE requirements.

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 support updates will be reflected in the "Release Notes" section in the Product documentation and in our website at https://securityreviewer.atlassian.net/wiki/spaces/KC/pages/29524029/CWE.

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

https://securityreviewer.atlassian.net/wiki/spaces/KC/pages/29524029/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):

https://securityreviewer.atlassian.net/wiki/spaces/KC/pages/29524029/CWE#CWE%E2%84%A2-Results

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

https://securityreviewer.atlassian.net/wiki/spaces/KC/pages/29524029/CWE#CWE%E2%84%A2-Results

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

https://securityreviewer.atlassian.net/wiki/spaces/KC/pages/29524029/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):

Each vulnerability detected has always its own CWE™ ID with the related web link to the CWE webpage

You can list and export in Excel CSV all CWEs found during the Static Analysis:

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 Static Analysis Reports, each rule's violation shows the related clickable 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):

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

In the "Vulnerabilities" panel, vulnerability listing can be sorted and filtered by "CWE-ID" and "Category".

Customers can filter vulnerabilities selecting in the main panel the vulnerabilities groped by Category

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

Every vulnerability is associated with a "Category" and a “CWE-ID” directly linked to the CWE website

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

Vulnerabilities can be exported in PDF or CSV format. The exported file includes the CWE-ID

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: Francesco Mariani

Title: Chief Product Officer

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: Francesco Mariani

Title: Chief Product Officer

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: Francesco Mariani

Title: Chief Product Officer