Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 38 ยท Scanner and Extensions

Burp Scanner - Crawling and Auditing

Learn how Burp Scanner crawls a site and audits it, what passive and active checks do, how to scope a scan safely, and how to read the scan task results.

The first four chapters of this track taught you to drive Burp by hand: proxy a request, replay it in Repeater, fuzz it in Intruder. Burp Scanner automates a large part of that work. It visits the application, remembers what it found, and then sends carefully chosen test requests to look for known classes of weakness. In this lesson you learn what the scanner does, how its two phases fit together, and how to start a scan without harming a system you do not own.

Only scan applications you own or have written permission to test. An active scan sends thousands of requests, some of them malformed on purpose. Against a system you are not authorised to test that is illegal in most countries, and against a fragile one it can cause outages. Every example here is read-only output, or a stand-in that runs on your own machine.

A note about what runs on this site: Burp Suite is a desktop Java application, so it cannot run in your browser. The Burp screens and logs below are labelled example output that matches how the tool behaves. The runnable blocks are small Python stand-ins that show the idea behind a feature, not Burp itself.

Two phases: crawl, then audit

Burp Scanner has two jobs, and a scan task can do either or both:

  • Crawl discovers content. It starts at one or more URLs, follows links, submits forms with sample values, and builds a map of the site (the site map you saw in the Target tab).
  • Audit tests what the crawl found. For each request it sends variations and watches the responses for signs of vulnerabilities.

A Crawl and audit task runs both, one after the other. A Crawl task only builds the map, and an Audit selected items task skips discovery and tests only the requests you chose.

flowchart LR
  A["Start URLs<br/>and scope"] --> B["Crawl:<br/>follow links, fill forms"]
  B --> C["Site map<br/>(URLs, parameters)"]
  C --> D["Audit:<br/>passive checks"]
  C --> E["Audit:<br/>active checks"]
  D --> F["Issues list"]
  E --> F

The crawl feeds the site map, and the audit reads it.

How the crawler differs from the old spider

Older Burp versions had a "spider" that just followed links. The modern crawler behaves more like a browser: it keeps a cookie jar, tracks state, understands JavaScript-built navigation, and notices when a link leads to a page that depends on being logged in. It also tries to recognise the same page reached by different URLs so it does not loop forever on calendars or session IDs in the path.

Passive and active checks

The audit phase uses two kinds of check, and the difference matters for safety.

Kind What it does Extra requests Risk to the target
Passive Reads responses that already exist (from the proxy or crawl) and flags things like missing security headers, cookies without HttpOnly, or an email address in a page None Almost none
Active Sends new requests containing test payloads and compares the replies Many Can create data, trigger errors, slow the server

Passive checking is why Burp Suite Professional shows issues just by browsing through the proxy: nothing extra is sent. Active checking is what you control carefully.

A passive check you can run

A passive check is nothing magical: it is a function over a response. This stand-in applies three checks to a response written as plain text.

Python A passive check in plain Python (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Burp's built-in checks are far more careful, but the principle is the same: they never send anything, they only look.

Starting a scan

In Burp Suite Professional you can start a scan from several places: right-click a request and choose Scan, use the Dashboard and click New scan, or right-click a host in the site map. The wizard asks for:

  1. Scan type: crawl and audit, crawl only, or audit only.
  2. URLs to scan: the start points.
  3. Scan configuration: crawl strategy, audit coverage, limits.
  4. Application login: optional credentials so the crawler can reach logged-in pages.

Example of the Dashboard task line once a scan is running (labelled example output):

TEXT
Task 4  Crawl and audit of https://lab.example.test
Status: Auditing   Requests: 18,420   Errors: 0
Issues found:  High 1   Medium 3   Low 5   Information 9
Crawl: 214 locations   Audit queue: 37 items

Define scope first

Burp has a target scope, a list of URL prefixes that you are allowed to test. Always set it before scanning (Target tab, Scope). Then the scanner stays inside it, and you can tell Burp not to even log out-of-scope traffic. Scope is both a safety rail and a legal record of what you intended to test.

Add the logout URL and any "delete account" or "reset database" pages to the exclude list. A crawler that clicks every link will eventually click those.

Reading task results

Select a task on the Dashboard and you get three views:

  • Issue activity: each finding with severity (High, Medium, Low, Information) and confidence (Certain, Firm, Tentative).
  • Event log: crawler decisions, login failures, rate-limit messages.
  • Logger / Audit items: every request the scan sent, so you can replay one in Repeater to confirm a finding by hand.

Severity says how bad the issue would be if real. Confidence says how sure Burp is that it is real. A "Medium / Tentative" finding is a lead to verify, not a result to report. The next lessons cover scan configuration and triage.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the difference between the crawl and audit phases?

    The crawler maps the application; the audit takes the discovered requests and tests them.
  2. 2. Why can passive checks run on traffic that just passes through the proxy?

    Passive checks read existing messages, so they add no traffic and carry almost no risk.
  3. 3. What should you do before starting a scan?

    Scope keeps the scanner on authorised hosts, and exclusions stop the crawler triggering destructive links.
  4. 4. An issue is listed as Medium severity with Tentative confidence. What does that mean?

    Confidence is separate from severity. Tentative findings are leads that need manual confirmation.

Summary

  • Scanner = crawl (discover) plus audit (test); you can run either or both.
  • Passive checks read existing traffic; active checks send new requests and carry real risk.
  • Set scope and excludes first, and only scan systems you are authorised to test.
  • Read severity and confidence together, and confirm tentative issues by hand.
  • The Burp screens shown here are labelled example output; the Python blocks are stand-ins.

Next: Scan configurations and insertion points