News

ShiftLeft focuses on developer productiveness with subsequent era static evaluation resolution

shiftleft-focuses-on-developer-productiveness-with-subsequent-era-static-evaluation-resolution

ShiftLeft has introduced an up to date model of its NextGen Static Evaluation resolution. The discharge options new workflows designed to assist builders enhance safety and improve productiveness.

In response to the corporate, developer productiveness suffers when safety isn’t automated or built-in into the life cycle. A current ShiftLeft survey discovered 96% of builders felt a disconnect between improvement and safety workflows, which impacted productiveness. Moreover, respondents revealed developer-friendly safety workflows had been the next precedence than defending apps in manufacturing environments.

RELATED CONTENT: Builders shopping for in to safety duties

“The one option to ship safety on the tempo of contemporary SDLCs is to create a tradition of particular person developer accountability for the safety of the code they write. Nevertheless, this calls for new AppSec options purpose-built for in the present day’s necessities,” mentioned Manish Gupta, CEO of ShiftLeft. “Based mostly on our new survey, it’s clear builders really feel advert hoc safety processes and the instruments they’ve accessible to them in the present day aren’t serving to. We’ve at all times put productiveness and safety on the basis of our platform, and our prospects’ outcomes show that the brand new workflow is considerably bettering their safety postures whereas growing developer productiveness.”

The newest launch options:

The power to automate code evaluation with each pull/merge request
Rapid safety suggestions
Means for builders to repair vulnerabilities inside their improvement setting
Means to app safety groups to write down security-focused construct guidelines
Greatest practices via safety insights
Limitless concurrent scans to eradicate bottlenecks
Means to scan supply code inside the group
Self-service on-boarding
Customizable workflows

“This developer-centric strategy to code evaluation enormously will increase safety and productiveness by delivering the best vulnerability to the best developer on the proper time. Imply time to remediation (MTTR) is diminished as a result of vulnerabilities get fastened whereas the code continues to be recent within the builders’ minds, and susceptible code doesn’t turn into deeply interconnected as a result of safety construct guidelines forestall it from coming into the grasp department,” the corporate wrote in its announcement.   

0 Comments

admin

    Reply your comment

    Your email address will not be published. Required fields are marked*