OpenText Fortify
OpenText Fortify: Application Security Testing (AST) platform. SAST, DAST, SCA, IAST. Application security in CI/CD. Formerly Micro Focus Fortify.

Key Features
- SAST - Static Application Security Testing (Static Code Analyzer)
- DAST - Dynamic Application Security Testing (WebInspect)
- SCA - Software Composition Analysis (open source)
- IAST - Interactive testing in runtime
- SSC - Software Security Center for management
OpenText Fortify Models
Choose the model that fits your organization's needs
OpenText Fortify Platform
OpenText Fortify Platform: application security across the software lifecycle. Static and dynamic testing, open source analysis, shared findings management.
OpenText Fortify DAST
OpenText Fortify DAST: dynamic security testing of running web applications and APIs. CI/CD pipeline scanning, ScanCentral, authenticated sessions.
OpenText Fortify Static Code Analyzer
OpenText Fortify Static Code Analyzer: static source code analysis. Detect and eliminate code vulnerabilities.
OpenText Fortify WebInspect
OpenText Fortify WebInspect: dynamic scanning of running web applications. Vulnerability detection without access to source code, FAST Proxy, CI/CD integration.
OpenText Fortify Software Security Center
OpenText Fortify Software Security Center: a shared place for results from static, dynamic and open source testing. Triage, tracking, on-premises deployment.
OpenText Fortify Software Composition Analysis
OpenText Fortify Software Composition Analysis: open source dependency analysis. SBOM generation, licence identification, vulnerability detection in components.
Table of Contents
What is OpenText Fortify?
The three kinds of application testing answer three different cybersecurity questions, and no organization starts all three at once. Static analysis asks what is in the code, dynamic asks what a stranger can reach, composition analysis asks whose code you inherited. Which comes first depends on where your last incident came from.
OpenText Fortify (formerly Micro Focus Fortify) is an Application Security Testing (AST) platform - tools for detecting vulnerabilities in applications at every stage of the SDLC. From source code analysis, through dynamic testing, to open source component analysis.
Main components:
- Static Code Analyzer (SAST) - source code analysis
- WebInspect (DAST) - dynamic testing of running applications
- Software Composition Analysis (SCA) - dependency security
- Software Security Center (SSC) - centralized management
What problem does it solve?
flowchart LR
subgraph Without AST
A[Developer writes code] --> B[Deploy to prod]
B --> C[Hacker finds bug]
C --> D[Breach / fix cost]
end
subgraph With Fortify
E[Developer writes code] --> F[SAST in IDE]
F --> G[DAST before prod]
G --> H[Secure release]
end
style A fill:#dc2626,stroke:#b91c1c,color:#fff
style B fill:#dc2626,stroke:#b91c1c,color:#fff
style C fill:#dc2626,stroke:#b91c1c,color:#fff
style D fill:#dc2626,stroke:#b91c1c,color:#fff
style E fill:#22c55e,stroke:#16a34a,color:#fff
style F fill:#22c55e,stroke:#16a34a,color:#fff
style G fill:#22c55e,stroke:#16a34a,color:#fff
style H fill:#22c55e,stroke:#16a34a,color:#fff
Common problems:
- Vulnerabilities detected only in production (or by hackers)
- No visibility - how many vulnerabilities do we have in portfolio?
- Open source components with CVEs
- Compliance requires security testing (PCI DSS, OWASP)
- DevOps without security - “DevSecOps” only on paper
How does Fortify work?
flowchart TD
A[Source code] --> B[Static Code Analyzer]
B --> C[SAST results]
D[Running application] --> E[WebInspect]
E --> F[DAST results]
G[Dependencies] --> H[SCA]
H --> I[CVEs in libraries]
C --> J[Software Security Center]
F --> J
I --> J
J --> K[Dashboard]
J --> L[Reports]
J --> M[Remediation tracking]
style A fill:#6366f1,stroke:#4f46e5,color:#fff
style B fill:#8b5cf6,stroke:#7c3aed,color:#fff
style D fill:#6366f1,stroke:#4f46e5,color:#fff
style E fill:#f59e0b,stroke:#d97706,color:#fff
style G fill:#6366f1,stroke:#4f46e5,color:#fff
style H fill:#22c55e,stroke:#16a34a,color:#fff
style J fill:#dc2626,stroke:#b91c1c,color:#fff
Fortify Components
Static Code Analyzer
SAST - code analysis
- 33+ programming languages
- 1000+ vulnerability categories
- Data flow analysis
- IDE plugins
WebInspect
DAST - dynamic testing
- Automated web scanning
- API testing (REST, SOAP)
- Authenticated scanning
- OWASP Top 10 coverage
Software Composition Analysis
SCA - open source
- Library identification
- CVE matching
- License compliance
- SBOM generation
Software Security Center
Centralized management
- Result aggregation
- Trend analysis
- Remediation workflow
- Reporting / compliance
Fortify on Demand
SaaS - hosted testing
- SAST as a Service
- DAST as a Service
- Mobile testing
- Expert remediation
Audit Workbench
Result analysis
- Vulnerability triage
- False positive suppression
- Code navigation
- Fix recommendations
SAST vs DAST vs SCA
| Aspect | SAST (Static Code Analyzer) | DAST (WebInspect) | SCA |
|---|---|---|---|
| What it analyzes | Source code | Running application | Dependencies (libs) |
| When | Development, CI | QA, before prod | Build time |
| Coverage | Entire code | Available endpoints | Open source |
| False positives | More | Less | Low |
| Requires | Source access | Application URL | Manifest/lock file |
flowchart LR
A[Code] --> B[SAST]
B --> C[Build]
C --> D[SCA]
D --> E[Deploy]
E --> F[DAST]
F --> G[Production]
style A fill:#6366f1,stroke:#4f46e5,color:#fff
style B fill:#8b5cf6,stroke:#7c3aed,color:#fff
style C fill:#6366f1,stroke:#4f46e5,color:#fff
style D fill:#22c55e,stroke:#16a34a,color:#fff
style E fill:#6366f1,stroke:#4f46e5,color:#fff
style F fill:#f59e0b,stroke:#d97706,color:#fff
style G fill:#22c55e,stroke:#16a34a,color:#fff
Supported languages (SAST)
| Category | Languages |
|---|---|
| Web | Java, C#, JavaScript, TypeScript, PHP, Python, Ruby, Go |
| Mobile | Swift, Objective-C, Kotlin, Java (Android) |
| System | C, C++, Rust |
| Scripting | Python, Perl, Bash |
| Other | COBOL, ABAP, Apex (Salesforce), SQL |
| Frameworks | Spring, .NET, React, Angular, Vue, Django, Rails |
DevSecOps Integration
Fortify integrates with CI/CD pipelines:
CI/CD
Jenkins, Azure DevOps, GitLab CI, GitHub Actions, Bamboo
IDE
VS Code, IntelliJ, Eclipse, Visual Studio
SCM
GitHub, GitLab, Bitbucket, Azure Repos
Issue Tracking
Jira, Azure Boards, ServiceNow
Who is it for?
Fortify MAKES sense when:
- • You develop your own applications (in-house development)
- • Compliance requires security testing (PCI DSS, OWASP)
- • You have multiple development teams
- • You want DevSecOps - security in CI/CD
- • You use multiple programming languages
Fortify DOESN'T make sense when:
- • You only buy ready-made applications (SaaS)
- • Small team - Snyk, SonarQube may suffice
- • No budget for enterprise AST
- • You only need SCA - consider Snyk, Mend
Fortify vs competition
| Aspect | Fortify | Checkmarx | Veracode | Snyk | SonarQube |
|---|---|---|---|---|---|
| SAST | Yes | Yes | Yes | Yes | Yes |
| DAST | WebInspect | No | Yes | No | No |
| SCA | Yes | Yes | Yes | Core | Community |
| Languages | 33+ | 30+ | 100+ | 10+ | 30+ |
| On-prem | Yes | Yes | No | No | Yes |
| Deployment | On-prem + SaaS | On-prem + SaaS | SaaS | SaaS | On-prem |
| Price | Premium | Premium | Premium | Freemium | Free + Paid |
Fortify advantage:
- Complete platform (SAST + DAST + SCA)
- On-premises option for regulated industries
- 33+ languages with deep analysis
- Software Security Center for governance
Specifications
| Parameter | Value |
|---|---|
| Deployment | On-premises, Fortify on Demand (SaaS), Hybrid |
| SAST | 33+ languages, 1000+ vulnerability categories |
| DAST | Web apps, APIs (REST, SOAP, GraphQL) |
| SCA | NVD, proprietary vulnerability database |
| Standards | OWASP Top 10, SANS 25, CWE, PCI DSS |
| Integration | Jenkins, Azure DevOps, GitLab, GitHub, IDE |
| Reporting | SSC dashboard, PDF, CSV, SARIF |
FAQ
SAST or DAST - which to choose? Both. SAST finds problems in code (early, more false positives). DAST tests running application (later, fewer FP). Together they provide best coverage.
How long does SAST scan take? Depends on code size. Small project: minutes. Large enterprise: hours. Can scan incrementally (only changed code).
Can WebInspect “break” the application? DAST is active testing - may trigger errors. Don’t run on production without preparation. Staging/QA is the best environment.
What about false positives? SAST generates more FP. Fortify has “Audit Workbench” for triage. You can mark FP - they won’t return in future scans.
Fortify on Demand vs on-premises? FoD is SaaS - code sent to OpenText cloud. On-prem for sensitive code (finance, government). Hybrid also possible.
How to start?
- Choose pilot applications
- Install SAST in CI/CD
- Train developers with Audit Workbench
- Add DAST before prod
- Expand to portfolio
Does nFlo implement Fortify? Yes. SAST/DAST/SCA deployments, CI/CD integration, developer training, SSC configuration.
Inquire about OpenText Fortify
Contact your product specialist and get a custom quote.

