liveBook · Manning

Static application security testing

Also called SAST

Static application security testing analyzes source code or other software artifacts without executing the application to identify potential security vulnerabilities.

How 3 Manning books explain it

Grokking Software Architecture

Static application security testing is the automated analysis of application source or compiled code for vulnerabilities without executing the application.

How it is used
Scans application code to catch business-logic vulnerabilities before code reaches production.
How deep it goes
Identifies hardcoded secrets and injection flaws, but does not describe how to remediate findings.
Examples
Names SonarQube as a scanning tool and hardcoded secrets and injection flaws as findings.
What you can do after
Apply it via tools such as SonarQube to flag hardcoded secrets or injection flaws.

Read how Grokking Software Architecture explains static application security testing →

Secure APIs

Static application security testing analyzes application source code or related artifacts without executing the application to identify security flaws and misconfigurations.

How it is used
Uses code analysis during implementation and CI/CD to catch security flaws before insecure APIs are released.
How deep it goes
Identifies common code flaws, vulnerabilities, and misconfigurations, while deferring runtime, dependency, fuzz, and integration concerns to other tests.
Examples
Uses Snyk, Semgrep, Aikido, and Checkmarx to inspect application code.
What you can do after
Diagnose code-level security flaws and misconfigurations before deployment.

Read how Secure APIs explains static application security testing →

Vibe Engineering

Static Application Security Testing is the analysis of source code or compiled code without executing the application to identify security vulnerabilities.

How it is used
Finds known security antipatterns in code before execution, providing a scalable verification layer for AI-generated and conventional code.
How deep it goes
Explains pattern matching, scalability, false positives, and limits, but stops short of reliably detecting domain-specific logical errors.
Examples
Uses unsafe regular expressions, unsanitized HTML output, and a parser bug that generic analysis cannot recognize.
What you can do after
Apply SAST in continuous verification, triage warnings, and combine findings with tests and human review.

Read how Vibe Engineering explains static application security testing →

Also covered in

What to know first

Related concepts

Questions about static application security testing

What is static application security testing?

Static application security testing analyzes source code or other software artifacts without executing the application to identify potential security vulnerabilities.

Which Manning books explain static application security testing?

Grokking Software Architecture, Secure APIs and Vibe Engineering.

What should I know before learning static application security testing?

Manning books that teach static application security testing usually introduce SQL injection and vulnerability first.

What is the difference between static application security testing and dynamic application security testing?

Static application security testing analyzes source code or other software artifacts without executing the application to identify potential security vulnerabilities. Dynamic application security testing is the evaluation of a running application through its interfaces or executable behavior to identify security vulnerabilities.

What is static application security testing a kind of?

Static application security testing is a kind of static analysis. Static analysis is the examination of source code or other software artifacts without executing the program to infer properties or identify potential issues.

What is static application security testing also called?

Static application security testing is also called SAST.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.