We just raised a $30M Series A: Read our story

Top 8 Application Security Testing (AST) Tools

VeracodeCheckmarxPortSwigger Burp Suite ProfessionalMicro Focus Fortify on DemandGitLabOWASP ZapContrast Security AssessAcunetix by Invicti
  1. leader badge
    The visibility into application status helps reduce risk exposure for our software. Today, any findings provided by the DAST are reviewed by the developers and we have internal processes in place to correct those findings before there can be a release. So it absolutely does prevent us from releasing weak code.
  2. leader badge
    It can integrate very well with DAST solutions. So both of them are combined into an integrated solution for customers running application security.
  3. Find out what your peers are saying about Veracode, Checkmarx, PortSwigger and others in Application Security Testing (AST). Updated: October 2021.
    542,721 professionals have used our research since 2012.
  4. leader badge
    We use the solution for vulnerability assessment in respect of the application and the sites. The automated scan is what I find most useful because a lot of customers will need it. Not every domain will be looking for complete security, they just need a stamp on the security key. For these kinds of customers, the scan works really well.
  5. leader badge
    Once we have our project created with our application pipeline connected to the test scanning, it only takes two minutes. The report explaining what needs to be modified related to security and vulnerabilities in our code is very helpful. We are able to do static and dynamic code scanning.
  6. We like that we can have an all-encompassing product and don't have to implement different solutions. GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable.
  7. It has evolved over the years and recently in the last year they have added, HUD (Heads Up Display).They offer free access to some other tools.
  8. report
    Use our free recommendation engine to learn which Application Security Testing (AST) solutions are best for your needs.
    542,721 professionals have used our research since 2012.
  9. The solution is very accurate in identifying vulnerabilities. In cases where we are performing application assessment using Contrast Assess, and also using legacy application security testing tools, Contrast successfully identifies the same vulnerabilities that the other tools have identified but it also identifies significantly more. In addition, it has visibility into application components that other testing methodologies are unaware of.
  10. There is a lot of documentation on their website which makes setting it up and using it quite simple.Overall, it's a very good tool and a very good engine.

Advice From The Community

Read answers to top Application Security Testing (AST) questions. 542,721 professionals have gotten help from our community of experts.
Rony_Sklar
Hi, Many companies wonder whether SAST or DAST is better for application security testing.  What are the relative benefits of each methodology? Is it possible to make use of both?
author avatarDan Doggendorf
User

SAST and  DAST are not mutually exclusive and should be used in conjunction with each other.  One should be used by the developers to ensure security is being addressed as they are writing the code.  The other is used for evaluating existing applications already in production to ensure they are not susceptible to any new vulnerabilities that have been discovered.  


The real question is which should have a higher priority when it comes to introducing the concepts into your application security model.  Unfortunately, there is no single answer to which comes first.  It all depends on your organizations culture, business model, and your relationships with the various impacted groups.

author avatarThomas Ryan
User

The easiest way to remember the role of each:


SCA & SAST = Am I Vulnerable
DAST & IAST = Am I Exploitable (In some cases together, they compliment SAST)
RASP & WAF = Can I Protect Myself  (Fixing the code is the primary option)

author avatarOscar Van Der Meer
Vendor

For application security you ideally need SAST, SCA and DAST. You need all three as they essentially measure different things:


SAST identifies bad coding practices that potentially could be exploited


SCA identifies known vulnerabilities in the libraries and components you are using and this is the main attack vector on applications.


DAST identifies some of the weaknesses that SAST and SCA identified, but also identifies weaknesses in the configuration. You might have the perfect application code with zero vulnerabilities, but if it is misconfigured, for instance using a default password, it still can be breached.


If you have to choose, look at SCA and then DATS first as that gives you the best bang for your buck from a risk reduction perspective

author avatarreviewer1572348 (Chief Architect at a computer software company with 10,001+ employees)
Real User

Both SAST and DAST are complementary to each other.  The best approach is to include both SAST and DAST.


SAST: Inspects underlying source code, requires understanding of source design, Is  utilized early in the development cycle and the average cost to remediate issues is low


DAST: Requires the application running, performs hacker-like (black box) testing, 


Utilized much later in the development cycle and the average cost to remediate issues is higher


If we look at OWASP Top 10 2021 changes, SAST or DAST will not cover all of them individually. In addition, we also need SCA to be done to look at open source vulnerabilities.

author avatarCurtis Yanko (Shiftleft)
Vendor

