New tool to help developers find and fix security weaknesses in proprietary code and open source dependencies

code-unsplash
Listen to this article

What To Know

  • 18 it will release a major update to the Polaris Software Integrity Platform™ to extend its static application security testing (SAST) and software composition analysis (SCA) capabilities to the developer’s desktop through the native integration of the Code Sight™ IDE plugin.
  • Building on the Code Sight SAST capabilities first introduced in 2019, this release introduces the ability to analyse declared and transitive open source dependencies, flagging components with known security issues alongside SAST findings in the IDE.

Editor’s Brief: When it comes to open source software (OSS), many developers know that the abundance of such code can dramatically shorten their developmental curve. Many enterprises embed OSS into their applications for a faster go-to-market. But what are the pitfalls? At the same time, proprietary code can be ridden with vulnerabilities, as code complexity increases. Leading software integrity vendor Synopsys introduces a first AST solution to help developers analyze both open source and proprietary code without leaving their IDE. The vendor’s new release is found below.

SINGAPORE Synopsys, Inc. (Nasdaq: SNPS) announced that on Feb. 18 it will release a major update to the Polaris Software Integrity Platformto extend its static application security testing (SAST) and software composition analysis (SCA) capabilities to the developer’s desktop through the native integration of the Code Sight™ IDE plugin. These capabilities, the first of their kind, will enable developers to proactively find and fix both security weaknesses in proprietary code and known vulnerabilities in open source dependencies simultaneously, without leaving their interactive development environment (IDE).

“In modern development environments, security testing needs to integrate seamlessly into the developer’s workflow, but it also needs to cover both proprietary and third-party code,” said Simon King, vice president of solutions at the Synopsys Software Integrity Group. “By providing real-time SAST and now SCA results together in the IDE, Synopsys enables developers to detect security defects in both their own code and the open source components they leverage – as they build their applications. Developers can fix problems in real time, avoiding the risks and loss of productivity when issues are allowed to go undetected for days, weeks, or even months after they’ve moved on to other tasks. With this release, the native integration of the Code Sight IDE plugin enables developers to build secure, high-quality software faster.”

More about the new Code Sight IDE plugin:

  • Building on the Code Sight SAST capabilities first introduced in 2019, this release introduces the ability to analyse declared and transitive open source dependencies, flagging components with known security issues alongside SAST findings in the IDE.
  • With the new SCA capabilities, developers can review known vulnerabilities of flagged components to verify the risk and determine remediation options, all without leaving the IDE.
  • The Code Sight plugin provides vulnerability information from Black Duck Security Advisories (BDSAs), researched by Synopsys, as well as public CVE records from the National Vulnerability Database (NVD).
  • BDSAs provide developers with more timely, accurate, and thorough risk and remediation information than is available in the NVD, helping them find and fix vulnerabilities faster and more effectively than other solutions.
  • The Code Sight plugin also helps developers quickly identify and select the best fix for vulnerabilities by providing detailed remediation guidance, directing them to more secure component versions. Developers can then implement fixes at once, without interrupting their workflow or leaving the IDE.
  • In addition to vulnerability information, the Code Sight plugin provides other information developers can use to optimise component selection, including open source license risks and potential security and license compliance violations of the organisation’s predefined open source policies.

To learn more, read the blog post.

###