DAST Configuration and Scope Management
What You'll Learn
You'll learn how to define scan boundaries, exclude sensitive endpoints, adjust attack intensity, and prevent DAST scanners from harming production systems.
Why Scope Management Matters
After setting up authentication (lesson 1373), your DAST scanner can now explore your application. But without proper configuration, it might:
- Overload production servers with aggressive requests
- Trigger real transactions (like sending emails or charging credit cards)
- Test third-party APIs you don't own
- Exhaust rate limits or cause service disruptions
Think of DAST scope management like giving a security auditor a map with clear boundaries: "Check these rooms thoroughly, but don't touch the server room or the CEO's office."
Key Configuration Areas
Setting Scan Scope
Define which URLs and domains the scanner should test. Most tools allow:
- Include lists: Base URLs and allowed paths (
https://app.example.com/api/*) - Exclude lists: Administrative endpoints, logout URLs, or destructive actions (
/admin/delete,/api/payment/charge)
Configuring Attack Intensity
Adjust how aggressively the scanner probes:
- Request rate: Requests per second (lower for production)
- Concurrent threads: Parallel attack simulations
- Timeout values: How long to wait for responses
- Depth limits: How many clicks deep to explore
Preventing Production Impact
- Use dedicated testing environments whenever possible
- Configure safe-mode scans that avoid destructive operations
- Set resource limits to prevent overwhelming servers
- Schedule scans during low-traffic periods
- Implement kill switches to stop problematic scans immediately
Key Takeaway: Proper DAST scope configuration protects production systems from scan-induced damage while ensuring comprehensive security coverage of authorized targets—balancing thoroughness with safety through explicit boundaries and throttled attack intensity.