No more typing reviews! Try our Samantha, our new voice AI agent.

FOSSA vs OpenText Static Application Security Testing comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

FOSSA
Average Rating
8.6
Reviews Sentiment
7.9
Number of Reviews
15
Ranking in other categories
Software Composition Analysis (SCA) (11th)
OpenText Static Application...
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
19
Ranking in other categories
Static Code Analysis (8th)
 

Mindshare comparison

While both are Security Software solutions, they serve different purposes. FOSSA is designed for Software Composition Analysis (SCA) and holds a mindshare of 2.3%, down 3.0% compared to last year.
OpenText Static Application Security Testing, on the other hand, focuses on Static Code Analysis, holds 4.3% mindshare, down 9.8% since last year.
Software Composition Analysis (SCA) Mindshare Distribution
ProductMindshare (%)
FOSSA2.3%
Snyk10.9%
Black Duck SCA9.0%
Other77.8%
Software Composition Analysis (SCA)
Static Code Analysis Mindshare Distribution
ProductMindshare (%)
OpenText Static Application Security Testing4.3%
Veracode10.7%
Checkmarx One8.5%
Other76.5%
Static Code Analysis
 

Featured Reviews

reviewer2588340 - PeerSpot reviewer
Senior Software Engineer at a manufacturing company with 10,001+ employees
Dependency management enhanced with update suggestions but lacks precise vulnerability tracking
FOSSA does not show the exact line of code with vulnerabilities, which adds time to the process as we have to locate these manually. Some other tools like Check Point or SonarQube provide exact line numbers for bugs. Also, the process in FOSSA can be quite contradicting and not very straightforward for new users.
DK
Lead Information Security Analyst at a financial services firm with 10,001+ employees
Focuses on detailed scans to find critical vulnerabilities while ensuring minimal false positives
I think Fortify Static Code Analyzer could be improved by updating the number of rule packs according to the latest vulnerabilities we find each year. We have updated to a version that is one less than the current latest version. It would be really helpful to include trending vulnerabilities and how to manage them. While it includes all the OWASP top factors, AI has come into the picture, so those updates should also be considered. I haven't thought much about additional features for improvement since I am using it daily. Most of our work revolves around scanning and providing the results, which sometimes feels like a crunch. However, I believe rule pack updates should be implemented. It feels easy to upgrade to the latest version as well.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"FOSSA provided us with contextualized, easily actionable intelligence that alerted us to compliance issues. I could tell FOSSA exactly what I cared about and they would tell me when something was out of policy. I don't want to hear from the compliance tool unless I have an issue that I need to deal with. That was what was great about FOSSA is that it was basically "Here's my policy and only send me an alert if there's something without a policy." I thought that it was really good at doing that."
"I found FOSSA's out-of-the-box policy engine to be accurate and that it was tuned appropriately to the settings that we were looking for. The policy engine is pretty straightforward... I find it to be very straightforward to make small modifications to, but it's very rare that we have to make modifications to it. It's easy to use. It's a four-category system that handles most cases pretty well."
"The support team has just been amazing, and it helps us to have a great support team from FOSSA. They are there to triage and answer all our questions which come up by using their product."
"The scalability is excellent."
"I am impressed with the tool’s seamless integration and quick results."
"What I really need from FOSSA, and it does a really good job of this, is to flag me when there are particular open source licenses that cause me or our legal department concern. It points out where a particular issue is, where it comes from, and the chain that brought it in, which is the most important part to me."
"The most valuable feature is definitely the ease and speed of integrating into build pipelines, like a Jenkins pipeline or something along those lines. The ease of a new development team coming on board and integrating FOSSA with a new project, or even an existing project, can be done so quickly that it's invaluable and it's easy to ask the developers to use a tool like this. Those developers greatly value the very quick feedback they get on any licensing or security vulnerability issues."
"Having it as a resource to very quickly triage incredibly high volumes of open-source coming into the company through agile development programs was invaluable."
"The most valuable features include its ability to detect vulnerabilities accurately and its integration with our CI/CD pipeline."
"The Software Security Center, which is often overlooked, stands out as the most effective feature."
"We write software, and therefore, the most valuable aspect for us is basically the code analysis part."
"The stability is good; I'm not running into anything that gives me a problem as far as my pipelines are concerned, and for what I use it for, it is sufficient and I get the results that I'm looking for."
"The stability of the solution is pretty good. There are no bugs or glitches."
"We've found the documentation to be very good."
"We are satisfied with this solution."
"Fortify Static Code Analyzer's most valuable features are its ability to provide best practices for fixing code and its examples and capabilities to address security problems in the code. It effectively identifies security vulnerabilities by analyzing the code and offering insights on improving it."
 

Cons

