l
l
Support added for Kubernetes versions 1.25 and 1.26
Support added for Kubernetes Persistent Volumes with optional support for Pod
Security Context fsGroup option (fsGroup support is required for using a non-
default container user ID)
l
l
Support added for kubectl command-line tool version 1.24, 1.25, and 1.26. Fortify
recommends the use of the same version of kubectl command-line tool as the
Kubernetes cluster version
Support added for version 3.10 and 3.11 of the Helm command-line tool
Fortify ScanCentral SAST
The following features have been added to Fortify ScanCentral SAST.
Specifying Fortify Static Code Analyzer Options and Properties as -targs and -
sargs Arguments
ScanCentral now supports the options specified in -targsand -sargsthat Fortify
Static Code Analyzer allows, and ignores or blocks those that are not allowed.
Clients now accept rules, filters, and project templates - not only through the
designated ScanCentral options, but also from the scan arguments parameter (-
sargs). Previously, if specified, these options were ignored. For more information,
see Appendix A: Fortify ScanCentral SAST Command-Line Options in the Fortify
ScanCentral SAST Installation, Configuration, and Usage Guide.
New Status Command Option: --block-until
Previously, a ScanCentral client had no way to let you know if an FPR that you
uploaded to Fortify Software Security Center was processed completely. Now, you
can use the --block-until option to block additional actions from being performed
until processing is complete, so that the merged results you later download include
all of the audits, comments, suppressed issues, and history from the previous
scans.
The new --block-untiloption for the STATUS command polls Fortify Software
Security Center for the scan merge status, and then returns the following
information:
l
Job status
l
SSC upload status
l
SSC application version ID
l
SSC application name
l
SSC application version name
l
SSC artifact ID
l
SSC artifact status
OpenText™ Fortify Software (24.4.0)
Page 25 of 33