Skip to end of metadata
Go to start of metadata

Description / Features

This plugin imports Fortify SSC reports into SonarQube:

  • Import the Fortify Security Rating, value between 1 and 5
  • Import the number of issues marked as critical, high, medium and low priority in Fortify
  • Link to the Fortify SSC web report
  • Import vulnerability issues as SonarQube issues. Supported languages are ABAP, C#, C++, Cobol, Java, JavaScript, Python and VB.

This plugin is neither autonomous nor server-less

Icon

As stated in the description above, this plugin imports audit reports available in Fortify SSC Server. This means that the plugin:

  • does not trigger Fortify scans
  • needs a connection to the Fortify server to retrieve the results
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).

Multi-module projects are currently supported only for Java projetcts

Icon

The Fortify plugin currently does not support multi-module projects for languages other than Java. You can watch and vote for the JIRA ticket concerning this issue: SONARPLUGINS-2452

 

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

  1. Configure the connection to the Fortify SSC Server in Settings > General Settings > Fortify:
    • Server URL
    • Login/password. Token-based authentication is not supported yet.
       
  2. Activate some rules from the "Fortify" rule repositorys in the Quality Profile
     
  3. Configure the project to be analyzed:
    •  By default, the Fortify plugin will try to match the value of sonar.projectName and sonar.projectVersion with the name and version of a project in your Fortify server. If they don't match, you can use sonar.fortify.projectName and sonar.fortify.projectVersion to configure the correct values.
    • Enable audit import on the projects you want to be scanned by Fortify: set the sonar.fortify.enable property to true.
       
  4. Run a SonarQube analysis. Something like the following should appear in the log:

    Security note for SonarQube 3.4.0 to 3.6.3 included

    Icon

    For the *.secured properties to be read during the project analysis, it is necessary to set the sonar.login and sonar.password properties to the credentials of a user that is:

    • System administrator
    • And project administrator on the project that is being analyzed
    Example:
    sonar-runner -Dsonar.login=admin -Dsonar.password=admin

Change Log

Loading

Version 1.1 (${entries.size()} issues)

Type Key Summary Priority

 

Loading

Version 1.0 (${entries.size()} issues)

Type Key Summary Priority

  • No labels