Releases: sonatype/nexus-iq-fortify-ssc
Releases · sonatype/nexus-iq-fortify-ssc
SonatypeFortifyBundle-5.1.2
Changelog
- Fixed an issue where the expected scan report was not being synchronized if the most recent one was an identical report generated by continuous monitoring
SonatypeFortifyBundle-5.1.1
Changelog
- Fixed issue where sync service did not terminate as expected when the
killProcess
flag was set totrue
- Added support for
fortifyApplicationId
when using thestartScanLoad
endpoint
SonatypeFortifyBundle-5.1.0
Changelog
- Fortify Application ID can now be used to map JSON instead of the application name
- Added support for synchronizing all violation categories, not only security
- Uploads of reports generated by continuous monitoring will be skipped if the data is identical to the previously uploaded report
- Fortify Audit Details are now clickable links for Fortify versions 23.0 and later
- Included license information for the report in the synchronized artifact. This can be configured via the include.license.information property
SonatypeFortifyBundle-5.0.1
- Resolved issue that sometimes caused a Null Pointer Exception during synchronization of violations for custom policies
SonatypeFortifyBundle-5.0.0
Changelog
- Consolidated artifact and suppression upload into a single call
SonatypeFortifyBundle-4.3.1
Changelog
- Memory usage optimizations
SonatypeFortifyBundle-4.3.0
Changelog
- Performance Improvements
- scheduling.job.cron is replaced with scheduling.fixed.rate.minutes
SonatypeFortifyBundle-4.2.13
Changelog
Added a new endpoint for triggering synchronization for a given project on-demand
SonatypeFortifyBundle-4.2.12
Changelog
- CVSS scores when only Sonatype CVSS Score Exists fixed
SonatypeFortifyBundle-4.2.11
Changelog
- CVSS scores being printed in wrong fields bug fixed
- Enhanced Logging