skip to content

Scanner & Audit

Burp Scanner crawls then audits, rates each issue by severity and confidence, and uses Collaborator to see out-of-band interactions. Interviewers probe triage: an unreviewed report is no pentest.

on this pageshow

explore

questions

6

In Burp Scanner, what do the crawl and audit phases each do, and which audit checks send no extra requests?

level: juniorimportance: must knowfreq 42%

answer

  1. two phases, map then test
  2. audit is split three ways
  3. one kind only watches traffic
  4. starts before the crawl ends
  5. crawl is not read-only

basics

~20 s

Burp Scanner first crawls the application to map its content and navigation, then audits it. Passive audit checks only analyse traffic already seen and send nothing extra; active checks send modified requests, and JavaScript analysis reads returned code.

solid answer

~40 s

A Burp scan has two phases. **Crawling** catalogues the application: it navigates with Burp's embedded browser by default, follows links, submits forms and logs in where needed. **Auditing** then tests what the crawl found, in three sub-phases: a **passive** phase that analyses normal traffic without sending any additional or modified request, an **active** phase that inserts modified input into requests, and a **JavaScript analysis** phase that studies returned code for DOM-based issues. By default the audit starts as soon as the crawl finds its first item rather than waiting for the crawl to end, and the audit queue is re-prioritised as new items appear. Only the passive audit is traffic-neutral. The crawl itself still generates requests, including form submissions.

go deeper

for a junior

Recall the order and the split: crawl maps the application, audit tests it, and passive checks add no requests of their own.

for a middle

Explain the three audit sub-phases, why passive consolidation exists, and why the audit starts as soon as the crawl finds its first item.

for a senior

Describe what each phase looks like in the target's logs and why a passive-only configuration still leaves the crawl's form submissions and logins to be scoped.

for a principal

Decide which scan phases and accounts a tooling standard permits per environment, weighing coverage against the state changes a crawl can cause.

## What a Burp scan is Burp Scanner is the automated dynamic web vulnerability scanner that powers scans in Burp Suite Professional and in Burp Suite DAST. A scan generally has two key phases: **crawling**, which maps the application, and **auditing**, which analyses its traffic and behaviour for security issues. In an authorised assessment the scan produces two things for a human to read: a map of what the application exposes, and a list of issues, each with a severity and a confidence. It replaces neither the written scope nor the review of the results. ## The crawl phase The crawler catalogues the application's content and the navigational paths between its parts. - It follows links, **submits forms** and **logs in where necessary**, so it behaves much as a person using the application would. - By default it uses Burp's embedded Chromium browser, which lets it handle pages whose interface is built by JavaScript. - It builds a directed graph of locations. A location is identified by its contents, not by the URL used to reach it, so changing cache-busters or tokens in URLs do not fool it. - It crawls breadth-first, fingerprints locations it has already visited and honours configurable cutoffs, which also keeps it from chasing endless content such as a calendar. - When an authenticated scan is configured, it first crawls without credentials, then tries to log in. If the application offers self-registration, Burp by default attempts to register a user. The crawl is therefore not read-only. Anything a normal user can do through the interface, including submitting a form, is something the crawler may do. ## The audit phase The audit tests the application. PortSwigger separates it into three phases so that redundant checks are avoided and work can run in parallel. | Sub-phase | What it does | Traffic it adds | |---|---|---| | Passive | Observes normal traffic for problems exposed during typical use, such as serialized objects in HTTP messages | None: no additional or modified requests | | Active | Inserts modified input into requests, in three tiers (Light, Medium, Intrusive) | Modified requests, many per insertion point | | JavaScript analysis | Static analysis of returned code plus dynamic analysis in an embedded headless browser, to find DOM-based issues | Works on responses already received | The three active tiers differ in how aggressive their requests are: **Light** checks send a small number of modified requests, **Medium** checks send requests the application might read as malicious, and **Intrusive** checks simulate real-world attacks and carry a significant risk of changing or damaging data. The point here is the line between the first row and the other two: only passive checks observe without touching. ## Order and parallelism 1. The crawl starts and discovers items. 2. By default the audit begins as soon as the **first** item is discovered. The setting is named *Allow crawl and audit phases to run in parallel*. 3. Each time the crawl finds something new, Burp recalculates the priority of every item in the audit queue. The priority score is weighted 80/20 in favour of **attack surface exposure** (how many insertion points an item adds) over **interest level** (state-changing methods, structured content, authentication required). 4. After the audit completes, follow-up passes retry requests that timed out. Because crawl and audit overlap, issues can appear while the crawl is still running, and an owner watching logs sees crawl-style and audit-style requests interleaved. ## Passive checks: what they need and what they leave out - A passive check needs traffic to look at. It sees what the crawl, or a person browsing through Burp, has already produced. - It cannot learn how the application reacts to unexpected input; that is what the active phase is for. - Passive findings can repeat across many pages through shared templates. Burp **consolidates** identical passive issues and reports one instance at the most relevant level, such as the web root or a shared folder, while every individual occurrence stays recorded as evidence in the report. The *Issue noise reduction* setting controls this, and the built-in *Audit coverage - maximum* configuration turns it off. ## What the owner and the defender see - From the crawl: browser-like navigation, form submissions and, if configured, logins. - From the active audit: bursts of modified requests, often to the same endpoint, and sometimes errors that Burp handles by retrying, marking checks failed or pausing the scan. - From the passive audit: nothing of its own. - By default Burp pauses an audit after 10 consecutive requests time out, so a struggling target tends to stop the scan rather than be hammered, unless a built-in configuration that overrides this has been chosen. ## Common traps - Calling a scan "passive" because only passive checks are enabled does not mean it sends nothing. The crawl is a separate phase with its own traffic. - Assuming the audit waits for the crawl. By default it does not. - Treating JavaScript analysis as a kind of active check. It is its own phase and works on code the application has already returned.

  • If only passive audit checks are enabled, is the scan harmless to the application?
    Not automatically. PortSwigger describes the passive-only built-in configuration as entirely non-intrusive, but the crawl is a separate phase: it navigates, submits forms and may log in or register a user, so an owner who needs a quiet scan should also scope and configure the crawl and use a dedicated test account.
  • Why does Burp report one passive issue for a missing header across a whole site instead of one per page?
    Passive issues caused by shared templates or platform-wide settings are consolidated: Burp reports a single instance at the most relevant level, for example the web root or a shared folder, and keeps every occurrence as evidence in the report. This reduces noise without losing the list of affected locations.
  • What changes for the reader of the log when crawl and audit run in parallel?
    Audit requests start as soon as the first item is found, so crawl navigation and modified audit requests arrive interleaved instead of in two blocks, and issues can be raised before the crawl ends. The audit queue is re-prioritised as the crawl discovers items.

  • Says a passive scan sends no requests, forgetting the crawl phase still makes them
  • Believes the audit always waits for the whole crawl to finish
  • Thinks the audit only observes traffic and never modifies a request
  • Assumes the crawler only follows links and never submits forms or logs in
  • Folds JavaScript analysis into the active phase instead of treating it as its own

