Skip to content
Cybersecurity OpenText

OpenText Fortify

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

Sales Representative
Łukasz Gil

Łukasz Gil

Sales Representative

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
Available now
Łukasz Gil

Łukasz Gil

Sales Representative

Send inquiry
Table of Contents

What is OpenText Fortify?

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

AspectSAST (Static Code Analyzer)DAST (WebInspect)SCA
What it analyzesSource codeRunning applicationDependencies (libs)
WhenDevelopment, CIQA, before prodBuild time
CoverageEntire codeAvailable endpointsOpen source
False positivesMoreLessLow
RequiresSource accessApplication URLManifest/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)

CategoryLanguages
WebJava, C#, JavaScript, TypeScript, PHP, Python, Ruby, Go
MobileSwift, Objective-C, Kotlin, Java (Android)
SystemC, C++, Rust
ScriptingPython, Perl, Bash
OtherCOBOL, ABAP, Apex (Salesforce), SQL
FrameworksSpring, .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

AspectFortifyCheckmarxVeracodeSnykSonarQube
SASTYesYesYesYesYes
DASTWebInspectNoYesNoNo
SCAYesYesYesCoreCommunity
Languages33+30+100+10+30+
On-premYesYesNoNoYes
DeploymentOn-prem + SaaSOn-prem + SaaSSaaSSaaSOn-prem
PricePremiumPremiumPremiumFreemiumFree + 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

ParameterValue
DeploymentOn-premises, Fortify on Demand (SaaS), Hybrid
SAST33+ languages, 1000+ vulnerability categories
DASTWeb apps, APIs (REST, SOAP, GraphQL)
SCANVD, proprietary vulnerability database
StandardsOWASP Top 10, SANS 25, CWE, PCI DSS
IntegrationJenkins, Azure DevOps, GitLab, GitHub, IDE
ReportingSSC 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?

  1. Choose pilot applications
  2. Install SAST in CI/CD
  3. Train developers with Audit Workbench
  4. Add DAST before prod
  5. 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.

Sales Representative
Łukasz Gil

Łukasz Gil

Sales Representative

Response within 24 hours
Free technical consultation
Custom quote and configuration

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a free consultation - we respond within 24h

Response in 24h Free quote No obligations

Or download free guide:

Download NIS2 Checklist