Table of Contents
- Market Categories and Deployment Types
- Key Criteria Comparison
- GigaOm Radar
- Vendor Insights
- Analyst’s Take
- About Shea Stewart
- About GigaOm
As we learned in the associated GigaOm report, “Key Criteria for Evaluating Developer Security Tools,” the most cost-effective method for reducing risk in software development is to identify and fix issues as close to the developer as possible. As the number of software developers continues to vastly outnumber the number of security professionals allocated to any software project, organizations need to invest in security tooling and automation that can help software developers consider and mitigate security risks in a proactive manner.
Add to this situation an appreciation for how the role of the developer has changed vastly over the last few years: Developers aren’t just responsible for software components; they can write infrastructure components, security controls, automations/integrations, and so forth. This has blended the worlds of the traditional software developers and the infrastructure and operations teams responsible for the environments that software components are deployed to. A much wider range of job titles can be incorporated into the developer role now, which requires the same security tooling and process oversight as does traditional software development.
As we consider how to evaluate vendors for developer security tools, we need to take these points into account:
- All vendors involved in improving application security can contribute to an organization’s overall enhanced security posture.
- “Shift-left” mindsets do not imply that the work of reducing risk is simply shifted to the developer, but rather that adding a focus on security early in the process will reduce risk and rework as software moves through the delivery pipeline.
- Security throughout the entire software development lifecycle (SDLC) is key for any organization that is focused on reducing risk.
In this report we have identified a number of vendors that address the specific need to catch and remediate security issues earlier in the software development lifecycle, which we articulate in the report as table stakes, key criteria, and evaluation metrics. While we review 12 vendor solutions here, we ruled out many more, including several offering capabilities focused on runtime protection, which merit review in upcoming GigaOm Key Criteria and Radar Reports.
How to Read this Report
This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding consider reviewing the following reports:
Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.
GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.
Solution Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.