Skip to main content

Supported Security Scanners

Harness STO supports over 40 security scanners, they are categorized as follows:

  • Harness Security Scanners: Scanners developed, maintained, and fully supported by Harness
  • Third-Party Scanners: External commercial or open-source scanners integrated with the Harness platform, not developed or directly maintained by Harness.
    • Open-Source Scanners: A subset of third-party scanners that are open-source.
  • Built-in Scanner Steps: Harness-provided scanner steps using pre-configured open-source scanners. These are ready-to-use within Harness pipelines and do not require additional commercial licenses. For a complete guide, refer to Built-in Scanners.

For a comprehensive list of all scanners, you can view them by Scan Type or Target Type further down this page.

Harness Security Scanners

Harness is expanding its native security scanning capabilities. These scanners are developed and maintained directly by Harness.

  • API DAST (previously Traceable): A Dynamic Application Security Testing scanner for your APIs. This was formerly known as the Traceable API DAST scanner.

Third-Party Scanners

The following are the list of third-party scanners that are categorized by Scan Type and Target Type. The list includes both commercial and open-source scanners.

Here are the list of scanners supported by STO by scan type.

In addition to the listed supported scanners, the Custom Scan step allows the use of various other scanners. For a complete list of supported scanners, refer to Scanners Supported with Custom Scan Step.

Static Application Security Testing - SAST Scanners

Static Application Security Testing (SAST) is a security testing practice that analyzes source code for potential vulnerabilities without executing the application. To configure and run SAST scans, refer Static Application Security Testing documentation.

  1. Bandit - open-source
  2. Black Duck (by Synopsys)
  3. Brakeman - open-source
  4. Checkmarx
  5. Checkmarx One
  6. Coverity - open-source
  7. CodeQL
  8. FOSSA
  9. Mend (formerly known as WhiteSource)
  10. Semgrep - open-source option
  11. Snyk
  12. SonarQube
  13. Veracode
  14. Wiz

In addition to the listed supported scanners, the Custom Scan step allows the use of various other scanners. For a complete list of supported scanners, refer to Scanners Supported with Custom Scan Step.

Secret Detection Scanners

Secret Detection is a security testing practice that scans code repositories for exposed credentials, API keys, tokens, and other sensitive information. To configure and run secret detection scans, refer Secret Detection documentation.

  1. Aqua Trivy - open-source
  2. Checkmarx One
  3. Gitleaks - open-source

In addition to the listed supported scanners, the Custom Scan step allows the use of various other scanners. For a complete list of supported scanners, refer to Scanners Supported with Custom Scan Step.

Software Composition Analysis - SCA Scanners

Software Composition Analysis (SCA) is a security testing practice that identifies vulnerabilities in open-source dependencies and third-party libraries used in your applications. To configure and run SCA scans, refer Software Composition Analysis documentation.

  1. Aqua Trivy - open-source
  2. Checkmarx
  3. Checkmarx One
  4. OSV Scanner - open-source
  5. OWASP Dependency-Check - open-source
  6. Snyk
  7. Veracode
  8. Wiz

In addition to the listed supported scanners, the Custom Scan step allows the use of various other scanners. For a complete list of supported scanners, refer to Scanners Supported with Custom Scan Step.

Container Scanners

Container Scanning is a security testing practice that analyzes your container images for potential vulnerabilities. To configure and run container scans, refer Container Scanning documentation.

  1. Anchore
  2. Aqua Security
  3. Aqua Trivy - open-source
  4. AWS ECR Scan
  5. Black Duck
  6. Checkmarx One
  7. Grype - open-source
  8. Prisma Cloud
  9. Snyk
  10. Sysdig
  11. Wiz

In addition to the listed supported scanners, the Custom Scan step allows the use of various other scanners. For a complete list of supported scanners, refer to Scanners Supported with Custom Scan Step.

Dynamic Application Security Testing - DAST Scanners

