This plugin imports Fortify SSC reports into SonarSonarQube:
- 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
|title||This plugin is not neither autonomous nor server-less|
As said 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 Sonar.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).
|title||Multi-module projects are currently supported only for Java projetcts|
The Fortify plugin currently does not support multi-module projects for languages other than Java. You can watch and vote for the following JIRA ticket concerning this issue: SONARPLUGINS-2452
Here are some screenshots of from the plugin:
- Install the Fortify plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
- Restart the Sonar server
|Include - Plugin Installation|
|Include - Plugin Installation|
- Configure the connection to the Fortify SSC Server in Configuration Settings > General Settings > Fortify:
- Server URL
- Login/password. Token-based authentication is not supported yet.
- Activate some Fortify rules rules from the "Fortify" rule repositorys in the Quality Profile
- Configure the project to be analyzed:
Inspect project. The following logs should appear
- By default project name and version must match the name and version defined in Fortify. They can be changed in Project Settings. By default, the Fortify plugin will try to match the value of
sonar.projectVersion with the name and version of a project in your Fortify server. If they don't match, you can use
sonar.fortify.projectVersion to configure the correct values.
- Enable audit import on the projects that have been you want to be scanned by Fortify: set the
sonar.fortify.enable property to
true in Project Settings.
- Image Added
Run a SonarQube analysis. Something like the following should appear in the log:
Image RemovedImage Removed
[INFO] [14:03:32.720] Fortify SSC Project: <Fortify project name>, version: <Fortify project version>
[INFO] [14:03:35.643] Sensor Fortify Audit Context...
[INFO] [14:03:35.643] Sensor Fortify Audit Context done: 0 ms
[INFO] [14:03:35.643] Sensor Fortify Performance Indicators...
[INFO] [14:03:36.701] Sensor Fortify Performance Indicators done: 1058 ms
[INFO] [14:03:36.701] Sensor Fortify Issues...
[INFO] [14:04:35.131] Loading 171 Fortify issues
[INFO] [14:04:35.149] Sensor Fortify Issues done: 58448 ms
|title||Security note for SonarQube 3.4.0 to 3.6.3 included|
*.secured properties to be read during the project analysis, it is necessary to set the
sonar.password properties to the credentials of a user that is:
- System administrator
- And project administrator on the project that is being analyzed
sonar-runner -Dsonar.login=admin -Dsonar.password=admin
|title||Release 1.Version 1.1|