Dynamic application security testing meaning, in plain words

DAST (dynamic application security testing) sends test traffic to a running site and studies its reactions. How it works and what it cannot see, per OWASP.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

DAST is a method that mounts mock attacks on a running site to look for holes. It stands for Dynamic Application Security Testing. It sends test traffic from outside to the site that is actually running and studies how it reacts.

How does DAST work?

Picture a patrol outside a building that tries each window and door to see whether it is shut. It does not look at the building's plans and judges only by whether things really open.

OWASP's DevSecOps guideline describes DAST as a black-box method that examines from outside without looking inside. It feeds malicious input into the application to look for weaknesses. Because the target is a running application, no knowledge of the source code or the framework is needed. Once set up, it needs little human effort, and it can be run automatically at night.

Tools for this method are sorted in OWASP's Vulnerability Scanning Tools page as automated checking tools that examine from outside. How an assessment proceeds is on the dynamic testing page, and the guide to checks from outside is on the web application assessment page.

Why does DAST matter?

For a published site, how it looks from outside is the very surface that gets attacked. Because it can be checked without knowing the program's contents, it can be used on a system built by an outside party and on a site whose workings you have not fully grasped.

OWASP's guideline says DAST is particularly useful for finding flaws in checking input and output, authentication problems, and server configuration mistakes. That it can examine both the screen side and the server side is also listed as a feature.

On the other hand, because it does not look at source code, it is hard to point to which line of the program causes a problem. Note that places the traffic cannot reach, and processing that does not go through an input path, are hard to check. Combine it with a method that reads the contents, such as SAST, to widen what you can see.

For conditions on running it against production, contact us.

Related terms

  • Dynamic testing: an assessment that actually operates a running site to find holes.
  • SAST: a method that reads a program without running it to find holes.
  • Vulnerability assessment: an expert check for holes in a site or system.
  • IAST: a method that watches for holes from inside while the app runs.

Next step

Assessments that examine a web application from outside are on the web application assessment page. The free URL check shows only what is visible from outside. For conditions on running tests against production, contact us.

Frequently asked questions

May DAST be run against a live site?

Before running it, decide the target, the time window, and a ceiling on load. It can put load on production, or leave many submissions in a form. If you have a test environment, try there first.

Should we choose DAST or SAST?

They serve different purposes, so choose by role, not one or the other. SAST suits a program still being written, and DAST suits checking a published site from outside. Combining both widens what you can see.

Frequently asked questions

May DAST be run against a live site?

Before running it, decide the target, the time window, and a ceiling on load. It can put load on production, or leave many submissions in a form. If you have a test environment, try there first.

Should we choose DAST or SAST?

They serve different purposes, so choose by role, not one or the other. SAST suits a program still being written, and DAST suits checking a published site from outside. Combining both widens what you can see.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.