It’s a false choice of a question but DAST exist because folks don’t trust their SAST tool. DAST is good about true positives but bad about false negatives. SAST just has a reputation for false positives but a new generation of SAST tools do a much better job.

author avatarRussell Webster
Real User

Both. They are not in competition with each other.
SAST is used for analyzing your written code for practices and patterns that are risky or vulnerable.
DAST is used @ runtime for analyzing the app for vulnerabilities as shown in other ways on the runtime memory stack, etc.
Both provide different value.

Look into RASP vs DAST vs IAST as well.

Rony_Sklar
What are the different types of tools that should be used together in DevSecOps? What are the specific tools that you like to use when working on your DevSecOps pipeline?  What is essential, and what is a nice-to-have? 
author avatarThomas Ryan
User

Everything in technology focuses on People, Process & Technology. What binds these together is business requirements and understanding the needs of each Line Of Business. Often each Line of Business requires completely different requirements, but what tools help you meet that unified vision and executive dashboard reporting to measure your KPIs.



  1. Code Repos – GitHub, GitLab

  2. Build Servers – Azure DevOps, Jenkins, Bamboo, TeamCIty

  3. Code Quality - SonarQube

  4. Software Composition Analysis (SCA) – Sonatype (Fortify Integration), Snyk, & BlackDuck

  5. Static Analysis (SAST) – Fortify On Premise, Fortify OnDemand (or Hybrid) CheckMarx (Fills the APEX, Perl, Groovy, etc.. gap that Fortify doesn’t cover)

  6. Infrastructure As Code (IaaC) – Aqua Security

  7. IAST – Not widely adapted due to agent limitations.

  8. DAST – WebInspect

    1. ScanCentral provides the most automation and scalability

    2. Highly Flexible API for Automation



  9. Metric Reporting – SaltMiner (Saltworks Security), Fortify SSC, Fortify OnDemand

  10. IDE (Eclipse, Visual Studio, JetBrains) – Fortify

  11. Continuous Monitoring - BitDiscovery


Why so much Fortify? It has been around 17 years, while it is old it is constantly evolving. It is the only Hybrid (Cloud & On-Premise Solution), it provides the flexibility needed for most customers. There is a reason why over 50% of Cigital (Synopsys) business is managing Fortify and not Synopsys tool suite. Deloitte, Accenture, IBM & Saltworks makes a lot of money managing Fortify. One thing you won’t hear from Gartner, Fortify SAST & DAST surpasses their competitors’ revenue by over 70%.

author avatarreviewer1572348 (Chief Architect at a computer software company with 10,001+ employees)
Real User

I believe we need to cover the SDLC from start to end as much as possible while ensuring that this does not mean too many dashboards and also keeping the cost of development in mind.


