dynamic application security testing
Testing a running service for security problems by sending it crafted requests and observing the responses and state changes.
In more detail
DAST sees what a user can actually reach: headers, redirects, error pages, reflected input and state changed without credentials. Run it against an isolated, disposable deployment with seeded fake data, and keep each finding as a request paired with an observed effect.
Related terms
- regression test — A test run to check that behaviour which used to work still works after a change.
- security headers — HTTP response headers that switch on browser protections, such as HSTS for HTTPS-only access and X-Frame-Options against framing.
- static application security testing — Finding security problems by reading a program's source code without running it.
Taught in
- Adding GitLab's Security Scanners To A Pipeline — GitLab Certified CI/CD Associate Exam Prep
- Dynamic Scanning — Application Security & Threat Modeling for Engineers