...
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
- Import vulnerability issues as Sonar violationsSonarQubeissues. Supported languages are ABAP, C#, C++, Cobol, Java, JavaScript, Python and VB.
| Info | ||
|---|---|---|
| ||
As said in the description above, this plugin imports audit reports available in Fortify SSC Server. This means that the plugin:
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). |
| Note | ||
|---|---|---|
| ||
The Fortify plugin currently does not support multi-module 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 the plugin:
Installation
- Install the Fortify plugin through the Update Center or download it into the SONAR SONARQUBE_HOME/extensions/plugins directory
- Restart the Sonar SonarQube server
Usage
- Configure the connection to the Fortify SSC Server in Configuration Settings > Configuration > General Settings > Fortify:
- Server URL
- Login/password. Token-based authentication is not supported yet.
- Activate some Fortify rules in the Quality Profile
- Configure the project to be analyzed:
- By default project name and version must match the name and version defined in Fortify. They can be changed in Project Settings.
- Enable audit import on the projects that have been scanned by Fortify: set
sonar.fortify.enabletotruein Project Settings.
Inspect projectRun a SonarQube analysis. The following logs should appear:
Code Block [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
Note title Security note for SonarQube 3.4+ For the
*.securedproperties to be read during the project analysis, it is necessary to set thesonar.loginandsonar.passwordproperties 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
| JIRA Issues | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
