In theory, modern web frameworks provide secure ways of accessing databases, making SQL injections a non-issue. The reality looks much different. Among other injection vulnerabilities, SQL injections are still atop the OWASP Top 10, and organizations still frequently fall victim. Therefore there is no way around software security testing solutions that can reliably detect SQL injections.
TL;DR Fuzzing JavaScript is easy now In this post, we introduce you to our new open-source fuzzer for the JavaScript ecosystem, Jazzer.js. Jazzer.js is a coverage-guided, in-process fuzzer for the Node.js platform. It’s based on the experience we gathered developing its namesake Jazzer, our fuzzer for the JVM platform. Internally, Jazzer.js uses libFuzzer as a solid industry-standard engine and brings many of its instrumentation-powered mutation features to JavaScript.
All app development companies are aware of the importance of mobile application security testing. Despite this, the app stores are full of potentially vulnerable apps. One of the reasons for this is the myths surrounding the mobile application security testing concept - how it might be complicated or expensive to get security. However, this blog will dispel these myths and present a true picture of mobile application security testing.
To keep up with the ever-evolving cyber threat landscape, application security is a big challenge. Unfortunately, security is often overlooked in the modern software development and delivery framework and assumed as a luxury. Rather than taking a proactive approach, security is incorporated as a reactive approach that increases costs and makes the company suffer losses.
Static Application Security Testing (SAST) is one of the principal techniques for assessing the source code of applications to detect possible vulnerabilities. SAST enhances application security during the early stages of the development life cycle and plays an important role in shifting security left. However, there are quite a few myths that are often associated with implementing SAST security tools. Let’s run through the big three.
SAST is one of the matured security testing methods. In the SAST, the source code is examined from the inside out while components are in a static position. It performs scanning in-house code and design to identify flaws that are reflective of weaknesses, and that could invite security vulnerabilities. The scans performed by SAST tools are dependent upon prior identification of rules that specify coding errors to examine and address.
