DAST: Dynamic Application Security Testing
DAST tests your running application from the outside. It sends crafted HTTP requests, such as SQL injection payloads, cross-site scripting strings, SSRF attempts and authentication bypass sequences, and observes the responses. It finds vulnerabilities that only show up at runtime: misconfigured CORS policies, missing security headers, broken authentication flows, server-side request forgery, and injection flaws that survive input validation.
What DAST catches that others miss: runtime configuration issues (TLS settings, missing CSP, broken CORS), authentication and session management flaws, and server-side logic flaws that only appear when the application is running with its real middleware, databases and APIs connected.
What DAST misses: vulnerable dependencies in your package manifest, hardcoded secrets in source code, and code paths that are not reachable over HTTP.
SAST: Static Application Security Testing
SAST analyses your source code without executing it. It traces data flows from user input (sources) to dangerous operations (sinks) and identifies patterns that lead to injection, insecure cryptography, hardcoded credentials and access control gaps. It works across your whole codebase, including code that is not yet deployed.
What SAST catches that others miss: taint-flow vulnerabilities (input reaches a SQL query without sanitisation), insecure cryptographic choices (MD5 for password hashing, Math.random() in security contexts), vulnerabilities in dead code, and framework-specific anti-patterns.
What SAST misses: runtime configuration issues, vulnerabilities in third-party dependencies, and infrastructure misconfigurations.
SCA: Software Composition Analysis
SCA checks your dependency tree, both direct and transitive, against vulnerability databases. When a new CVE is published for a library three levels deep in your dependency chain, SCA flags it. It also produces the component list that a Software Bill of Materials (SBOM) is built from.
What SCA catches that others miss: known CVEs in transitive dependencies, licence problems, outdated packages with known exploits, and some supply chain attack indicators.
What SCA misses: vulnerabilities in your own code and runtime misconfigurations.
Why you need all three
A real application has vulnerabilities in its own code (SAST finds these), in its dependencies (SCA finds these), and in its runtime configuration and behaviour (DAST finds these). Running only one scanner leaves two categories unexamined.
Consider a typical web application. SAST finds a SQL injection path in a controller. SCA finds that the ORM library has a known deserialisation vulnerability. DAST finds that the CORS policy allows any origin and the session cookies lack the Secure flag. Three scanners, three findings, and none of them detectable by the other two.
Spoorder includes DAST, SAST and SCA from the Builder plan upwards. Findings from all three land in one list and are de-duplicated, and findings with a known CVE carry EPSS and CISA KEV data. AI fix suggestions are limited per plan: 10 a month on Builder, 100 on Pro and 500 on Scale, with none on Free.
Ready to scan your application?
Free health check: HTTPS, TLS and security headers for one URL, in about a minute. Free account, no credit card.
Scan your app free →