Dynamic Application Security Testing (DAST)

Dynamic application security testing (DAST) tests a running application from the outside, sending attack-like requests to find vulnerabilities such as injection flaws and misconfigurations, without needing the source code.

AdvancedCategory: Cloud and software supply chain

Also called: DAST, web application scanning, black-box testing, web vulnerability scanner

What is DAST?

Dynamic application security testing examines an application while it's running, usually a website, web app or API. The scanner has no access to the source code. Instead, it behaves like an automated attacker: it crawls the application, finds forms, links and API endpoints, then sends crafted requests and watches the responses for signs of vulnerabilities. Because it sees only what an outsider sees, it's called black-box testing.

NIST's Secure Software Development Framework includes testing executable code for vulnerabilities as a core practice alongside code review.

What DAST finds

Strengths and limits

Strengths: it tests the real, deployed application, including its server and configuration; it works regardless of programming language; it finds problems SAST can't see; and findings are usually real and reproducible, with fewer false positives than SAST.

Limits: it finds problems late, after code is built; it can't point to the exact line of code; it can miss pages it can't reach, especially behind logins or in complex single-page apps; it rarely finds business logic or access control flaws; and aggressive scans can disrupt production systems or fill databases with junk.

Well-known tools include the free, open-source ZAP and commercial scanners such as Burp Suite.

DAST vs SAST vs pen testing

  • [SAST](/glossary/static-application-security-testing/) reviews code from the inside, early.
  • DAST scans the running app from the outside, automatically.
  • [Penetration testing](/glossary/penetration-testing/) is skilled people testing the app manually, finding logic and access control flaws automated tools miss.

A good program uses all three. For a business website or customer portal, a web application penetration test usually includes DAST scanning plus manual testing. Ongoing vulnerability scanning can include regular DAST scans between tests.

Related terms

Sources

  1. SP 800-218: Secure Software Development Framework (SSDF) Version 1.1 (NIST)
  2. Vulnerability Scanning Tools (OWASP)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.