Assumes Burp Suite 2026.9 documentation; crawl and audit in parallel arrived with DAST 2025.5 and the scanner pages for both products now describe it as the default.

open as a page

In a Burp Scanner report, what do an issue's severity and confidence each tell you, and what does a Tentative High deserve?

level: middleimportance: must knowfreq 45%

basics

~20 s

Severity says how serious an issue is if real; confidence (Certain, Firm or Tentative) says how sure Burp is that it is present. A Tentative High is serious if true but unproven, so verify it by hand before reporting it.

open as a page

Before running Burp Scanner against a production-like system, how do its Light, Medium and Intrusive active checks differ in impact, and which settings limit them?

level: seniorimportance: should knowfreq 30%

basics

~20 s

Light active checks send a few benign modified requests; Medium checks may look malicious and trigger alerts or logouts; Intrusive checks can cause permanent data loss or outages. Limit them with the Scan checks setting or a built-in configuration.

open as a page

During an authorised Burp Scanner run, what does Burp Collaborator traffic look like to egress monitoring, and what does a Collaborator interaction prove?

level: seniorimportance: should knowfreq 18%

basics

~20 s

The target or its back-end makes DNS lookups, then HTTP(S) or SMTP connections, to unique subdomains of the Collaborator domain, and egress logs show those calls. An interaction proves the system can be induced to call out, not that it is vulnerable.

open as a page

In Burp Scanner, what is a BCheck, and what must its definition file contain before Burp will accept it?

level: middleimportance: nice to knowfreq 8%

basics

~20 s

A BCheck is a custom scan check written as a plain-text .bcheck file in PortSwigger's own definition language. It must start with a metadata block, contain one given-then statement, and report issues with a severity and a confidence.

open as a page

What did Burp Suite Enterprise Edition become in 2025, and how does Burp Suite DAST relate to the Scanner in Burp Suite Professional?

level: middleimportance: nice to knowfreq 11%

basics

~20 s

Burp Suite Enterprise Edition was renamed Burp Suite DAST with DAST 2025.5 on 22 May 2025. PortSwigger says DAST and Professional share one scanning engine and severity model: Professional is the interactive desktop tool, DAST the automated one for many sites.

open as a page