Skip to content

Fortify SSC parser plugin to import Debricked SCA results for unified AppSec posture management

License

Notifications You must be signed in to change notification settings

fortify/fortify-ssc-parser-debricked-cyclonedx

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Fortify SSC Parser Plugin for Debricked results

Fortify Application Security provides your team with solutions to empower DevSecOps practices, enable cloud transformation, and secure your software supply chain. As the sole Code Security solution with over two decades of expertise and acknowledged as a market leader by all major analysts, Fortify delivers the most adaptable, precise, and scalable AppSec platform available, supporting the breadth of tech you use and integrated into your preferred toolchain. We firmly believe that your great code demands great security, and with Fortify, go beyond 'check the box' security to achieve that.

This Fortify SSC parser plugin allows for importing CycloneDX SBOM files generated by Debricked into SSC. Two versions of this plugin are available:

  • fortify-ssc-parser-debricked-cyclonedx.jar
    • Parser plugin compatible with all recent SSC versions
    • Debricked issues are displayed on the SSC Audit page only
  • fortify-ssc-22.2+-parser-debricked-cyclonedx.jar
    • Parser plugin compatible with SSC 22.2 and above
    • Debricked issues are displayed on both SSC Audit page and SSC Open Source page

Resources

Support

For general assistance, please join the Fortify Community to get tips and tricks from other users and the OpenText team.

OpenText customers can contact our world-class support team for questions, enhancement requests and bug reports. You can also raise questions and issues through your OpenText Fortify representative like Customer Success Manager or Technical Account Manager if applicable.

You may also consider raising questions or issues through the GitHub Issues page (if available for this repository), providing public visibility and allowing anyone (including all contributors) to review and comment on your question or issue. Note that this requires a GitHub account, and given public visibility, you should refrain from posting any confidential data through this channel.


This document was auto-generated from README.template.md; do not edit by hand