Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

(warning) This is documentation for upcoming version 2.0.

Description / Features

This plugin imports Fortify SSC rules descriptions and reports into SonarQube:

  • Parse extracted rulepacks to have rule descriptions into SQ
  • Import vulnerability issues as SonarQube issues. Supported languages are ABAP, C#, C++, Cobol, Java, JavaScript, Python and VB.
  • Compute the Fortify Security Rating, value between 1 and 5
  • Compute the number of issues marked as critical, high, medium and low priority in Fortify

This plugin is not autonomous

Icon

As stated in the description above, this plugin imports audit reports. This means that the plugin does not trigger Fortify scans.

As a consequence, Fortify scans must have been run before executing this plugin on SonarQube.
The plugin has been developed and tested with Fortify 2.50. Older versions might also work (feel free to tell us on the user mailing list if you managed to make it work in this case).

Here are some screenshots from the plugin:



Installation

  1. Install the plugin through the Update Center or download it into the SONARQUBE_HOME/extensions/plugins directory
  2. Restart the SonarQube server

Usage

Import Fortify rules into SonarQube

SonarQube server loads rule definitions from Fortify rulepacks. Rulepacks are :

  • XML files implemented by end-users to define custom rules.
  • BIN files provided by HP. They are encrypted XML files.

The SonarQube plugin is able to load the XML files, so BIN files must be beforehand manually uncompressed. Paths to the XML files (or to their parent directory) must be set in the property "sonar.fortify.rulepackPaths" of conf/sonar.properties. Value is a comma-separated list of absolute paths to XML files or to directories containing XML files. As a consequence SonarQube server must be restarted each time a rulepack is updated in Fortify.

Example

sonar.fortify.rulepackPaths=/path/to/fortify/rulepacks,/path/to/rulepack.xml

When server is restarted, the Fortify rules are listed in the "Quality Profiles" page.

Uncompress Rulepacks

The following command extracts XML files from BIN files :

java -cp rulepack-uncompress-2.0.jar:/path/to/Fortify/Core/lib/fortify-crypto-1.0.jar org.sonar.fortify.uncompress.CLI /path/to/rulepacks/dir

Note that the parameter is the path to the directory containing BIN files. Related XML files are extracted in the same directory by default. The output directory can be customized by setting a second parameter on the command-line :

java -cp rulepack-uncompress-2.0.jar:/path/to/Fortify/Core/lib/fortify-crypto-1.0.jar org.sonar.fortify.uncompress.CLI /path/to/rulepacks/dir /path/to/output/dir

Note that Fortify rules are only imported in SonarQube when appropriate SonarQube language plugin is installed. Here is the conversion table between Fortify language and SonarQube language:

FortifySonarQube
javajava
abapabap
actionscriptflex
cfmlUnsupported
cppcpp
dotnetcs
configurationxml
contentweb
jspweb
pythonpy
objcUnsupported
phpphp
sqlUnsupported
vbvb

 

Configure and run analysis

The SCA command-line, named "sourceanalyzer", must be executed before SonarQube analyzer. The generated report (FPR or VFDL file) is parsed to convert Fortify vulnerabilities to SonarQube issues. By nature SonarQube issues relate to rules that are activated in Quality profiles. For this reason don't forget to activate the Fortify rules in the selected Quality Profiles. Note that severity of rules are taken from Fortify report so the severity configured in quality profile is ignored.

The path to the Fortify report is set by the property "sonar.fortify.reportPath". Path is absolute or relative to the module base directory. If the property is missing then the plugin is disabled.

Example

  sonar-runner -Dsonar.fortify.reportPath=/path/to/project.fpr

Something like the following should appear in the log:

 

 

  • No labels