1. IDE Checks: This is the 1st step in shift left approach. Many open source tools integrate easily with IDE (VSC, Eclipse) etc and allow developers to do a check even before they commit code on local branch. We have leveraged SonarLint (https://www.sonarlint.org/) which covers a vast spectrum of programming languages and IDEs.


2. SAST: Many open source tools available in this space which do a check around security vulnerability, security hotpots etc. We use SonarQube.


3. SCA: Check against open source security vulnerabilities and license compliance is very important. WhiteSource is what we use here.


4. IaaC scan: We need tools to manage and analyze infrastructure as code (IaC) scan results across platforms and be able to resolve the issues.


5. Monitoring: Once application is deployed into production, we need tools to monitor it live and be able to check for vulnerabilities and other issues which happen when 100's of users are using the application from across the globe.


There are other areas like DAST, IAST which become important depending on size, complexity and business needs.

author avatarRama Susarla
Real User

It depends on the budget, business and technology portfolio of the enterprise. 


If you predominantly web-based and service architecture-oriented technology portfolio, Veracode set of tools (Green-light, Veracode SAST, Veracode DAST) is a good option. Veracode is good if you have enterprise-level DevSecOps transformation. But Veracode may not work well for legacy systems. 


I have also used Microfocus Fortify effectively. Just on SCA, universally used Sonarqube with standard plugins is I prefer as it is easy to use. All these tools are very used to integrate into DevSecOps Application Pipeline.

author avatarJeremy Vaughan
User

Depends on budget and the larger approach to security, compliance, and risk. There are many solutions and approaches out there but many limit the ability to scale DevSecOps beyond an experiment and justify to business leaders. Standard response: SCA, SAST, DAST, IAST. Many of these tools are disconnected and some slow down performance quit a bit, especially your traditional household names. What are your goals and what are your constraints to developing a program?

author avatarSteve Arone
User

The detailed answers below are a good summary.  How are teams pulling all these tools together and orchestrating in terms of agile stories and feedback loops?  Azure DevOps, JIRA, ServiceNow, Other?

author avatarGiorgio Riva
User

Hi we think that is essential a tool for applying static analysis technologies for Code Quality and Security

Charles Race
I'm choosing an Application Security Testing platform. My use cases are as follows: SAST DAST Component Scanning Vulnerability auditing  Mitigation What product/solution would you recommend and why? 
author avatarThomas Ryan
User

The first thing you'd want to do is


1.Look at your application inventory to determine the language and framework coverage.


2. The following would be what has the developer integrations with my current and future state CI/CD toolset, Developer IDE's


3. Do I have the security team to support it? Helps determine vendor and approach. I say Fortify as they are the only Hybrid (Cloud and OnPremise) approach. 


4. Does this need to be Cloud or OnPremise?


My most successful customers have used the following:


  • SAST - Hybrid of Fortify on-premise and Fortify on Demand, if support is needed for Perl or Groovy, buy some CheckMarx to cover that gap and Correlate findings with Saltworks SaltMiner.

  • DAST - WebInspect/ScanCentral & Fortify on Demand

  • Component Scanning - The most successful deployments have been with SonaType due to the Fortify integration. Blackduck, WhiteSource, and Snyk also manage plugins to Fortify SSC. If there is no budget, use OWASP Dependency Track to build your use case for a more robust Composition Analysis tool.

  • Vulnerability auditing - Done within Fortify SSC or Fortify OnDemand

  • Mitigation - Your Team, but if consulting is needed I would recommend Saltworks Security, Deloitte, Accenture & Cigital which have a reputation for managing Fortify programs.


Ping me if you need further guidance.


author avatarRaghavendra Rao PV
User

I suggest go for a Secure SDLC approach by integrating security at each level of the development life cycle. If you are constrained to select just one from the above then start with DAST. As it helps simulate realtime attacks on your production application and thus helps you address the most glaring issues.

author avatarSivaKrishna
Real User

The best application security testing platforms include GitHub, GitLab, HCL AppScan, Netsparker, Acunetix Vulnerability Scanner, Pentest-Tools.com, Detectify Deep Scan, Appknox, Checkmarx, and Micro Focus Fortify On Demand. 

author avatarVishalDhamke
Real User

SAST - Veracode, goes well with integration


DAST - Either Microfocus Webinspect or Burp Suite Professional or OWASP ZAP (Open Source)


Component Scanning - Blackduck or Sonatype Nexus Platform or Whitesource Bolt 


Vulnerability Auditing - Nessus & CIS - CAT ( Assessor Pro) or Qualys


Mitigation -  Team effort, for Security Orchestration  - Threadfix or ZeroNorth

author avatarW_K
User

Kiuwan - scan for 3rd party libs


SonarQube - CD\CI integration with low price

author avatarCuneyt KALPAKOGLU Phd.
Real User

I would like you to buy CHECKMARX as a SAST TOOL and have a look to KONDUKTO which embeds security tests into DevOps pipelines in an automated fashion using both open source and commercial security tools.                                  Vulnerabilities coming from different sources, be it from penetration tests, bug bounty programs or automated tools can be managed in a single platform to provide a unified view. With its unique process automation and CI/CD integration capabilities, Kondukto helps to scale AppSec effort and paves the way for DevSecOps.                                      My advice to pay attention the Visibility into vulnerabilities in native environments leads to improved security awareness among developers.

✔ Custom-tailored training programs based on the vulnerabilities created by each developer and team increase the ROI of training.

✔ Remediation database allows developers to benefit from the know-how accumulated in the company and fix vulnerabilities faster.

author avatarRogerio Goncalves
User

Hi my name is Rogerio from Xmart Solutions Brazil. we are an independent consultancy that representing several Ast solutions. Some factors are important to be evaluated such as: 


how many sast applications (static analysis) and how often will you do the analysis? how many analyzes (urls) will you do dynamically?
what are your sprints? Do you have internal development or with third parties? 


which languages ​​from your legacy? how will you implement with integrations? what tools?


would you like to have everything automated?


these are just a few questions for a decision.


I hope I contributed


Find out what your peers are saying about Veracode, Checkmarx, PortSwigger and others in Application Security Testing (AST). Updated: October 2021.
542,721 professionals have used our research since 2012.