Dynamic Application Security Testing (DAST) is a security testing practice that identifies vulnerabilities in running applications by simulating real-world attacks. To configure and run DAST scans, refer Dynamic Application Security Testing documentation.

  1. Burp Suite Enterprise Edition
  2. Checkmarx One
  3. Nikto - open-source
  4. Nmap - open-source
  5. Traceable
  6. Veracode
  7. Zap - open-source

In addition to the listed supported scanners, the Custom Scan step allows the use of various other scanners. For a complete list of supported scanners, refer to Scanners Supported with Custom Scan Step.

Infrastructure as Code - IaC Scanners

Infrastructure as Code (IaC) scanning is a security testing practice that analyzes IaC configurations to identify misconfigurations, security vulnerabilities, and compliance issues before deployment. To configure and run IaC scans, refer Infrastructure as Code documentation.

  1. Checkmarx One
  2. Checkov - open-source
  3. Snyk
  4. Wiz

In addition to the listed supported scanners, the Custom Scan step allows the use of various other scanners. For a complete list of supported scanners, refer to Scanners Supported with Custom Scan Step.


Scanners supported with Custom Scan step

The following scanners do not have a dedicated step in STO, but they can be used through the Custom Scan step.

  1. Clair
  2. Data Theorem
  3. Docker Content Trust
  4. Fortify Static Code Analyzer
  5. Fortify on Demand
  6. HCL AppScan
  7. Metasploit - open-source
  8. Nessus
  9. Nexus
  10. OpenVAS - open-source
  11. Qualys Web Application Scanning
  12. Qwiet AI (formerly ShiftLeft)
  13. Reapsaw - open-source
  14. ScoutSuite - open-source
  15. Tenable
  16. Veracode
  17. JFrog Xray

If you are looking for scanners that are not available as steps or are not supported through the Custom Scan step, you can use the Custom Ingest step to import scan results into STO. For detailed instructions, see Ingest results from unsupported scanners

Supported ingestion formats

Here are the scanners that support ingestion scan mode in STO and the data format each scanner expects for ingestion into STO.

info

Static Analysis Results Interchange Format (SARIF) is an open JSON format supported by many scan tools, especially tools available as GitHub Actions. Harness STO can ingest SARIF 2.1.0 data from any tool that supports this format.

Harness recommends that you publish and ingest using the scanner-specific JSON format when available, because it tends to include more useful information.

  • Anchore Enterprise — JSON
  • Aqua Security — JSON
  • Aqua Trivy — JSON (recommended), SARIF
  • AWS ECR — JSON
  • AWS Security Hub — JSON
  • Bandit — JSON (recommended), SARIF
  • Black Duck Hub — JSON
  • Brakeman — JSON
  • Burp — XML
  • Traceable — JSON
  • Checkmarx — XML, SARIF
  • CheckmarxOne — JSON
  • CodeQL — SARIF
  • Coverity — XML
  • Data Theorem — JSON
  • Docker Content Trust — JSON
  • Fortify — JSON
  • Fortify on Demand — JSON
  • Fossa — JSON
  • Gitleaks — JSON (recommended), SARIF
  • HQL AppScan — XML
  • Grype — JSON
  • Mend (formerly Whitesource) — JSON
  • Nessus — XML
  • Nexus — JSON
  • Nikto — XML
  • Nmap — XML
  • OpenVAS — JSON
  • OWASP Dependency Check — JSON
  • Prisma Cloud — JSON
  • Prowler — JSON
  • Qualys — XML
  • Qwiet — JSON
  • Reapsaw — JSON
  • Semgrep — SARIF
  • Snyk — JSON (recommended), SARIF
  • SonarQube — JSON
  • Sysdig — JSON
  • Tenable — JSON
  • Veracode — XML
  • JFrog Xray — JSON
  • Wiz - JSON (recommended), SARIF
  • Zed Attack Proxy (ZAP) — JSON
  • Checkov - JSON, SARIF