liveBook · Manning

Static application security testing

As explained in Grokking Software Architecture

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

Static application security testing (SAST) scans application code without running it, helping teams catch vulnerabilities before code reaches production. A tool such as SonarQube can flag hardcoded secrets or injection flaws in the CI/CD pipeline. section 11.7.1

How Grokking Software Architecture covers it

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.
How it connects
Connects SAST with CI/CD pipelines and application vulnerabilities such as injection flaws.

Also explained in

Compare how 3 books explain static application security testing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.