Static Application Security Testing (SAST) involves analyzing source code or compiled code for security vulnerabilities without executing the program. This method is well-suited for identifying syntax errors, coding standards violations, and potential security issues early in the development lifecycle.
A . Static application security testing (SAST): SAST tools analyze the source code to detect syntax errors, vulnerabilities, and other issues before the code is run. This is the most relevant task for the DevSecOps team to identify syntax errors and improve code quality.
B . Software composition analysis: This focuses on identifying vulnerabilities in open-source components and libraries used in the application but does not address syntax errors directly.
C . Runtime application self-protection (RASP): RASP involves monitoring and protecting applications during runtime, which does not help in identifying syntax errors during the development phase.
D . Web application vulnerability scanning: This involves scanning the running application for vulnerabilities but does not address syntax errors in the code.
Reference:
CompTIA Security+ Study Guide
OWASP (Open Web Application Security Project) guidelines on SAST
NIST SP 800-95, "Guide to Secure Web Services"
Top of Form
Bottom of Form