Related Services
Our services supporting the implementation and management of this solution
Web Application Penetration Testing
Cybersecurity
One SQL injection = access to entire database. Find vulnerabilities before hackers do.
Source Code Security Review
Cybersecurity
Find critical vulnerabilities in code before they reach production. Save 10x the cost of fixing.
Active Directory Security Audit
Cybersecurity
We find paths to Domain Admin before attackers do.
CIS Security Audit
Cybersecurity
Harden system configurations to CIS Benchmarks. Close the default settings attackers look for.
From Our Knowledge Base
Articles related to this solution
Clean restore point after ransomware: how to check a backup before you restore it
A practical guide to ransomware recovery: how to choose a clean restore point, why the latest backup may be infected, where and what to check before restoring, how to rebuild identity and in what order to return to production — based on CISA, NIST and CERT Polska.
GRC (governance, risk, compliance): how to combine them in one cybersecurity process
A guide to GRC in cybersecurity: the OCEG definition, the difference between governance, risk and compliance, the GOVERN function in NIST CSF 2.0, board obligations under NIS2, the amended Polish Act on the National Cybersecurity System and DORA, a shared register of requirements, risks and controls, and a maturity check for the process.
DNSSEC: what it protects, what it doesn't and how to enable it for a .pl domain
A practical guide to DNSSEC for administrators and CISOs: the chain of trust, protection against forged answers, the limits of that protection (confidentiality, DoS, the registrar account), DoT and DoH, checking a domain, enabling it for .pl through the registrar, choosing an algorithm under RFC 9904, typical outages and NIS2 requirements.
Related Products
Other solutions you might be interested in
Aruba ClearPass
Aruba Networks
Aruba ClearPass: NAC platform with profiling of 70+ thousand device types. Zero Trust access control for users, BYOD, and IoT.
Barracuda CloudGen Firewall
Barracuda Networks
Barracuda CloudGen Firewall: next-gen firewall with SD-WAN. IPS, application control, VPN, threat protection. Appliance, virtual, cloud.
Barracuda Email Protection
Barracuda Networks
Barracuda Email Protection: AI-powered email security against phishing, ransomware, BEC and account takeover. Gateway + API for Microsoft 365 and Google.
Barracuda SecureEdge
Barracuda Networks
Barracuda SecureEdge: SASE platform combining SD-WAN with cloud security. Zero Trust, SWG, CASB, FWaaS. Protection for distributed workforce.
Want to Reduce IT Risk and Costs?
Book a consultation - we respond within 24h
Or download free guide:
E-book: Digital Resilience Strategy 2026