Try our new research platform with insights from 80,000+ expert users

Black Duck vs Fortify Static Code Analyzer comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Black Duck
Average Rating
7.6
Reviews Sentiment
7.2
Number of Reviews
20
Ranking in other categories
Software Composition Analysis (SCA) (1st)
Fortify Static Code Analyzer
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
16
Ranking in other categories
Static Code Analysis (3rd)
 

Mindshare comparison

While both are Security Software solutions, they serve different purposes. Black Duck is designed for Software Composition Analysis (SCA) and holds a mindshare of 22.9%, down 23.6% compared to last year.
Fortify Static Code Analyzer, on the other hand, focuses on Static Code Analysis, holds 24.1% mindshare, up 19.6% since last year.
Software Composition Analysis (SCA)
Static Code Analysis
 

Featured Reviews

Saravanan_Radhakrishnan - PeerSpot reviewer
Enables applications to be secure, but it must provide more open APIs
The product enables other applications to be secure. We use it to onboard 400 to 500 applications into the DevOps platform, protect them, and have a secure environment. The tool integrates well with different technologies, application stacks, and databases. The APIs are available. We can read the blogs in the community for open-source compliance and security. The community feeds are important. Black Duck is a leader in Gartner. It is a reliable solution.
Vishal Dhamke - PeerSpot reviewer
An expansive platform with comprehensive security rules and patterns to identify vulnerabilities
Setting up Fortify Static Application Security Testing (SAST) involves several steps to ensure that the tool is correctly configured and integrated into your development workflow, for example: installation, license activation, user access and permissions, integration with the development environment, project configuration, custom rules and policies, etc. The initial setup is very easy. I have used the enterprise version and a standalone version. The enterprise version definitely takes an ample amount of time to deploy because it needs to have a server, other logistics, and a proper RBAC in place. The enterprise version would take an ample amount of time, but the standard version is just a few clicks. A team of four to five people is required for the maintenance, and frequent updates are required to keep all the signatures up to date. I would rate the setup a nine out of ten.

Quotes from Members

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

Pros

"The UI is the solution's most valuable feature since it allows for easy pipeline integration."
"The stability is okay."
"The software composition analysis is most effective for security risk management."
"The automated code scanning feature and Black Duck's integration with our development tools have enhanced our software compliance process and overall audit readiness."
"I like the fact that the product auto analyzes components."
"The solution is very good at scanning and evaluating open source software."
"We didn't have a central inventory to quickly identify issues or determine how many products were affected. Now under Black Duck, it's all consolidated. You search for a component and immediately see which products use it."
"The cloud option of the product is always available and a positive aspect of the solution."
"The most valuable features include its ability to detect vulnerabilities accurately and its integration with our CI/CD pipeline."
"The integration Subset core integration, using Jenkins is one of the good features."
"The reference provided for each issue is extremely helpful."
"Integrating the Fortify Static Code Analyzer into our software development lifecycle was straightforward. It highlights important information beyond just syntax errors. It identifies issues like password credentials and access keys embedded in the code."
"We've found the documentation to be very good."
"Fortify Static Code Analyzer tells us if there are any security leaks or not. If there are, then it's notifying us and does not allow us to pass the DevOps pipeline. If it is finds everything's perfect, as per our given guidelines, then it is allowing us to go ahead and start it, and we are able to deploy it."
"We write software, and therefore, the most valuable aspect for us is basically the code analysis part."
"I like Fortify Software Security Center or Fortify SSC. This tool is installed on each developer's machine, but Fortify Software Security Center combines everything. We can meet there as security professionals and developers. The developers scan their code and publish the results there. We can then look at them from a security perspective and see whether they fixed the issues. We can agree on whether something is a false positive and make decisions."
 

Cons

