DAST
DAST: Dynamic Application Security Testing
DAST tests an application that is already running, from the outside. The scanner crawls the web interface and API, sends specially crafted requests and analyzes the responses. Source code is not required.
DAST finds what is visible only at runtime: configuration errors, session and authentication problems, missing security headers, and injections that actually fire.
How it works
- Crawling: the scanner builds a map of pages, forms and API endpoints (often from an OpenAPI specification).
- Passive checks: analysis of server responses without attacks, covering headers, cookies and information leaks in error messages.
- Active checks: injecting payloads for SQL injection, XSS, path traversal and so on.
- Authenticated scanning: logging in to test the protected part of the application.
Limitations and common mistakes
- It needs a deployed environment, preferably a test one rather than production.
- It does not show the line of code with the flaw, only the request and the response.
- It finds logic vulnerabilities poorly. That is the pentester's work.
Tools
OWASP ZAPNucleiBurp SuiteNikto
Questions and answers
Is DAST a pentest?
No. DAST is automated scanning. A pentest is the work of a person who looks for attack chains and logic errors. Automation gives regularity and a pentest gives depth.
Can DAST run against production?
Passive checks can. Active attacks may change data and load the system, so they are run on a test environment.