Posted by Synopsys Editorial Team on January 4, 2018
In addition to ensuring software quality, development teams are under increasing pressure to address software security concerns. The high-profile data breaches that continuously arise are raising awareness of security issues. Because of this, customers, stakeholders, and boards of directors are asking questions of development teams that they never have before. Questions like:
Developers are incentivized to move quickly. When security or QA teams require code to be rewritten after it has been checked in or compiled, releases can be delayed. Work that has already been completed may need to be unraveled and restarted. Worse, if defects are discovered after code has shipped, implementing fixes can be unreliable and costly.
In many firms, development teams also bear more direct responsibility for finding and resolving problems. At the same time, many developers have limited experience with software security. Development leaders might struggle to create a consistent process that accounts for varying levels of expertise.
According to data gathered from the 2017 Synopsys Security and Quality Survey, 39% of security- and development-focused experts claim that the most difficult challenge to overcome when ensuring software is free of security defects is that their developers don’t have the knowledge or expertise to ensure the code they create or compile is secure.
Additionally, the development cycle isn’t as clear-cut as it once was. Many organizations have moved away from the Waterfall approach. They now have distinct stages for development versus testing. Additionally, many firms are implementing a more iterative, continuous process. Tech stacks also include a wide range of frameworks and languages, including open source code, which are compiled together.
Automation is key when it comes to helping developers balance the competing pressures of speed and security without requiring deep security domain expertise. Tools that scan for bugs in code can identify common quality and security issues. They can also give developers a chance to remedy them before the code is passed along.
Testing tools that provide results with high fidelity can be a developer’s best friend. They reduce a mountain of potential risks to a manageable list. Such tools can point the developers to fixes that can affect multiple instances of shared code at once. Additionally, in the context of the developer workflow, different types of security testing tools can be applied in different ways to identify different types of potential issues.
Static application security testing (SAST) tools such as Synopsys Static Analysis (Coverity) examine an application’s code or binary without executing the application. This solution provides deep full-path coverage accuracy and can support thousands of developers. It can also quickly analyze large projects exceeding 100 million lines of code and integrate to key development tools and CI/CD systems.
Get the latest Software Integrity news, thought leadership, and more.