"It can be cumbersome to use or invalidate open source software because there is a hold time to check requirements or common regulations to ensure compliance."
"We're not too sure about the extension of the firewall. It never shows up in the Hub."
"There are areas for improvement such as false positives and the scanning of containers."
"The tool's documentation and support are areas of concern where improvements are required."
"It is a cloud-only solution. In many cases, companies like to evaluate the software, but they're very reluctant to give you the software. It would be great if they could offer an on-prem component that could be used to scan the code and then upload the discovery results to the cloud and get all the information from there, but there is no such possibility. You have to upload the code to the Black Duck cloud system. Of course, they have a strong legal department, and they offer some configuration, but it is never enough. You have to give the code, which is a drawback. In modern designs like Snyk or FOSSA, you don't need to give the code. It requires more native integration with Coverity because they go together technically. You need both Coverity and Black Duck Hub. It would be really helpful for companies working in this space to get a combined offer from the same company. They should provide an option to buy Coverity for an additional fee. Coverity combined with Black Duck Hub will provide a one-step analysis to get everything you need and a unified report. It would be really great to be able to connect Black Duck Hub with Coverity unified reports."
"The initial setup could be simplified. It was somewhat complex."
"The scanner client is limited by the size of software it can handle."
"Black Duck can improve the time it takes for a scan. Most of the time it's not ideal when integrated with the live DevSecOps pipeline. We have to create a separate job to scan the library because it takes a couple of hours to scan all those libraries. The scanning could be faster."
"The product shows false positives for Python applications."
"False positives need improvement in the future. Fortify's vulnerability remediation guidance helps improve code security, but I think they need to improve the focus of the solution, as it still contains many bugs and needs a thorough review."
"The troubleshooting capabilities of this solution could be improved. This would reduce the number of cases that users have to submit."
"Their licensing is expensive."
"The generation of false positives should be reduced."
"The pricing is a bit high."
"It comes with a hefty licensing fee."
"Fortify Static Code Analyzer is a good solution, but sometimes we receive false positives. If they could reduce the number of false positives it would be good."
 

Pricing and Cost Advice

"Black Duck is more suitable if you require a lot of licensing compliance. For smaller organizations, WhiteSource is better because its pricing policies are not really suitable for huge organizations."
"The price charged by Black Duck is exorbitant."
"The price is quite high because the behavior of the software during the scan is similar to competing products."
"The pricing is a little high."
"It is expensive."
"I rate the product's price one on a scale of one to ten, where one is a high price, and ten is a low price."
"The price is low. It's not an expensive solution."
"Depending on the use case, the cost could range from $10,000 USD to $70,000 USD."
"Although I am not responsible for the budget, Fortify SAST is expensive."
"From our standpoint, we are significantly better off with Fortify due to the favorable pricing we secured five years ago."
"The setup costs and pricing for Fortify may vary depending on the organization's needs and requirements."
"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 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."
"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.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Manufacturing Company
17%
Computer Software Company
14%
Healthcare Company
4%
Financial Services Firm
30%
Computer Software Company
13%
Manufacturing Company
11%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

How does WhiteSource compare with Black Duck?
We researched Black Duck but ultimately chose WhiteSource when looking for an application security tool. WhiteSource is a software solution that enables agile open source security and license compl...
What do you like most about Black Duck?
The cloud option of the product is always available and a positive aspect of the solution.
What is your experience regarding pricing and costs for Black Duck?
The price charged by Black Duck is exorbitant. For the features provided by the product, I would not want to pay a high price. There are many other products in the market that offer better features...
What do you like most about Fortify Static Code Analyzer?
Integrating the Fortify Static Code Analyzer into our software development lifecycle was straightforward. It highlights important information beyond just syntax errors. It identifies issues like pa...
What is your experience regarding pricing and costs for Fortify Static Code Analyzer?
I rate the pricing of Fortify Static Code Analyzer as a seven out of ten since it is a bit expensive.
What needs improvement with Fortify Static Code Analyzer?
False positives need improvement in the future. Fortify's vulnerability remediation guidance helps improve code security, but I think they need to improve the focus of the solution, as it still Con...
 

Also Known As

Blackduck Hub, Black Duck Protex, Black Duck Security Checker
Fortify Static Code Analysis SAST
 

Overview

 

Sample Customers

Samsung, Siemens, ScienceLogic, BryterCX, Dynatrace
Information Not Available
Find out what your peers are saying about Black Duck, Veracode, Snyk and others in Software Composition Analysis (SCA). Updated: December 2024.
824,053 professionals have used our research since 2012.