Using results from Fortify Static Code Analyzer

This video goes deep into the various ways to use results from Fortify Static Code Analyzer to help you build secure software faster. Common ways to view fortify on premise static scan results:
• Within the output from Source Analyzer (or ScanCentral) [4:15]
• Within a Supported IDE [7:05]
• Within Audit Workbench [11:53]
• Within Fortify SSC [20:15]
• Via output From CI Pipeline [25:46]
• Using FPRUtility [28:40]
• Via Fortify generated Reports [30:52]

These are some of the ways to perform scans using Fortify Static Code Analyzer:
1. From the CLI (command-line interface) or Script that use Source Analyzer (this video)
2. From the CLI or Script that use ScanCentral
3. Within a supported IDE (integrated development environment)
4. As part of a CI Pipeline

Two earlier videos looked at the ways to perform static scans in Fortify Static Code Analyzer.

Fortify Results include:
• List of issues found and counts
• Files scanned
• Functions/Methods scanned
• Statistics about the scanned code
• Statistics about the scan environment

Fortify Static Code Analyzer pinpoints the root cause of security vulnerabilities in the source code, prioritizes the most serious issues, and provides detailed guidance on how to fix them so developers can resolve issues in less time with centralized software security management.

- Connect with peers and share your knowledge
- Find solutions and answers to your technical questions
- Stay informed on new releases and product enhancements
- Access downloads, demos, videos and support tips

[harithaguda]

I have executed scan for a directory and uploaded fpr in SSC where I could see privacy violation for a file. Later I have executed scan for that particular file and opened fpr in Auditworkbench, there this violation type is not listed. Can you please guide what am I missing here.

[pavankumar.]

How to setup fortify in ec2 Linux instance