Course contentsShow
← Security
Lesson 2208 of 3,05243. Offensive Security ToolingFree lesson

Target Scope and Site Map Management

Defining testing scope, managing the site map, understanding passive vs active spidering, and organizing discovered content.

Target Scope and Site Map Management

You'll learn how to control which parts of an application Burp Suite interacts with and how to organize discovered pages for efficient testing.

Why Scope Matters

When testing a web application, you don't want to accidentally scan or attack systems you're not authorized to test. Imagine you're auditing a company's blog at blog.example.com, but Burp starts following links to payments.example.com or external sites—that's both unauthorized and unprofessional.

Target scope is your safety boundary. It tells Burp: "Only interact with these specific domains or paths." Everything outside is off-limits.

Defining Your Scope

In Burp Suite, you define scope under the Target tab → Scope settings. You can:

  • Add specific URLs, domains, or IP ranges
  • Use regex patterns for fine-grained control
  • Set "include" rules (what's in scope) and "exclude" rules (exceptions)

For example, if testing https://shop.example.com/admin/*, you'd include that path but exclude https://shop.example.com/logout to avoid disrupting your session.

The Site Map: Your Navigation Hub

As Burp intercepts traffic, it automatically builds a site map—a tree structure showing all discovered URLs, parameters, and responses. Think of it as a automatically-drawn blueprint of the application.

Passive vs Active Spidering

  • Passive spidering: Burp observes traffic you generate manually (clicking links, submitting forms) and maps what it sees. No automated requests.
  • Active spidering: Burp automatically crawls the application, following links and submitting forms to discover hidden pages. More thorough, but detectable.

The site map color-codes entries (black for in-scope, gray for out-of-scope) and lets you annotate, filter, and organize findings by folder structure.

Key Takeaway: Proper scope definition prevents unauthorized testing and legal issues, while the site map organizes your attack surface—use passive discovery first, then controlled active spidering within defined boundaries.