After installing latest Windows patch, DISA STIG 4.10 Report No Longer Visible When running the Static Code Analyzer 19.2.2 and after installing the latest Windows patch version 19.2.2.0006. If you can no longer see DISA STIG 4.10 as an option when trying to create a BIRT report then to resolve this issue, copy the line: […]
AWB 19.2 fails to launch on MacOS Mojave Launching AWB 192.2 on MacOS Mojave results in the dialog box: "An error has occurred.See the log file/Users/<username>/.fortify/AWB-19.2.0/configuration411/1584723467252.log" Clicking "Ok" on, the dialog box closes. The root cause was related to an incomplete installation. As it was found to be missing some bundles, after a reinstall of […]
The following features have been added to Fortify Static Code Analyzer. .NET Updates Support added for .NET Core 2.2, 3.0, and 3.1 Support added for C# 8 Support added for VB.NET 16.0 (2019) Support added for MSBuild 16.4 Support added for .NET Framework version 4.8 Support added for ASP.NET 4.8 macOS Update Support added for macOS 10.15 […]
The following features have been added to Fortify Software Security Center. SQL Server Change You no longer need to download the JDBC JAR file or ensure Tomcat Server classpath includes its location when using SQL Server as your database. GUI Changes Applications View Now displays application versions in an expandable list beneath the application name. Scans View A Copy […]
If you are having trouble scanning Java project with Advanced Scan in Auditworkbench and getting an error that there are No valid input files specified. To avoid that error add the following to the advance scanner: “-source”\”1.8″\”-Dcom.fortify.sca.fileextensions.class=BYTECODE”/”-Dcom.fortify.sca.fileextensions.jar=ARCHIVE” and name every single folder with *.class and *.jar.