Abstract
Statically analyzing code during development is a common process of the development process, using Static Application Security Testing tools. SAST analyzes code without its execution and is also very fast compared to dynamic means and therefore focuses on a certain program part. However, the results of static analysis tools are not always accurate, either missing vulnerabilities or reporting false positives. This paper considers an evaluation of several SAST tools and an analysis of student code samples with known vulnerabilities, comparing manual analysis with the results of SAST tools. The results confirmed that SAST tools properly identify critical vulnerabilities and provide errors. A tool has identified ShiftLeft as the most efficient tool; however, its findings overlapped with the results of other tools for some applications. In addition, an analysis of student projects showed the most frequent vulnerabilities as Cross-site Scripting (XSS), NoSQL/SQL Injection, and Server-Side Request Forgery (SSRF) which make up more than 52% of the found vulnerabilities.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: The International Journal of Engineering & Information Technology (IJEIT)
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
