Micro FocusFortify SoftwareSoftware Version: 20.1.0
System Requirements
Document Release Date: Revision 2: June 19, 2020
Software Release Date: May 2020
Legal NoticesMicro FocusThe Lawn22-30 Old Bath RoadNewbury, Berkshire RG14 1QNUK
https://www.microfocus.com
WarrantyThe only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth inthe express warranty statements accompanying such products and services. Nothing herein should be construed asconstituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions containedherein. The information contained herein is subject to change without notice.
Restricted Rights LegendConfidential computer software. Except as specifically indicated otherwise, a valid license from Micro Focus is required forpossession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer SoftwareDocumentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standardcommercial license.
Copyright Notice© Copyright 2001 - 2020 Micro Focus or one of its affiliates
Trademark NoticesAll trademarks, service marks, product names, and logos included in this document are the property of their respectiveowners.
Documentation UpdatesThe title page of this document contains the following identifying information:
l Software Version number
l Document Release Date, which changes each time the document is updated
l Software Release Date, which indicates the release date of this version of the software
This document was produced on June 19, 2020. To check for recent updates or to verify that you are using the most recentedition of a document, go to:
https://www.microfocus.com/support-and-services/documentation
System Requirements
Micro Focus Fortify Software (20.1.0) Page 2 of 50
Contents
Preface 6
Contacting Micro Focus Fortify Customer Support 6
For More Information 6
About the Documentation Set 6
Change Log 7
Introduction 8
Software Delivery 8
Software Licenses 8
Fortify Static Code Analyzer Requirements 8
Hardware Requirements 9
Software Requirements 9
Platforms and Architectures 9
Supported Languages 10
Supported Build Tools 12
Supported Compilers 13
Secure Code Plugins 14
Single Sign-On (SSO) 15
Service Integrations for Fortify Static Code Analyzer Tools 15
Fortify Software Security Content 16
Fortify Software Security Center Server Requirements 16
Hardware Requirements 16
Database Hardware Requirements 16
Database Performance Metrics for Minimum and Recommended HardwareRequirements 17
Platforms and Architectures 17
Application Servers 18
Fortify Software Security Center Database 18
Deploying Fortify Software Security Center to a Kubernetes Cluster (Optional DeploymentStrategy) 19
Kubernetes: Versions 1.14–1.17 19
Locally-Installed Tools Required 19
Additional Requirements 20
Browsers 20
Authentication Systems 21
System Requirements
Micro Focus Fortify Software (20.1.0) Page 3 of 50
Single Sign-On (SSO) 21
BIRT Reporting 21
Service Integrations for Fortify Software Security Center 22
Fortify ScanCentral Requirements 22
Application Servers 22
ScanCentral Controller Hardware Requirements 22
ScanCentral Controller Platforms and Architectures 23
ScanCentral Client and Sensor Hardware Requirements 23
Supported Languages and Build Tools for ScanCentral Sensor Project Translation 24
Supported Languages 24
Supported Build Tools 25
Fortify WebInspect Agent Requirements 25
Platforms and Architectures 25
Java Runtime Environments 25
Java Application Servers 26
.NET Frameworks 26
IIS for Windows Server 26
Fortify WebInspect Requirements 26
Running as Administrator 26
Hardware Requirements 27
Software Requirements 27
Support for Postman 28
Notes on SQL Server Editions 28
WebInspect on Docker 29
Ports and Protocols 29
Required Connections 29
Optional Connections 30
Connections for Tools 32
Fortify WebInspect Agent 32
WebInspect Software Development Kit (SDK) 32
Software Integrations for Fortify WebInspect 33
Fortify WebInspect Enterprise Requirements 33
Installation and Upgrade Requirements 33
Integrations for Fortify WebInspect Enterprise 34
Fortify WebInspect Enterprise Database 34
Hardware Requirements 34
Software Requirements 35
Administrative Console Requirements 35
System Requirements
Micro Focus Fortify Software (20.1.0) Page 4 of 50
Hardware Requirements 36
Software Requirements 36
Ports and Protocols 36
Required Connections 37
Optional Connections 38
Connections for Tools 39
Fortify WebInspect Enterprise Sensor 40
Fortify WebInspect Enterprise Notes and Limitations 40
Fortify License and Infrastructure Manager Requirements 40
Hardware Requirements 40
Software Requirements 41
Version Compatibility Matrix 42
Fortify Software Component Compatibility 42
FPR File Compatibility 42
Virtual Machine Support 43
Technologies and Features no Longer Supported in this Release 43
Technologies and Features to Lose Support in the Next Release 44
Acquiring Fortify Software 45
About Verifying Software Downloads 48
Preparing Your System for Digital Signature Verification 48
Verifying Software Downloads 49
Assistive Technologies (Section 508) 49
Send Documentation Feedback 50
System Requirements
Micro Focus Fortify Software (20.1.0) Page 5 of 50
Preface
Contacting Micro Focus Fortify Customer Support
You can contact Micro Focus Fortify Customer Support, manage your Support cases, acquire licenses,and manage your account on the following website:
https://softwaresupport.softwaregrp.com
For More Information
For more information about Fortify software products:https://software.microfocus.com/solutions/application-security
About the Documentation Set
The Fortify Software documentation set contains installation, user, and deployment guides for allFortify Software products and components. In addition, you will find technical notes and release notesthat describe new features, known issues, and last-minute updates. You can access the latest versions ofthese documents from the following Micro Focus Product Documentation website:
https://www.microfocus.com/support-and-services/documentation
System Requirements
Micro Focus Fortify Software (20.1.0) Page 6 of 50
Change LogThe following table lists revisions made to this document.
Document Revision Changes
Revision 2:June 19, 2020
Updated:
l "Supported Build Tools" on page 12 and "Supported Compilers" onpage 13 - New supported versions for xcodebuild, and swiftc that areavailable with Micro Focus Fortify Static Code Analyzer version 20.1.1
Revision 1:June 1, 2020
Updated:
l "Supported Build Tools" on page 12 and "Supported Compilers" onpage 13 - New supported versions for xcodebuild, swiftc, and Clang thatare available with Micro Focus Fortify Static Code Analyzer version20.1.1
l "Software Requirements" on page 35 - Updated the supported IISversions and recommended browsers for WebInspect Enterprise server
System Requirements
Micro Focus Fortify Software (20.1.0) Page 7 of 50
IntroductionThis document provides the details about the environments and products that Micro Focus supportsfor this version of Micro Focus Fortify Software, which includes:
l Micro Focus Fortify Static Code Analyzer and Fortify Static Code Analyzer Tools (Micro FocusFortify Audit Workbench and Secure Code Plugins)
l Micro Focus Fortify Software Security Center Server
l Micro Focus Fortify ScanCentral
l Micro Focus Fortify WebInspect Agent
l Micro Focus Fortify WebInspect
l Micro Focus Fortify WebInspect Enterprise
l Micro Focus Fortify License and Infrastructure Manager
Software Delivery
Micro Focus Fortify Software is delivered only electronically. It is not available on disc. See "AcquiringFortify Software" on page 45 for more information.
Software Licenses
Micro Focus Fortify Software products require a license.
For Micro Focus Fortify Software Security Center, Micro Focus Fortify Static Code Analyzer, MicroFocus Fortify Audit Workbench, Micro Focus Fortify Secure Code Plugins, Micro Focus FortifyScanCentral, and Micro Focus Fortify WebInspect Agent, you must download the Fortify licenses foryour purchases from either the Fortify Customer Portal (https://support.fortify.com) or Micro FocusFortify Customer Support (https://softwaresupport.softwaregrp.com). To access either location, usethe credentials that Micro Focus Fortify Customer Support has provided.
To download the Fortify license from the Fortify Customer Portal:
1. Log onto the Fortify Customer Portal.
2. Click Download Licenses, and then click the link for the license you want to use.
For Micro Focus Fortify WebInspect and Micro Focus Fortify WebInspect Enterprise, you will receive anemail with instructions for how to activate your product.
Fortify Static Code Analyzer RequirementsThis section describes the system requirements for Micro Focus Fortify Static Code Analyzer, and theFortify Static Code Analyzer Tools (including the Secure Code Plugins).
Micro Focus Fortify Software (20.1.0) Page 8 of 50
Hardware Requirements
Fortify recommends that you install Micro Focus Fortify Static Code Analyzer on a high-end processorwith at least 16 GB of RAM. If you plan to scan dynamic languages such as JavaScript, TypeScript,Python, PHP, or Ruby, Fortify recommends that you have 32 GB of RAM. If your software is complex,you might require more RAM. See the content about improving performance in the Micro Focus FortifyStatic Code Analyzer User Guide for more information.
Increasing the number of processor cores and increasing memory both result in faster processing.
Software Requirements
Micro Focus Fortify Static Code Analyzer requires Java 8. The Fortify SCA and Applications installerinstalls OpenJDK/JRE 1.8.0_181.
Translating .NET and Visual Studio C/C++ projects requires the Windows operating system and the.NET Framework version 4.7.2 or later.
Platforms and Architectures
Micro Focus Fortify Static Code Analyzer supports the platforms and architectures listed in thefollowing table.
Operating System Platforms
Windows Windows 8.1, 10
Windows Server 2012 R2
Windows Server 2016
Windows Server 2019
Linux Red Hat Enterprise Linux 6 update 5 and later
Red Hat Enterprise Linux 7.x
SUSE Linux Enterprise Server 12
macOS 10.14, 10.15
System Requirements
Micro Focus Fortify Software (20.1.0) Page 9 of 50
Fortify Static Code Analyzer Tools (including Secure Code Plugins) support the platforms andarchitectures listed in the following table.
Operating System Platforms
Windows 8.1, 10
Linux Red Hat Enterprise Linux 6 update 5 and later
Red Hat Enterprise Linux 7.x
SUSE Linux Enterprise Server 12
macOS 10.14, 10.15
Supported Languages
Micro Focus Fortify Static Code Analyzer supports the programming languages listed in the followingtable.
Language Versions
.NET Framework 2.0–4.8
.NET Core 2.0–3.1
ABAP/BSP 6
Note: Fortify ABAP Extractor is supported on a system running SAPrelease 7.02, SP level 0006.
ActionScript 3.0
Angular 2,4,5,6,7
Apex 36
ASP.NET 2.0–4.8
C# 5, 6, 7, 8
C/C++ See "Supported Compilers" on page 13
Classic ASP (with VBScript)
2.0, 3.0
System Requirements
Micro Focus Fortify Software (20.1.0) Page 10 of 50
Language Versions
COBOL IBM Enterprise COBOL for z/OS 3.4.1 with CICS, IMS, DB2, and IBM MQ
ColdFusion 8, 9, 10
Go 1.12, 1.13
Note: Scanning Go code is supported on Windows and Linux.
HTML 5 and earlier
Java (including Android)
5, 6, 7, 8, 9, 10, 11, 12, 13
JavaScript ECMAScript 2015, 2016, 2017, 2018
JSP 1.2, 2.1
Kotlin 1.3.50 (Technical Preview)
MXML (Flex) 4
Objective-C/C++ See "Supported Compilers" on page 13
PHP 5.3, 5.4, 5.5, 5.6, 7.0, 7.1
PL/SQL 8.1.6
Python 2.6, 2.7, 3.x (3.7 and earlier)
Ruby 1.9.3
Scala 2.11, 2.12, 2.13
Swift 5
See "Supported Compilers" on page 13 for supported swiftc versions.
T-SQL SQL Server 2005, 2008, 2012
TypeScript 2.8, 3.0, 3.1, 3.2
VB.NET 11, 14, 15.x, 16.0
VBScript 2.0, 5.0
Visual Basic 6.0
System Requirements
Micro Focus Fortify Software (20.1.0) Page 11 of 50
Language Versions
XML 1.0
Supported Build Tools
Micro Focus Fortify Static Code Analyzer supports the build tools listed in the following table.
Build Tool Versions Notes
Ant 1.10.7 and earlier
Bamboo (see the AtlassianMarketplace for supportedversions)
The Fortify App for Bamboo is available from theAtlassian Marketplace.
Gradle 2.13, 4.x (4.10.3 andearlier)
The Fortify Static Code Analyzer Gradle build integrationsupports the following language/platform combinations:
l Java/Windows, Linux, and macOS
l Kotlin/Windows and Linux
l C/Linux
l C++/Linux
Jenkins (see the Jenkins PluginIndex for supportedversions)
The Fortify Jenkins plugin is available from the JenkinsPlugins Index at https://plugins.jenkins.io/fortify.
Maven 3.0.5, 3.5.x, 3.6.x
MSBuild 4.x, 12.0, 14.0, 15.x, 16.4
Xcodebuild 11, 11.1, 11.2.1, 11.3,11.3.1, 11.4.1, 11.5
Note: Xcodebuild version 11.4.1 and 11.5 support isavailable with Fortify Static Code Analyzer version20.1.1.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 12 of 50
Supported Compilers
Micro Focus Fortify Static Code Analyzer supports the compilers listed in the following table.
Compiler Versions Platform
gcc GNU gcc 4.9, 5.x Windows,Linux, macOS
g++ GNU g++ 4.9, 5.x Windows,Linux, macOS
OpenJDKjavac
9, 10, 11, 12, 13 Windows,Linux, macOS
Oracle javac 7, 8, 9 Windows,Linux, macOS
cl 2015, 2017, 2019 Windows
Intel C++Compiler
icc 8.0 Linux
Clang 11.0.0, 11.0.3
Note: Clang version 11.0.3 support is available with FortifyStatic Code Analyzer version 20.1.1.
macOS
Swiftc 5.1, 5.1.2, 5.1.3, 5.2.2, 5.2.4
Note: Swiftc version 5.2.2 and 5.2.4 support is available withFortify Static Code Analyzer version 20.1.1.
macOS
System Requirements
Micro Focus Fortify Software (20.1.0) Page 13 of 50
Secure Code Plugins
The following table lists the supported integrated development environments (IDE) for the Micro FocusFortify Secure Code Plugins.
Plugin /Extension IDE and Version Notes
Fortify EclipsePlugins(Complete andRemediation)
Eclipse 2018-12 (4.10), 2019-x
Fortify AnalysisPlugin
Android Studio 3.3, 3.4, 3.5
IntelliJ IDEA 2019.x
FortifyRemediationPlugin
Android Studio 3.3, 3.4, 3.5
IntelliJ IDEA 2019.x
PyCharm 2019.x
WebStorm 2019.x
SecurityAssistantExtension forVisual Studio
(see the Visual Studio Marketplace forsupported versions)
Security Assistant Extension for VisualStudio is available from the Visual StudioMarketplace.
SecurityAssistant Pluginfor Eclipse
Eclipse 2018.x, 2019.x
Fortify VisualStudioExtension
Visual Studio 2015 Community,Professional, and Enterprise
Visual Studio 2017 Community,Professional, and Enterprise
Visual Studio 2019 Community,Professional, and Enterprise
Note: The Fortify Visual StudioExtension is not compatible withVisual Studio Express.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 14 of 50
Single Sign-On (SSO)
The Eclipse Complete plugin and the Visual Studio extension support the following SSO methods toconnect with Fortify Software Security Center:
l SPNEGO/Kerberos SSO
l X.509 SSO
Service Integrations for Fortify Static Code Analyzer Tools
The following table lists the supported service integrations for Micro Focus Fortify Audit Workbenchand the Fortify Secure Code Plugins.
Service Versions Supported Tools
Bugzilla 5.0.x Audit Workbench, Eclipse Plugin, VisualStudio Extension
Micro Focus Application LifecycleManagement (ALM)/Quality Center Enterprise (QC)
12.50 Audit Workbench, Eclipse Plugin
Team Foundation Server (TFS) 2015 Audit Workbench, Eclipse Plugin
2017 Audit Workbench, Eclipse Plugin,Visual Studio Extension
Azure DevOps Server 2019 Audit Workbench, Eclipse Plugin, VisualStudio Extension
Azure DevOps (formerly VSTS)
Note: Only basic user passwordauthentication is supported.
n/a Audit Workbench, Eclipse Plugin
Jira 7.11 andlater, 8.x
Audit Workbench, Eclipse Plugin
Fortify Software Security Center BugTracker
20.1.0 Audit Workbench, Eclipse Plugin,Visual Studio Extension
System Requirements
Micro Focus Fortify Software (20.1.0) Page 15 of 50
Fortify Software Security Content
Micro Focus Fortify Secure Coding Rulepacks are backward compatible with all supported FortifySoftware versions. This ensures that Rulepacks updates do not break any working Fortify Softwareinstallation.
Fortify Software Security Center ServerRequirementsThis section describes the system requirements for the Micro Focus Fortify Software SecurityCenter server.
Hardware Requirements
Micro Focus Fortify Software Security Center requires the hardware specifications listed in the followingtable.
Component Minimum Recommended
Application server Java heap size 4 GB 24 GB
Database server Processor Quad-core Eight-core
RAM 8 GB 64 GB
Database Hardware Requirements
Fortify recommends an eight-core processor with 64 GB of RAM for the Fortify Software SecurityCenter database. Using less than this recommendation can impact Fortify Software Security Centerperformance.
Use the following formula to estimate the size (in GB) of the Fortify Software Security Center databasedisk space:
((<Total_Issues>*30 KB) + <Total_Artifacts>) ÷ 1,000,000
where:
l <Total_Issues> is the total number of issues in the system
l <Total_Artifacts> is the total size in KB of all uploaded artifacts and scan results
Note: This equation produces only a rough estimate for database disk space allocation. Do not usethis formula to estimate disk space requirements for long-term projects. Disk requirements forFortify Software Security Center databases increases in proportion to the number of projects,
System Requirements
Micro Focus Fortify Software (20.1.0) Page 16 of 50
scans, and issues in the system.
Database Performance Metrics for Minimum and Recommended HardwareRequirements
The following table shows performance metrics (number of issues discovered per hour) for FortifySoftware Security Center configured with the minimum and the recommended hardware requirements.
DatabaseIssues per HourMinimum Configuration
Issues per HourRecommended Configuration
MySQL 362,514 2,589,385
Oracle 231,392 3,020,950
SQL Server 725,028 3,625,140
Platforms and Architectures
Micro Focus Fortify Software Security Center supports the platforms and architectures listed in thefollowing table.
Operating System Versions
Windows Server 2012 R2
Server 2016
Server 2019
Linux Red Hat Enterprise Linux 6 update 5 and later
Red Hat Enterprise Linux 7.x
SUSE Linux Enterprise Server 12
Note: Although Fortify Software Security Center has not been tested on all Linux variants, mostdistributions are not known to have issues.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 17 of 50
Application Servers
Micro Focus Fortify Software Security Center supports Apache Tomcat version 9.x for the followingJDK versions:
l Red Hat OpenJDK 8
l SUSE OpenJDK 8
l Oracle JDK 8
l Zulu OpenJDK 8 from Azul (installation of fontconfig, DejaVu Sans font and DejaVu Serif font isrequired on the server)
Fortify only supports the deployment of a single Fortify Software Security Center instance.Furthermore, that instance must not be behind a load balancer.
Fortify Software Security Center Database
Micro Focus Fortify Software Security Center requires that all database schema collations arecase-sensitive.
Fortify Software Security Center supports the databases listed in the following table.
Database VersionsCollation /Character Set Driver
MySQL 5.7(CommunityEdition)
8.0(CommunityEdition)
utf8_bin, latin1_general_cs
5.1.47 or later
Driver class:
com.mysql.jdbc.driver
JAR file:
mysql-connector-java-<version>-bin.jar
Oracle 12cRelease 2
19c
AL32UTF8 for alllanguages
WE8MSWIN1252for US English
Oracle Database 12c Release 2 (12.2.x) JDBC Driver
Driver class:
oracle.jdbc.OracleDriver
JAR file:
ojdbc8.jar (for Java 8)
System Requirements
Micro Focus Fortify Software (20.1.0) Page 18 of 50
Database VersionsCollation /Character Set Driver
SQL Server 2016
2017
2019
Make sure to usethe case-sensitive(CS) option whenchoosing yourcollation method.For example:
SQL_Latin1_General_CP1_CS_AS
The driver is included in the Fortify SoftwareSecurity Center WAR file.
Microsoft JDBC Driver 8.2 for SQL Server
Driver class:
com.microsoft.sqlserver.jdbc.SQLServerDriver
Note: Fortify does not support the direct conversion from one database server type to another,such as converting from MySQL to Oracle. To do this, you must use the Server API to move datafrom your current Fortify Software Security Center instance to a new Fortify Software SecurityCenter instance that uses the database server type you want to use going forward. Micro FocusProfessional Services can assist you with this process.
Deploying Fortify Software Security Center to a KubernetesCluster (Optional Deployment Strategy)
If you plan to deploy Micro Focus Fortify Software Security Center on a Kubernetes cluster, you mustmake sure that the following requirements are met.
Kubernetes: Versions 1.14–1.17
l Persistent volume support
l (Recommended) A load balancer service
l At least 7 GB of RAM and 1 CPU on a single node (with default configuration)
l Maximum usage: 28 GB of RAM and 8 CPUs on a single node (with default configuration)
l 4 GiB of storage for persistent volume (with default configuration)
Locally-Installed Tools Required
l A kubectl command-line tool - Fortify recommends using the same version as the Kubernetes clusterversion (1.14–1.17)
l Helm command-line tool, version 3.0 or 3.1
l Air-gapped installation only - (Recommended) A Docker client and server installation (any version)
System Requirements
Micro Focus Fortify Software (20.1.0) Page 19 of 50
Additional Requirements
l Kubeconfig file for the Kubernetes cluster
l Docker Hub account with access to Fortify Software Security Center images
Note: If you need access to Fortify Docker Organization on Docker Hub, [email protected] with your first name, your last name, and your Docker accountname. Micro Focus Fortify will then give you access to the Fortify Docker organization thatcontains the Fortify Software Security Center images.
l DNS name for the Fortify Software Security Center web application (address used to access theservice)
l Java keystore for setting up HTTPS (For details, see the Micro Focus Fortify Software SecurityCenter User Guide) The keystore must contain a CA certificate and a server certificate for the FortifySoftware Security Center DNS name with an associated private key.
l Keystore password
l Private key password
l An installed Oracle, SQL Server, or MySQL for database server
l Database server host name
l Name of the Fortify Software Security Center database
l Username and password for an account that has permission to manage the Fortify SoftwareSecurity Center schema and data
l (Oracle or MySQL database only) An HTTP server that is accessible from the Kubernetes clusterfor distributing the JDBC driver. For supported driver versions, see "Fortify Software SecurityCenter Database" on page 18.
l Fortify Software Security Center license
Browsers
Fortify recommends that you use one of the browsers listed in the following table and a screenresolution of 1400 x 800.
Browser Version
Google Chrome 65.0 or later
Microsoft Edge 38 or later
Mozilla Firefox 59.0 or later
Safari 11
System Requirements
Micro Focus Fortify Software (20.1.0) Page 20 of 50
Authentication Systems
Micro Focus Fortify Software Security Center supports the following directory services:
l LDAP: LDAP 3 compatible
Important! Although Fortify supports the use of multiple LDAP servers, it does not support theuse of multiple LDAP servers behind a load balancer.
l Windows Active Directory Service
Single Sign-On (SSO)
Fortify Software Security Center supports:
l Central Authorization Server (CAS) SSO
l HTTP Headers SSO (Oracle SSO, CA SSO)
l SAML 2.0 SSO
l SPNEGO/Kerberos SSO
l X.509 SSO
BIRT Reporting
Micro Focus Fortify Software Security Center custom reports support Business Intelligence andReporting Technology (BIRT) Designer version 4.4.2.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 21 of 50
Service Integrations for Fortify Software Security Center
Micro Focus Fortify Software Security Center supports the service integrations listed in the followingtable.
Service Applications Versions
Bug tracking Bugzilla 5.0.x
Micro Focus Application Lifecycle Management (ALM)/Quality Center Enterprise (QC)
12.50
Jira 7.1x through8.x
Team Foundation Server (TFS) 2015, 2017
Azure DevOps Server 2019
Azure DevOps (formerly VSTS)
Note: Only basic user password authentication issupported.
n/a
Authentication Active Directory 2008, 2012
Dynamic assessments Micro Focus Fortify WebInspect Enterprise 20.1.0
Fortify ScanCentral RequirementsMicro Focus Fortify ScanCentral has three major components: a ScanCentral Controller, ScanCentralclients, and ScanCentral sensors.
Application Servers
Micro Focus Fortify ScanCentral supports Apache Tomcat version 9.0.x for Java 8.
ScanCentral Controller Hardware Requirements
Fortify recommends that you install the ScanCentral Controller on a high-end 64-bit processor runningat 2 GHz with at least 8 GB of RAM.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 22 of 50
ScanCentral Controller Disk Space Requirements
To estimate the amount of disk space required on the machine that runs the ScanCentral Controller, useone of the following equations equation:
IntendedUse Equation
Remote scanonly
<Number_Jobs_Per_Day> x (<Avg_MBS_Size> + <Avg_FPR_Size> + <Avg_SCA_Log_Size>) x <Number_Days_Data_is_Persisted>
Remotetranslationand scan
<Number_Jobs_Per_Day> x (<Avg_Archived_Project_With_Dependencies_Size> +<Avg_FPR_Size> + <Avg_SCA_Log_ Size>) x <Number_Days_Data_is_Persisted>
By default, data is persisted for seven days.
ScanCentral Controller Platforms and Architectures
The ScanCentral Controller supports the platforms and architectures listed in the following table.
Operating System Versions
Windows Server 2012 R2
Server 2016
Server 2019
Linux Red Hat Enterprise Linux 6 update 5 and later
Red Hat Enterprise Linux 7.x
SUSE Linux Enterprise Server 12
ScanCentral Client and Sensor Hardware Requirements
ScanCentral clients and sensors run on any machine that supports Micro Focus Fortify Static CodeAnalyzer. Because ScanCentral clients and sensors are installed on build machines running Micro FocusFortify Static Code Analyzer, the hardware requirements are met.
See "Fortify Static Code Analyzer Requirements" on page 8 for hardware, software, and platform andarchitecture requirements.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 23 of 50
ScanCentral Sensor Disk Space Requirements
To estimate the amount of disk space required on the machine that runs a ScanCentral sensor, use oneof the following equations:
IntendedUse Equation
Remotescan only
<Number_of_Scans> x (<Average_MBS_Size> + <Average_FPR_Size> + <Average_SCA_Log_Size>) x <Number_Days_Data_is_Persisted>
Remotetranslationand scan
<Number_Jobs_Per_Day> x (<Avg_Archived_Project_With_Dependencies_Size> +<Avg_Project_With_Dependencies_Size> + <Avg_FPR_Size> + <Avg_SCA_Log_ Size>)x <Number_Days_Data_is_Persisted>
By default, data is persisted for seven days.
Supported Languages and Build Tools for ScanCentral SensorProject Translation
Micro Focus Fortify ScanCentral supports offloading project translation to ScanCentral sensors for thefollowing languages and build tools.
Supported Languages
Fortify ScanCentral supports offloading project translation to ScanCentral sensors for the followinglanguages. See "Supported Languages" on page 10 for specific supported versions.
l .NET applications in C# and VB.NET (.NET Core, .NET Standard, ASP.NET)
Note: Translation of .NET applications require .NET Framework version 4.7.2 or later.
l ABAP
l Apex
l Classic ASP
l ColdFusion
l Java
l JavaScript
l PHP
l PL/SQL
l Python
l Ruby
l T-SQL
System Requirements
Micro Focus Fortify Software (20.1.0) Page 24 of 50
l TypeScript
l Visual Basic
Supported Build Tools
Fortify ScanCentral supports the build tools listed in the following table.
Build Tool Version
Gradle 6.x
Maven 3.x
MSBuild 16.4
Fortify WebInspect Agent RequirementsMicro Focus Fortify WebInspect Agent technology is delivered for production application logging andprotection .
Platforms and Architectures
Fortify WebInspect Agent supports 32-bit and 64-bit applications written in Java 5, 6, 7, 8, and 10.
Java Runtime Environments
Fortify WebInspect Agent supports the Java runtime environments listed in the following table.
JRE Major Versions
IBM J9 5 (SR10 and later)
6 (SR6 and later)
Oracle HotSpot 5, 6, 7, 8
Oracle JRockit 5, 6 (R27.6 and later)
Note: The Java agent is supported on Windows, Linux, and Unix.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 25 of 50
Java Application Servers
Fortify WebInspect Agent supports the Java application servers listed in the following table.
Application Server Versions
Apache Tomcat 6.0, 7.0, 8.0, 9.0
IBM WebSphere 7.0, 8.0, 8.5, 8.5.5
Oracle WebLogic 10.0, 10.3, 11g, 11gR1, 12c
Red Hat JBoss Enterprise Application Platform 5.1.2, 5.2.0, 6.0.1, 6.1.1, 6.2.0, 6.3.0, 6.4.0
Jetty 9.3
WildFly 10.1
.NET Frameworks
Fortify WebInspect Agent supports .NET Framework versions 2.0, 3.0, 3.5, 4.0, 4.5, 4.5.1, and 4.7.
IIS for Windows Server
Fortify WebInspect Agent supports Internet Information Services (IIS) versions 6.0, 7.0, 7.5, 8, 8.5, and10.0.
Fortify WebInspect RequirementsBefore you install Micro Focus Fortify WebInspect, make sure that your system meets the requirementsdescribed in this section.
Running as Administrator
Micro Focus Fortify WebInspect requires administrative privileges for proper operation of all features.Refer to the Windows operating system documentation for instructions on changing the privilege levelto run Fortify WebInspect as an administrator.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 26 of 50
Hardware Requirements
Fortify recommends that you install Micro Focus Fortify WebInspect on a system that conforms to thesupported components listed in the following table. Fortify does not support beta or pre-releaseversions of operating systems, service packs, and required third-party components.
Component Requirement Notes
Processor 2.5 GHz quad-coreor faster
Complex applications might benefit from additional cores.
RAM 16 GB Complex applications might benefit from additional memory.
Hard disk 40 GB Using SQL Express and storing scans locally requiresadditional disk space per scan.
Display 1280 x 1024
Software Requirements
Micro Focus Fortify WebInspect runs on and works with the software packages listed in the followingtable.
Package Versions Notes
Windows Windows 10 Recommended
Windows 8.1
Windows Server 2016
Windows Server 2019
.NET Platform .NET Framework 4.8
SQL Server SQL Server 2014 SP3 Recommended
No scan database limit
SQL Server 2012 SP4 No scan database limit
SQL Server 2016 SP2 No scan database limit
SQL Server 2017 No scan database limit
System Requirements
Micro Focus Fortify Software (20.1.0) Page 27 of 50
Package Versions Notes
SQL Server 2019 No scan database limit
SQL Server Express SQL Server 2017 Express Recommended
10 GB scan database limit
SQL Server 2012 Express SP4 10 GB scan database limit
SQL Server 2014 Express SP3 10 GB scan database limit
SQL Server 2016 Express SP2 10 GB scan database limit
SQL Server 2019 Express 10 GB scan database limit
Browser Internet Explorer 11 Recommended
Internet Explorer 10
Portable Document Format Adobe Acrobat Reader 11 Recommended
Adobe Acrobat Reader 8.1.2 Minimum
Support for Postman
Postman collection version 2.1 is required for conducting scans in Fortify WebInspect. You do not needto install Postman on the machine where the Fortify WebInspect REST API is installed.
However, you must install the following third-party software on the machine where the FortifyWebInspect REST API is installed:
l Node.js 10.16.3 LTS and the included Node Package Manager (NPM)
l Newman command-line collection runner 4.5.1
Notes on SQL Server Editions
When using the Express edition of SQL Server:
l Scan data must not exceed the database size limit. If you require a larger database or you need toshare your scan data, use the full version of SQL Server.
l During the installation you might want to enable “Hide advanced installation options.” Accept alldefault settings. Micro Focus Fortify WebInspect requires that the default instance is namedSQLEXPRESS.
When using the full edition of SQL Server:
l You can install the full version of SQL Server on the local host or nearby (co-located). You canconfigure this option in Fortify WebInspect Application Settings (Edit > Application Settings >Database).
System Requirements
Micro Focus Fortify Software (20.1.0) Page 28 of 50
l The account specified for the database connection must also be a database owner (DBO) for thenamed database. However, the account does not require sysadmin (SA) privileges for the databaseserver. If the database administrator (DBA) did not generate the database for the specified user,then the account must also have the permission to create a database and to manipulate the securitypermissions. The DBA can rescind these permissions after Fortify WebInspect sets up the database,but the account must remain a DBO for that database.
WebInspect on Docker
Fortify WebInspect on Docker has the requirements listed in the following table.
Package Version Notes
Docker Enterprise 18.09 or later
Windows Windows Server 2016 Recommended
Windows 10
Ports and Protocols
This section describes the ports and protocols Micro Focus Fortify WebInspect uses to make requiredand optional connections.
Required Connections
The following table lists the ports and protocols Micro Focus Fortify WebInspect uses to make requiredconnections.
Direction Endpoint URL or Details Port Protocol Notes
FortifyWebInspectto targethost
Target host Scan target host Any HTTP Fortify WebInspect must connect to theweb application or web service to bescanned.
FortifyWebInspectto SQLdatabase
SQL Server Expressor SQL ServerStandard/Enterprise
SQLEXPRESS serviceon localhost or SQLTCP service locallyinstalled or remotehost
1433 SQL TCP Used to maintain the scan data and togenerate reports within the FortifyWebInspect application.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 29 of 50
Direction Endpoint URL or Details Port Protocol Notes
FortifyWebInspecttoCertificateRevocationList (CRL)
Verisign CRL http://crl.verisign.com/pca3.crl
or
http://csc3-2004-crl.verisign.com/CSC3-2004.crl
80 HTTP Offline installations of FortifyWebInspect or Fortify WebInspectEnterprise require you to manuallydownload and apply the CRL fromVerisign. Fortify WebInspect productsprompt for these lists from Windowsand their absence can cause problemswith the application. A one-timedownload is sufficient, however Fortifyrecommends that you download theCRL as part of regular maintenance.
Optional Connections
The following table lists the ports and protocols Micro Focus Fortify WebInspect uses to make optionalconnections.
Direction Endpoint URL or Details Port Protocol Notes
FortifyWebInspectto FortifyLicenseactivationserver
RemoteFortifyLicensingService
https://licenseservice.fortify.microfocus.com
443 HTTPSover SSL
For one-time activation of a FortifyWebInspect Named User license.You may optionally use thefollowing:
l An offline activation processinstead of using this directconnection
l Upstream proxy withauthentication instead of adirect connection
FortifyWebInspecttoSmartUpdateserver
RemoteSmartUpdateservice
https://smartupdate.fortify.microfocus.com
443 HTTPSover SSL
Used to automatically update theFortify WebInspect product.SmartUpdate is automatic whenopening the product UI, but can bedisabled and run manually. Canoptionally use upstream proxywith authentication instead of adirect connection.
FortifyWebInspectto FortifySupportChannelserver
RemoteFortifySupportChannelservice
https://supportchannel.fortify.microfocus.com
443 HTTPSover SSL
Used to retrieve productmarketing messages and toupload Fortify WebInspect data orproduct suggestions to Micro FocusFortify Customer Support. Messagecheck is automatic when openingthe product UI, but can bedisabled and run manually. Canoptionally use upstream proxy
System Requirements
Micro Focus Fortify Software (20.1.0) Page 30 of 50
Direction Endpoint URL or Details Port Protocol Notes
with authentication instead of adirect connection.
FortifyWebInspectto FortifyWebInspectTelemetryserver
RemoteFortifyWebInspectTelemetryandperformancereportingservice
https://telemetry.fortify.com
Note: Accessing thisURL in a browser doesnot display anycontent.
443 HTTPSover SSL
The Telemetry service provides anautomated process for collectingand sending Fortify WebInspectusage information to Micro Focus.Our software developers use thisinformation to help improve theproduct.
FortifyWebInspectto FortifyLicense andInfrastructureManager(LIM)
FortifyWebInspectLIM
(LocalLicensingService)
Lease Concurrent Userlicense
443 Webservicesover SSL
Required for Fortify WebInspectclient to lease and use aConcurrent User licensemaintained in a LIM license pool.You can detach the client licensefrom LIM after activation to avoida constant connection.
FortifyWebInspectAPI listener
Localmachine API,or network IPaddress
http://localhost:8083/webinspect/api
8083 oruser-specified
HTTP Use to activate a FortifyWebInspect API Windows Service.This opens a listening port onyour machine, which you can uselocally or remotely to generatescans and retrieve the resultsprogrammatically. This API can beSSL enabled, and supports Basic orWindows authentication.
FortifyWebInspectto FortifyWebInspectEnterprise
FortifyWebInspectEnterpriseserver
User-specified FortifyWebInspect server
443 oruser-specified
HTTP orHTTPSover SSL
The Enterprise Server menuconnects Fortify WebInspect as aclient to the enterprise securitysolution to transfer findings anduser role and permissionsmanagement.
FortifyWebInspectsensorservice toFortifyWebInspectEnterprise
FortifyWebInspectEnterpriseserver
User-specified FortifyWebInspect server
443 oruser-specified
HTTP orHTTPSover SSL
Separate from the FortifyWebInspect UI, you can configurethe local installation as a remotescan engine for use by theenterprise security solutioncommunity. This is done through aWindows Service. This constitutesa different product from FortifyWebInspect desktop and isrecommended to be run on itsown, non-user-focused machine.
Browser toFortify
localhost Manual Step-Mode Scan Dynamic,8081, or
HTTP orHTTPS
Fortify WebInspect serves as a webproxy to the browser, enabling
System Requirements
Micro Focus Fortify Software (20.1.0) Page 31 of 50
Direction Endpoint URL or Details Port Protocol Notes
WebInspect user-specified
over SSL manual testing of the target webserver through Fortify WebInspect.
FortifyWebInspectto QualityCenterEnterprise(ALM)
QC server User-specified ALM server Server-specified
HTTP orHTTPSover SSL
Permits submission of findings asdefects to the ALM bug tracker.
Connections for Tools
The following table lists the ports and protocols that the Micro Focus Fortify WebInspect tools use tomake connections.
Tool Direction Endpoint Port Protocol Notes
Web Proxy To target host localhost 8080 oruser-specified
HTTP orHTTPSover SSL
Intercepts and displays web traffic
Web FormEditor
To target host localhost Dynamic,8100, oruser-specified
HTTP orHTTPSover SSL
Intercepts web traffic and capturessubmitted forms
Login orWorkflowMacroRecorders
To target host localhost Dynamic,8081, oruser-specified
HTTP orHTTPSover SSL
Records browser sessions for replayduring scan
WebDiscovery
Fortify WebInspectmachine totargeted IP range
Targethostnetworkrange
User-specifiedrange
HTTPandHTTPSover SSL
Scanner for identifying rogue webapplications hosted among the targetedscanned IP and port ranges
Use to provide targets to FortifyWebInspect (manually)
Fortify WebInspect Agent
For system requirements, see "Fortify WebInspect Agent Requirements" on page 25.
WebInspect Software Development Kit (SDK)
The WebInspect SDK requires the following software:
l Visual Studio 2013 or 2015
l .NET Framework 4.6.1
System Requirements
Micro Focus Fortify Software (20.1.0) Page 32 of 50
Important! Visual Studio Express versions do not support third-party extensions. Therefore, theseversions do not meet the software requirements to use the WebInspect SDK.
Software Integrations for Fortify WebInspect
The following table lists products that you can integrate with Micro Focus Fortify WebInspect.
Product Versions
Micro Focus Fortify WebInspect Enterprise 20.1.0
Micro Focus Application Lifecycle Management (ALM)
Note: You must also install the ALM Connectivity tool to connect FortifyWebInspect to ALM.
11.5, 12.01, 12.21,12.53
Micro Focus Fortify Software Security Center 20.1.0
Micro Focus Unified Functional Testing 11.5
Fortify WebInspect Enterprise RequirementsBefore you install Micro Focus Fortify WebInspect Enterprise, make sure that your systems meet therequirements described in this section.
Note: Product versions that are not specifically listed in this document are not supported.
Installation and Upgrade Requirements
You can upgrade directly from Micro Focus Fortify WebInspect Enterprise 19.2.0 to Fortify WebInspectEnterprise 20.1.0. You cannot upgrade directly from any other versions of Fortify WebInspectEnterprise. For detailed information about upgrades, see the Micro Focus Fortify WebInspectEnterprise Installation and Implementation Guide.
Integration with Micro Focus Fortify Software Security Center is optional. If you are integrating FortifyWebInspect Enterprise with Fortify Software Security Center, then you must install and run FortifySoftware Security Center 20.1.0 before you install a new instance of Fortify WebInspect Enterprise orupgrade from Fortify WebInspect Enterprise 19.2.0. You can install Fortify Software Security Centerand Fortify WebInspect Enterprise on the same or different machines. Using separate machines mightimprove performance.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 33 of 50
Integrations for Fortify WebInspect Enterprise
You can integrate Micro Focus Fortify WebInspect Enterprise with the following components:
l Micro Focus Fortify WebInspect sensors 20.1.0
l Micro Focus Fortify WebInspect Agent 20.1.0
Fortify WebInspect Enterprise Database
Fortify recommends that you configure the database server on a separate machine from either MicroFocus Fortify Software Security Center or Micro Focus Fortify WebInspect Enterprise.
The Fortify WebInspect Enterprise Server SQL database requires case-insensitive collation.
Important! This is opposite the requirement for Fortify Software Security Center databases asdescribed in "Fortify Software Security Center Database" on page 18.
Hardware Requirements
The following table lists the hardware requirements for the Micro Focus Fortify WebInspect Enterpriseserver.
Component Requirement Notes
Processor 3.0 GHz quad-core or faster Recommended
2.5 GHz dual-core Minimum
RAM 16 GB Recommended
8 GB Minimum
Hard disk 100+ GB Recommended
20+ GB if using a local database
5 GB if using a remote database
Display 1920 x 1080 Recommended
1280 x 1024 Minimum
System Requirements
Micro Focus Fortify Software (20.1.0) Page 34 of 50
Software Requirements
Micro Focus Fortify WebInspect Enterprise server runs on and works with the software packages listedin the following table.
Package Versions Notes
Windows Windows Server 2016 Recommended
Windows Server 2019
.NET Platform .NET Framework 4.8
Web Server IIS 10 Recommended
IIS 7.5, 8.0, 8.5
SQL Server SQL Server 2014 SP3 Recommended
No scan database limit
SQL Server 2012 SP4 No scan database limit
SQL Server 2016 SP2 No scan database limit
SQL Server 2017 No scan database limit
SQL Server 2019 No scan database limit
Browser Mozilla Firefox 75 or later Recommended
Google Chrome 81 or later
Microsoft Edge 81 or later
Internet Explorer 11
Administrative Console Requirements
This section describes the hardware and software requirements for the Micro Focus Fortify WebInspectEnterprise Administrative Console.
You do not need to install the Fortify WebInspect Enterprise Administrative Console on the samemachine as the Web Console of the Fortify WebInspect Enterprise server. The two consoles havedifferent system requirements. In addition, you can install multiple Administrative Consoles on differentmachines connected to the same Fortify WebInspect Enterprise server.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 35 of 50
Hardware Requirements
The following table lists the hardware requirements for Fortify WebInspect Enterprise AdministrativeConsole.
Component Requirement Notes
Processor 2.5 GHz dual-core Minimum
RAM 4 GB Minimum
Hard disk 2 GB
Display 1980 x 1080 Recommended
1280 x 1024 Minimum
Software Requirements
The Fortify WebInspect Enterprise Administrative Console runs on and works with the softwarepackages listed in the following table.
Package Versions Notes
Windows Windows 10 Recommended
Windows 8.1
Windows Server 2016
Windows Server 2019
.NET .NET Framework 4.8
Ports and Protocols
This section describes the ports and protocols Micro Focus Fortify WebInspect Enterprise uses to makerequired and optional connections.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 36 of 50
Required Connections
The following table lists the ports and protocols Micro Focus Fortify WebInspect Enterprise uses tomake required connections.
Direction EndpointURL orDetails Port Protocol Notes
Fortify WebInspectEnterprise Managerserver to SQLdatabase
SQL ServerStandard/Enterprise
SQL TCPservice onlocallyinstalled orremote host
1433 oruser-specified
SQL TCP Used to maintain the scan dataand full Enterprise environment.Custom configurations ofSQL Server are permitted,including port changes andencrypted communication.
Fortify WebInspectEnterprise Managermachine to FortifySoftware SecurityCenter server
Fortify SoftwareSecurity Centerserver
User-specifiedFortifySoftwareSecurityCenterserver
8180 oruser-specified
HTTP orHTTPSover SSL
As a modular add-on, FortifyWebInspect Enterprise requires aconnection to its core FortifySoftware Security Center server.
Note: This connection isrequired only if you integrateFortify WebInspect Enterprisewith Fortify Software SecurityCenter.
Sensor machines toFortify WebInspectEnterprise Managerserver
Fortify WebInspectEnterprise server
User-specifiedFortifyWebInspectEnterpriseserver
443 oruser-specified
HTTPSover SSL
Communication is two-way HTTPtraffic, initiated in-bound by theFortify WebInspect sensormachine.
Browser users toFortify WebInspectEnterprise server UI
Fortify WebInspectEnterprise server
User-specifiedFortifyWebInspectEnterpriseserver
443 oruser-specified
HTTPSover SSL
You can configure FortifyWebInspect Enterprise not to useSSL, but tests indicate that it mightaffect the product usability.
Browser user toFortify SoftwareSecurity Center UI
Fortify SoftwareSecurity Centerserver
User-specifiedFortifySoftwareSecurityCenterserver
8180 oruser-specified
HTTP orHTTPSover SSL
You can configure the FortifySoftware Security Center server onany available port duringinstallation.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 37 of 50
Optional Connections
The following table lists the ports and protocols Micro Focus Fortify WebInspect Enterprise uses tomake optional connections.
Direction Endpoint URL or Details Port Protocol Notes
FortifyWebInspectdesktopmachines toFortifyWebInspectEnterpriseManagerserver
FortifyWebInspectEnterpriseserver
User-specified FortifyWebInspectEnterprise server
443 oruser-specified
HTTPSover SSL
Communication is two-way HTTP traffic,initiated in-bound by the FortifyWebInspect desktop machine.
FortifyWebInspectEnterpriseManagermachine toFortifyLicenseactivationserver
FortifyLicensingService
https://licenseservice.fortify.microfocus.com
443 HTTPSover SSL
For one-time activation of the FortifyWebInspect Enterprise server license aswell as periodic checks during an update.You may optionally use the following:
l An offline activation process instead ofusing this direct connection
l Upstream proxy with authenticationinstead of a direct Internet connection
Important! If you use the offlineactivation process, then you mustalso use the offline SmartUpdateprocess. For more information, seethe Micro Focus Fortify WebInspectEnterprise User Guide or theWebInspect EnterpriseAdministrative Console help.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 38 of 50
Direction Endpoint URL or Details Port Protocol Notes
FortifyWebInspectEnterpriseManagermachine toSmartUpdateserver
SmartUpdate https://smartupdate.fortify.microfocus.com
443 HTTPSover SSL
Used to acquire product updates as wellas all connected clients (FortifyWebInspect sensors and FortifyWebInspect desktop). The administratormanually runs SmartUpdate, howeverFortify recommends that you set up anautomated schedule. New client releasesare held in reserve until the FortifyWebInspect Enterprise administratormarks them as Approved, at which timethey are automatically distributed fromthe Fortify WebInspect EnterpriseManager server. Can support the use ofan upstream proxy with authenticationinstead of a direct Internet connection.
Important! Access to theSmartUpdate server also requiresaccess to the licensing server. If youhave restrictions on outgoing traffic,you must whitelist both theSmartUpdate server and thelicensing server.
FortifyWebInspectEnterpriseManagermachine tomail server
User’s mailserver
Email alerts 25 oruser-specified
SMTP Used for SMTP alerts for administrationteam. To enable mobile TXT alerts, youcan use an SMTP-to-SMS gatewayaddress.
FortifyWebInspectEnterpriseManagermachine toSNMPCommunity
User’s SNMPCommunity
SNMP alerts 162 oruser-specified
SNMP Used for SNMP alerts for administrationteam.
Connections for Tools
The following table lists the ports and protocols that the Micro Focus Fortify WebInspect Enterprisetools use to make connections.
Tool Direction Endpoint Port Protocol Notes
Web Proxy To targetwebapplication
localhost 8080 oruser-specified
HTTP orHTTPSover SSL
Intercepts and displays web traffic
System Requirements
Micro Focus Fortify Software (20.1.0) Page 39 of 50
Tool Direction Endpoint Port Protocol Notes
Web FormEditor
To targetwebapplication
localhost Dynamic,8100, oruser-specified
HTTP orHTTPSover SSL
Intercepts web traffic and captures submittedforms
Login orWorkflow MacroRecorders
To targetwebapplication
localhost Dynamic,8081, oruser-specified
HTTP orHTTPSover SSL
Records browser sessions for replay duringscan
Web Discovery Totargeted IPrange
localhost User-specifiedrange
HTTPandHTTPSover SSL
Scanner for identifying rogue webapplications hosted among the targetedscanned IP and port ranges
Use to provide targets to Fortify WebInspect(manually)
Fortify WebInspect Enterprise Sensor
A Micro Focus Fortify WebInspect Enterprise sensor is a Micro Focus Fortify WebInspect sensor thatruns scans on behalf of Fortify WebInspect Enterprise. See "Fortify WebInspect Requirements" onpage 26 for more information.
To run a scan from Fortify WebInspect Enterprise, you must have at least one instance of FortifyWebInspect connected and configured as a sensor.
Fortify WebInspect Enterprise Notes and Limitations
l You can connect any instance of Micro Focus Fortify Software Security Center to only one instanceof Micro Focus Fortify WebInspect Enterprise, and you can connect any instance of FortifyWebInspect Enterprise to only one instance of Fortify Software Security Center.
l For a Fortify WebInspect Enterprise environment to support Internet Protocol version 6 (IPv6), youmust deploy the IPv6 protocol on each Fortify WebInspect Enterprise Administrative Console, eachFortify WebInspect Enterprise sensor, and the Fortify WebInspect Enterprise server.
Fortify License and Infrastructure ManagerRequirementsThis section describes the hardware and software requirements for Micro Focus Fortify License andInfrastructure Manager (LIM).
Hardware Requirements
Fortify recommends that you install the LIM on a system that conforms to the supported componentslisted in following table. Beta or pre-release versions of operating systems, service packs, and requiredthird-party components are not supported.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 40 of 50
Component Requirement Notes
Processor 2.5 GHz single-core or faster Recommended
1.5 GHz single-core Minimum
RAM 2+ GB Recommended
1 GB Minimum
Hard disk 50+ GB Recommended
20 GB Minimum
Display 1280 x 1024 Recommended
1024 x 768 Minimum
Software Requirements
LIM runs on and works with the software packages listed in the following table.
Package Versions Notes
Windows Server Windows Server 2012, 2012 R2
Windows Server 2016
Windows Server 2019
Web Server IIS 8.5 Recommended
IIS 7.5, 8.0, 10
.NET Platform .NET Framework 4.5, 4.6.1
ASP.NET4.5, 4.6
Browser Internet Explorer 11 Recommended
Mozilla Firefox 51.0 Recommended
Mozilla Firefox 44.0, 47.0, 69.0
System Requirements
Micro Focus Fortify Software (20.1.0) Page 41 of 50
Version Compatibility MatrixThis section provides compatibility information for Micro Focus Fortify Software components.
Fortify Software Component Compatibility
Micro Focus Fortify Software version 20.1.0 works with the component versions listed in the followingtable.
Component Version
Micro Focus Fortify Software Security Center 20.1.0
Micro Focus Fortify Static Code Analyzer Tools(Micro Focus Fortify Audit Workbench, Fortify Secure Code Plugins, and Fortify CustomRules Editor)
20.1.0
Micro Focus Fortify WebInspect Agent 20.1.0
Micro Focus Fortify WebInspect 20.1.0
Micro Focus Fortify WebInspect Enterprise 20.1.0
FPR File Compatibility
Earlier versions of Micro Focus Fortify Software products cannot open and read FPR files generated bylater versions of Fortify Software products. For example, Micro Focus Fortify Audit Workbench 18.20cannot read 20.1.0 FPR files. However, later versions of Fortify Software products can open and readFPR files generated by earlier versions of Fortify Software products. For example, Fortify AuditWorkbench version 20.1.0 can open and read version 18.20 FPR files.
FPR version numbers are determined as follows:
l The FPR version is the same as the version of the analyzer that initially generated it. For example, anFPR generated by Fortify Software version 20.1.0 also has the version number 20.1.0.
l The FPR version is the same as the version of the Micro Focus Fortify Software Security Center orMicro Focus Fortify Static Code Analyzer Tool used to modify or audit the FPR.
l If you merge two FPRs, the resulting FPR has the version of the more recently generated FPR. Forexample, if you merge a version 18.20 FPR with a version 20.1.0 FPR, the resulting FPR has theversion number 20.1.0.
You can only open 20.1.0 FPR files with Fortify Software Security Center or Fortify Static CodeAnalyzer Tools version 20.1.0 or later.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 42 of 50
Caution Regarding Uploading FPRs to Fortify Software Security Center
Fortify Software Security Center keeps a project file that contains the latest scan results and auditinformation for each application. Fortify Audit Workbench and the Secure Code Plugins also use thisproject file for collaborative auditing.
Each time you upload an FPR to Fortify Software Security Center, it is merged with the existing projectfile. If the FPR has a later version number than the existing project file, the existing project file versionchanges to match the FPR. For Fortify Audit Workbench and the Secure Code Plugins to work with theupdated FPR, they must be at least the same version as the FPR. For example, Fortify Audit Workbench18.20 cannot open and read a 20.1.0 FPR.
Virtual Machine SupportYou can run Micro Focus Fortify Software products on an approved operating system in virtual machineenvironments. You must provide dedicated CPU and memory resources that meet the minimumhardware requirements. If you find issues that cannot be reproduced on the native environments withthe recommended processing, memory, and disk resources, you must work with the provider of thevirtual environment to resolve them.
Note: Running Fortify Software products in a VM environment with shared CPU and memoryresources is not supported.
Technologies and Features no Longer Supported inthis ReleaseThe following technologies and features are no longer supported in Fortify Software:
l Fortify Static Code Analyzer: Translating .NET binaries and translating with custom MSBuild tasks
l Build Tools:
l Xcodebuild 10.0, 10.1, 10.2, 10.2.1, 10.3
l Compilers:
l Clang 10.0, 10.0.1
l Swiftc 4.2, 4.2.1, 5.0, 5.0.1
l All compilers on Solaris
l Databases (Fortify Software Security Center):
l Oracle 18c (18.3)
l Integrated Development Environments (IDEs):
l Android Studio 3.1
l IntelliJ IDEA 2018.x
System Requirements
Micro Focus Fortify Software (20.1.0) Page 43 of 50
l PyCharm 2018.x
l WebStorm 2018.x
l Operating Systems:
l macOS 10.13
l Solaris
l Supported Languages:
l .NET Core 1.x
l Swift 4.2
The following Micro Focus Fortify Software Security Center features are no longer supported:
l Authentication Tokens
The JenkinsToken type has been removed from this release. Use the CIToken type instead.
Technologies and Features to Lose Support in theNext ReleaseThe following technologies and features are scheduled for deprecation in the next Micro Focus FortifySoftware release:
l Application Server (Micro Focus Fortify Software Security Center):
l JDK 8 for Apache Tomcat
l Bug Trackers:
l Team Foundation Server (TFS) 2015 and 2017
l Databases (Fortify Software Security Center):
l MySQL 5.7 (Community Edition)
l SQL Server 2016
l Fortify Software Security Center (deployment to a Kubernetes cluster only):
l Kubernetes versions 1.14 through 1.15
l Fortify Static Code Analyzer support for all Swift, Xcode, and Objective-C/C++ versions will followthe deprecation path Apple Inc. adopts.
The following Micro Focus Fortify Static Code Analyzer features are scheduled for deprecation in thenext release:
l Incremental Analysis
System Requirements
Micro Focus Fortify Software (20.1.0) Page 44 of 50
The following Fortify Software Security Center and Fortify Static Code Analyzer Tools features arescheduled for deprecation in the next release:
l Authentication Tokens:
Use the new ScanCentralCtrlToken type instead of CloudCtrlToken. The CloudCtrlToken type will beremoved in the next release.
l Reports:
l DISA STIG 3.x
l SSA Portfolio
l SSA Application
l External Metadata Mappings:
l DISA STIG 3.x
Acquiring Fortify SoftwareMicro Focus Fortify Software is available as an electronic download. For instructions on how todownload the software from Micro Focus Fortify Customer Support(https://softwaresupport.softwaregrp.com), click Contact Us / Self Help from the Software Licensesand Downloads page to review the videos and the Quick Start Guide.
The following table lists the available packages and describes their contents.
File Name Description
Fortify_SCA_and_Apps_20.1.0_Windows.zip
Fortify SCA and Applications installer for Windows
This installer includes the following components:
l Fortify Static Code Analyzer
l Fortify Audit Workbench
l Fortify Custom Rules Editor
l Fortify Plugin for Eclipse
l Fortify Analysis Plugin for IntelliJ and Android Studio
l Fortify Extension for Visual Studio
l Fortify Scan Wizard
l Sample applications
Note:
l Fortify Software Security Content (Rulepacks and external metadata)can be downloaded during the installation.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 45 of 50
File Name Description
l The package includes the Fortify Remediation Plugin for Eclipse, theFortify Security Assistant Plugin for Eclipse, and the FortifyRemediation Plugin for JetBrains IDEs.
Fortify_SCA_and_Apps_20.1.0_Windows.zip.sig
Signature file for the Fortify SCA and Applications package for Windows
Fortify_SCA_and_Apps_20.1.0_Linux.tar.gz
Fortify SCA and Applications installer for Linux
The installer includes the following components:
l Fortify Static Code Analyzer
l Fortify Audit Workbench
l Fortify Custom Rules Editor
l Fortify Plugin for Eclipse
l Fortify Analysis Plugin for IntelliJ and Android Studio
l Fortify Scan Wizard
l Sample applications
Note:
l Fortify Software Security Content (Rulepacks and external metadata)can be downloaded during the installation.
l The package includes the Fortify Remediation Plugin for Eclipse, theFortify Security Assistant Plugin for Eclipse, and the FortifyRemediation Plugin for JetBrains IDEs.
Fortify_SCA_and_Apps_20.1.0_Linux.tar.gz.sig
Signature file for Fortify Static Code Analyzer for Linux
Fortify_SCA_and_Apps_20.1.0_Mac.tar.gz
Fortify SCA and Applications installer for macOS
This installer includes the following components:
l Fortify Static Code Analyzer
l Fortify Audit Workbench
System Requirements
Micro Focus Fortify Software (20.1.0) Page 46 of 50
File Name Description
l Fortify Custom Rules Editor
l Fortify Plugin for Eclipse
l Fortify Analysis Plugin for IntelliJ and Android Studio
l Fortify Scan Wizard
l Sample applications
Note:
l Fortify Software Security Content (Rulepacks and external metadata)can be downloaded during the installation.
l The package includes the Fortify Remediation Plugin for Eclipse, theFortify Security Assistant Plugin for Eclipse, and the FortifyRemediation Plugin for JetBrains IDEs.
Fotify_SCA_and_Apps_20.1.0_Mac.tar.gz.sig
Signature file for the Fortify SCA and Applications package for macOS
Fortify_SSC_Server_20.1.0.zip
Fortify Software Security Center
Fortify_SSC_Server_20.1.0.zip.sig
Signature file for Fortify Software Security Center
Fortify_ScanCentral_Controller_20.1.0.zip
Fortify ScanCentral Controller
Fortify_ScanCentral_Controller_20.1.0.zip.sig
Signature file for Fortify ScanCentral Controller
WebInspect_64_20.1.0.zip
Fortify WebInspect 64-bit package
This package includes product documentation (PDF)
WebInspectToolkit_20.1.0.zip
Fortify WebInspect Toolkit package for use with Fortify WebInspectEnterprise
System Requirements
Micro Focus Fortify Software (20.1.0) Page 47 of 50
File Name Description
WebInspect_Agent_20.1.0.zip
Fortify WebInspect Agent package
WI_Enterprise_20.1.0.zip
Fortify WebInspect Enterprise package
The package includes the following components:
l Fortify WebInspect Enterprise server
l Fortify WebInspect Enterprise Administrative Console
l Product documentation (PDF)
About Verifying Software Downloads
This topic describes how to verify the digital signature of the signed file that you downloaded from theMicro Focus Fortify Customer Support site. Verification ensures that the downloaded package has notbeen altered since it was signed and posted to the site. Before proceeding with verification, downloadthe Fortify Software product files and their associated signature (*.sig) files. You are not required toverify the package to use the software, but your organization might require it for security reasons.
Preparing Your System for Digital Signature Verification
Note: These instructions describe a third-party product and might not match the specific,supported version you are using. See your product documentation for the instructions for yourversion.
To prepare your system for electronic media verification:
1. Navigate to the GnuPG site (http://www.gnupg.org).
2. Download and install GnuPG Privacy Guard version 1.4.x or 2.0.x.
3. Generate a private key, as follows:
a. Run the following command (on a Windows system, run the command without the $ prompt):
$ gpg --gen-keyb. When prompted for key type, select DSA and Elgamal.
c. When prompted for a key size, select 2048.
d. When prompted for the length of time the key should be valid, select key does not expire.e. Answer the user identification questions and provide a passphrase to protect your private key.
4. Download the Micro Focus GPG public keys (compressed tar file) from the following location:
https://entitlement.mfgs.microfocus.com/ecommerce/efulfillment/digitalSignIn.do
5. Extract the public keys.
6. Import each downloaded key with GnuPG, as follows:
l Run gpg --import <Path_to_Key>/<File_Name_of_Key>
System Requirements
Micro Focus Fortify Software (20.1.0) Page 48 of 50
Verifying Software Downloads
To verify that the signature file matches the downloaded software package:
1. Navigate to the directory where you stored the downloaded package and signature file.
2. Run the following command:
gpg --verify <Signature_File_Name> <Downloaded_File_Name>3. Examine the output to make sure that you receive verification that the software you downloaded is
signed by Micro Focus Group Limited and is unaltered. Your output will include something similarto the following:
gpg: Signature made Fri, Oct 06, 2017 10:37:56 PM PDT using RSA key IDAA71A9CFgpg: checking the trustdbgpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust modelgpg: depth: 0 valid: 3 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 3ugpg: next trustdb check due at 2025-12-07gpg: Good signature from "Micro Focus Group Limited RSA-2048-12"
Note: A warning message might be displayed because the public key is not known to the system.You can ignore this warning or set up your environment to trust these public keys.
Assistive Technologies (Section 508)In accordance with section 508 of the Rehabilitation Act, Micro Focus Fortify Audit Workbench hasbeen engineered to work with the JAWS screen reading software package from Freedom Scientific.JAWS provides text-to-speech support for use by the visually impaired. With JAWS, labels, text boxes,and other textual components can be read aloud, providing greater access to these technologies.
Micro Focus Fortify Software Security Center works well with the ChromeVox screen reader.
System Requirements
Micro Focus Fortify Software (20.1.0) Page 49 of 50
Send Documentation FeedbackIf you have comments about this document, you can contact the documentation team by email. If anemail client is configured on this computer, click the link above and an email window opens with thefollowing information in the subject line:
Feedback on System Requirements (Fortify Software 20.1.0)
Just add your feedback to the email and click send.
If no email client is available, copy the information above to a new message in a web mail client, and sendyour feedback to [email protected].
We appreciate your feedback!
Micro Focus Fortify Software (20.1.0) Page 50 of 50