JavaScript is arguably the most important modern programming language, but despite its massive popularity, it is inherently very difficult to secure.
Code quality testing is commonplace to protect the master branch from defects. For example, unit testing creates a gate that ensures new code doesn’t break the application before it reaches the master branch. Not only does this increase the code quality of the master branch, it also ensures that other developers are not pulling problematic code into their own pull requests and writing new code that depends on the problematic code. Most organizations (99.7%) do not enforce similar security testing and quality gates in pull requests to protect their master branches.
This webinar will cover a developer-friendly model to analyze code insert security build rules for JavaScript. In this webinar, we'll discuss:
The growing gap between AppSec and application development
Why is analyzing JavaScript difficult? And how does ShiftLeft helps you conquer the complexity with modern developer workflows (including build rules)Why security build rules are so important bridging the gap
Requirements to consider when deploying security build rules
As well as show a live example of what this can look like in a GitHub repository