"FOSSA does not show the exact line of code with vulnerabilities, which adds time to the process as we have to locate these manually."
"One thing that can sometimes be difficult with FOSSA is understanding all that it can do. One of the ways that I've been able to unlock some of those more advanced features is through conversations with the absolutely awesome customer success team at FOSSA, but it has been a little bit difficult to find some of that information separately on my own through FAQs and other information channels that FOSSA has. The improvement is less about the product itself and more about empowering FOSSA customers to know and understand how to unlock its full potential."
"I wish there was a way that you could have a more global rollout of it, instead of having to do it in each repository individually. It's possible, that's something that is offered now, or maybe if you were using the CI Jenkins, you'd be able to do that. But with Travis, there wasn't an easy way to do that. At least not that I could find. That was probably the biggest issue."
"For open-source management, FOSSA's out-of-the-box policy engine is easy to use, but the list of licenses is not as complete as we would like it to be. They should add more open-source licenses to the selection."
"The solution provides contextualized, actionable, intelligence that alerts us to compliance issues, but there is still a little bit of work to be done on it. One of the issues that I have raised with FOSSA is that when it identifies an issue that is an error, why is it in error? What detail can they give to me? They've improved, but that still needs some work. They could provide more information that helps me to identify the dependencies and then figure out where they originated from."
"I would like more customized categories because our company is so big. This is doable for them. They are still in the stages of trying to figure this out since we are one of their biggest companies that they support."
"I would like more customized categories because our company is so big."
"On the legal and policy sides, there is some room for improvement. I know that our legal team has raised complaints about having to approve the same dependency multiple times, as opposed to having them it across the entire organization."
"The price can be improved."
"Currently, we get four to five errors on the side of tagging, and it notifies you of every tiny inconsistency."
"The deployment of Fortify Static Code Analyzer needs to be simplified."
"Their licensing is expensive."
"The generation of false positives should be reduced."
"I know the areas that they are trying to improve on. They've been getting feedback for several years. There are two main points. The first thing is keeping current with static code languages. I know it is difficult because code languages pop up all the time or there are new variants, but it is something that Fortify needs to put a better focus on. They need to keep current with their language support. The second thing is a philosophical issue, and I don't know if they'll ever change it. They've done a decent job of putting tools in place to mitigate things, but static code analysis is inherently noisy. If you just take a tool out of the box and run a scan, you're going to get a lot of results back, and not all of those results are interesting or important, which is different for every organization. Currently, we get four to five errors on the side of tagging, and it notifies you of every tiny inconsistency. If the tool sees something that it doesn't know, it flags, which becomes work that has to be done afterward. Clients don't typically like it. There has got to be a way of prioritizing. There are a ton of filter options within Fortify, but the problem is that you've got to go through the crazy noisy scan once before you know which filters you need to put in place to get to the interesting stuff. I keep hearing from their product team that they're working on a way to do container or docker scanning. That's a huge market mover. A lot of people are interested in that right now, and it is relevant. That is definitely something that I'd love to see in the next version or two."
"Not all languages are supported in Fortify."
"The troubleshooting capabilities of this solution could be improved. This would reduce the number of cases that users have to submit."
 

Pricing and Cost Advice

"FOSSA is not cheap, but their offering is top-notch. It is very much a "you get what you pay for" scenario. Regardless of the price, I highly recommend FOSSA."
"FOSSA is a fairly priced product. It is not either cheaper or expensive. The pricing lies somewhere in the middle. The solution is worth the money that we are spending to use it."
"The solution's pricing is good and reasonable because you can literally use a lot of it for free."
"Its price is reasonable as compared to the market. It is competitively priced in comparison to other similar solutions on the market. It is also quite affordable in terms of the value that it delivers as compared to its alternative of hiring a team."
"The solution's cost is a five out of ten."
"There is a licensing fee, and if you bring them to the company and you want them to do the installation and the implementation in the beginning, there is a separate cost. Similarly, if you want consultation or training, there is a separate cost. I see it as suitable only for enterprises. I do not see it suitable for a small business or individual use."
"The setup costs and pricing for Fortify may vary depending on the organization's needs and requirements."
"Although I am not responsible for the budget, Fortify SAST is expensive."
"The price of Fortify Static Code Analyzer could be reduced."
"I rate the pricing of Fortify Static Code Analyzer as a seven out of ten since it is a bit expensive."
"From our standpoint, we are significantly better off with Fortify due to the favorable pricing we secured five years ago."
"The licensing is expensive and is in the 50K range."
"It has a couple of license models. The one that we use most frequently is called their flexible deployment. We use this one because it is flexible and based on the number of code-contributing developers in the organization. It includes almost everything in the Fortify suite for one developer price. It gives access to not just the secure code analyzer (SCA) but also to FSC, the secure code. It gives us accessibility to scan central, which is the decentralized scanning farm. It also gives us access to the software security center, which is the vulnerability management platform."
report
Use our free recommendation engine to learn which Software Composition Analysis (SCA) solutions are best for your needs.
917,433 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
20%
Financial Services Firm
15%
Comms Service Provider
7%
Outsourcing Company
6%
Financial Services Firm
23%
Manufacturing Company
9%
Computer Software Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise1
Large Enterprise8
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise11
 

Questions from the Community

What needs improvement with FOSSA?
FOSSA does not show the exact line of code with vulnerabilities, which adds time to the process as we have to locate these manually. Some other tools like Check Point or SonarQube provide exact lin...
What is your primary use case for FOSSA?
I have worked with FOSSA primarily to manage the dependencies in our projects. For example, if I take a Spring Boot application, FOSSA helps in identifying mismatches or unsupported dependencies th...
What advice do you have for others considering FOSSA?
For those seeking to ensure their application is updated with the latest features, FOSSA can be a beneficial add-on. However, it should not replace your existing primary security solutions such as ...
What is your experience regarding pricing and costs for Fortify Static Code Analyzer?
My experience with the pricing, setup costs, and licensing has been good. We have the scan machines, and we are planning to request more from Micro Focus now. We have calls every month or every oth...
What needs improvement with Fortify Static Code Analyzer?
I think Fortify Static Code Analyzer could be improved by updating the number of rule packs according to the latest vulnerabilities we find each year. We have updated to a version that is one less ...
What is your primary use case for Fortify Static Code Analyzer?
Our main use cases for Fortify Static Code Analyzer typically involve trying to figure out the critical vulnerabilities. It depends on the type of scans that we are doing, whether it is a release s...
 

Also Known As

No data available
Fortify Static Code Analysis SAST
 

Overview

 

Sample Customers

AppDyanmic, Uber, Twitter, Zendesk, Confluent
Information Not Available
Find out what your peers are saying about Snyk, Veracode, Black Duck and others in Software Composition Analysis (SCA). Updated: October 2026.
917,433 professionals have used our research since 2012.