DAST Named

Dynamic analysis hits running apps — concept on YOUR local lab URL only.

DAST Named• Audio Walkthrough

00:00/02:46

Visual · t17_dast_named

DAST = probe running app like a client would. Original Cyberlium.

DAST finds the hole your unit tests never visited — but only on servers you are allowed to hammer.

Dynamic Application Security Testing sends HTTP requests to a live app to find XSS, misconfig headers, cookie issues, and exposed endpoints. Tools include OWASP ZAP and Burp Scanner modes — used against YOUR lab instance on localhost or $LAB_URL you deploy. DAST is noisy and needs scope rules. Never aim DAST at employer production, school portals, SaaS you do not own, or 'just checking' public sites — that is unauthorized testing. Pair DAST findings with SAST and manual review on $REPO.

1. SAST vs DAST

SAST: source without running. DAST: HTTP to running build with routes and config live.

DAST catches deployment mistakes SAST misses — wrong headers, debug endpoints enabled.

Command guide

Try these commands — SAST vs DAST

═══ LINUX / BASH (Network & Reconnaissance Audit) ═══

Scan target host for open ports and service version signatures

Command — copy this

nmap -sS -sV -p 80,443,8080 -Pn ${LAB_HOST:-127.0.0.1}

DNS and WHOIS reconnaissance on authorized domain

Command — copy this

dig +short A target.local
dig +short MX target.local
whois target.local 2>/dev/null | grep -iE "(Registrar|Creation Date|Name Server)" | head -6

Inspect HTTP headers for technology stack fingerprinting

Command — copy this

curl -s -I "http://${LAB_HOST:-127.0.0.1}:8080" | grep -iE "(Server|X-Powered-By|Set-Cookie|Content-Security-Policy)"

Primary tools to practice this lesson: curl, python3. Reference sites: DAST overview (https://owasp.org/www-project-web-security-testing-guide/); OWASP ZAP (https://www.zaproxy.org/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.