On this page
- Comparison to GitLab
- Software Composition Analysis (SCA)
Anchore is a company that offers security scanning for Docker containers, Docker container registries, and Kubernetes clusters. They offer an Open Source, Enterprise, and Federal version of their products. They leverage public vulnerability feeds to scan customers' environments for vulnerabilities and alert them so end users can take action.
Comparison to GitLab
Although Anchore does software composition analysis well, they do very little beyond that narrow scope. Comparatively, GitLab provides a superior experience for ALL types of security scanning - not only container scanning, but also SAST, DAST, Fuzz Testing, and others. This approach maximizes the kinds of vulnerabilities that can be detected while only incurring the maintenance costs of a single tool.
Anchore leverages publicly-available vulnerability feeds to identify their vulnerabilities. GitLab does this as well; however, GitLab is also a CVE Numbering Authority, which means that security researchers can work directly with GitLab on any security issues they find. GitLab's commitment to leveraging the latest vulnerability feeds is also publicly visible to customers at advisories.gitlab.com.
Finally, GitLab provides a superior experience for developers in viewing, correcting, and responding to vulnerabilities. Because GitLab’s scanning capabilities are integrated with the rest of GitLab, the vulnerabilities appear as part of the developer’s regular workflow, inline within their MRs. This visibility is critical to be able to effectively shift security left. With Anchore, developers will need to look at an external tool to see the details about their vulnerabilities, making them much less likely to correct them before the code goes to production.
Anchore can be complementary to GitLab if users have already bought both. GitLab supports integration with tools that customers are already using and plays well with others.
Software Composition Analysis (SCA)
Strengths and Weaknesses
|Strengths|| • Integrated security as part of DevOps workflow for all developers
• High-quality container security by leveraging all the latest feeds for vulnerabilities
• Supports on-premise deployments including disconnected, offline, or air-gapped environments
• Security leadership by being a CVE Numbering Authority and a recognized in the Gartner AST magic quadrant
• End-to-end DevOps offering from SCM to CI to CD to Security and more
| • Single-focused, purpose built container scanning product
• Can work with many CI/CD providers (e.g. GitHub, GitLab, BitBucket)
|Weaknesses||• Pricing requires buying all of GitLab Ultimate, not just Container Scanning|| • Narrow product offering only focused on one type of scanning
• It is difficult to justify the cost of maintaining an entire security tool when the tool addresses such limited scope (SCA only)
|Secrets and Passwords||✅||✅|
|Open Source & Third Party Package Audit||✅||✅|
|Security results shown to developers as part of their daily work||✅|
GitLab allows you to perform Secret Detection in CI/CD pipelines; checking for unintentionally committed secrets and credentials. Results are then shown in the Merge Request and in the Pipeline view. This feature is available as part of Auto DevOps to provide security-by-default.
GitLab automatically detects well known security bugs in the libraries that are included by the application, protecting your application from vulnerabilities that affect dependencies that are used dynamically. Results are then shown in the Merge Request and in the Pipeline view. This feature is available as part of Auto DevOps to provide security-by-default.
When building a Docker image for your application, GitLab can run a security scan to ensure it does not have any known vulnerability in the environment where your code is shipped. Results are then shown in the Merge Request and in the Pipeline view. This feature is available as part of Auto DevOps to provide security-by-default.
If you feel there are inaccurate statements in this comparison or a tool missing, please edit this page or propose edits by opening an issue. You can also send an email to firstname.lastname@example.org with your suggested edits if you're unable to open an issue or edit this page.
We strive for technical accuracy and will review and update this post for inaccuracies as quickly as possible.