Everything About ___
Live briefing

Everything about Static application security testing

Software securing application

Static application security testing (SAST) is used to secure software by reviewing its source code to identify security vulnerabilities. Although the process of checking programs by reading their code has existed as long as computers have existed, the technique spread to security in the late 90s and the first public discussion of SQL injection in 1998 when web applications integrated new technologies like JavaScript and Flash. Wikipedia →

🧭 Start here: a 6-step reading path

  1. Read the overview: Static application security testingA 5-minute orientation
  2. Skim a recent paper: Understanding Industry Perspectives of Static Application Security Testing (SAST) EvaluationInfluential work since 2022
  3. Pick up a classic book: C How to ProgramThe most-reprinted book on the subject
  4. Read the landmark paper: Vulnerabilities Mapping based on OWASP-SANS: A Survey for Static Application Security Testing (SAST)Cited 70 times
  5. Go sideways: Application securityA closely related topic
  6. Go sideways: Automated code reviewA closely related topic

📖 Definitions

No dictionary entry for this exact phrase.

🗂️ The subject at a glance

  1. Overview
  2. SAST strengths
  3. SAST weaknesses
  4. Pipeline Automation and Standardization

🏆 Landmark papers (most cited)

🆕 Influential since 2022

📚 Books worth reading

Ranked by number of editions on Open Library, a rough measure of how lasting a book is.

🔗 Related topics