In Burp Suite, what does the target scope control during an authorised test, and what does it not do?
answer
- tells Burp which hosts to test
- logging, interception and display filters
- redirect following and live scan tasks
- a tester's aid, not a permission
- out-of-scope items stop being logged
basics
~20 sBurp's target scope tells it which hosts and URLs you intend to test; history filters, Proxy logging and interception, redirect following and live scanning read it. It cuts noise and accidents but is not the written authorisation.
solid answer
~40 sIn Burp Suite the **target scope** (Target > Scope) lists the hosts and URLs you intend to test. Other parts of Burp consult it: display filters can show only in-scope items, the Proxy can log or intercept only in-scope traffic, Repeater and Intruder can follow redirections only to in-scope URLs, WebSocket interception and match and replace rules can be limited to in-scope items, and in Professional a live task can audit in-scope requests. Setting scope also offers to stop logging out-of-scope items. Scope is the tester's own aid for noise and accidental testing: Burp's pages describe it as helping to avoid attacking hosts you may not test, not as proof of permission, so the written authorisation remains the boundary.
go deeper
Recall that scope names the hosts you intend to test, and that it cuts noise and helps avoid testing outside the agreed targets.
Name where Burp reads scope: history display filters, Proxy logging and interception, match and replace, redirection following, and live scan tasks.
Review a project: check the scope list against the authorisation, the logging choice, the history filter and the redirect settings, and say what each hides.
Define the team standard: scope is transcribed from the authorisation, reviewed by a second person, and never offered as evidence of permission.
## What target scope is The **target scope** is the list on the Target > Scope tab that tells Burp Suite which hosts and URLs you want to test. It exists because a browser proxied through Burp produces a great deal of traffic the tester does not care about: analytics calls, fonts, third-party widgets, update checks. Scope separates "the application under test" from everything else, and several parts of Burp read it. ## Where Burp reads scope | Part of Burp | What scope changes | |---|---| | Site map and HTTP history | A display filter can show only in-scope items | | Proxy history logging | Out-of-scope items can stop being sent to the history or to live tasks | | Proxy interception | Interception can be limited to in-scope traffic; the WebSocket rules have an **Only intercept in-scope messages** setting | | Match and replace | **Only apply to in-scope items** limits the rules | | Repeater and Intruder | Redirection following can be limited to destinations that are in scope | | Scanner live tasks (Professional) | A live task can audit in-scope requests as you browse | When you add a host with **Add to scope**, Burp shows the Proxy history logging prompt. Answering Yes turns on **Don't send items to Proxy history or live tasks, if out of scope**, and it makes **Apply to out-of-scope items** available in the TLS pass through settings. With that second option on, connections to out-of-scope hosts are passed through without Burp decrypting them, and neither the intercept view nor the history shows any detail of them. ## What scope does not do - It is **not authorisation**. The documentation presents scope as a way to reduce noise and to help avoid accidentally attacking hosts or endpoints you do not have permission to test. Whether you may test a host is decided by the written authorisation, which another topic covers; the scope list should be a transcription of it. - It is not a firewall. Browsing to an out-of-scope site still works; the traffic is simply not logged or intercepted once the options above are set. - Several of the effects are **settings**, not automatic behaviour. A filter that is switched off, or a Proxy that was never told to stop logging, will show and keep everything. ## A worked example An assessor is authorised to test `app.example.internal` only. The browser also loads a font host and an analytics host. The assessor adds `app.example.internal` to scope, answers Yes to the logging prompt and turns on the display filter, and the history now shows one host. A reviewer who opens that project cannot tell from it whether the page also contacted the font and analytics hosts: Burp stopped recording them, and only the application's logs or a network record would show it. Had the prompt been skipped, the project would hold third-party traffic that belongs to other organisations and that the team may not want in a project file it shares. ## Reading a test with scope in mind 1. Compare the scope list with the list in the authorisation. Every entry in one should appear in the other. 2. Check the display filter before reading the history. A history showing only in-scope items hides how much other traffic passed through. 3. Check the Proxy history logging choice. If out-of-scope items are not logged, absence from the history proves nothing about whether the browser contacted that host. 4. Check redirection settings in Repeater and Intruder, so a redirect cannot carry a request to a host outside the list. ## Staging first Burp's Proxy page states that using the Proxy may have unexpected effects in some applications, and that until you are fully familiar with its functionality and settings you should use it only against non-production systems. A scope list plus a staging target is the normal safe starting point. ## Common mistakes - Treating scope as the permission. - Believing a request to an out-of-scope host is blocked. - Reading a filtered history as the whole record of what the browser did. - Selecting Include subdomains when the authorisation names one application host.
- After you add the target host to Burp's scope and stop logging out-of-scope items, do requests to other hosts stop reaching them?No. Scope changes what Burp logs, intercepts, filters, follows and audits. The browser's other requests still pass through the listener to their servers. That is why scope is a noise and accident control, and why the authorisation, not scope, decides what may be tested.
- What would you check when reviewing a colleague's Burp project before signing off a test?That the scope list matches the written authorisation, that out-of-scope handling and the history filter are what the colleague says they are, that redirection following is limited to in-scope destinations, and that the project was pointed at a staging system unless production was explicitly authorised.
- Treats Burp's scope as proof the tester had permission
- Believes Burp blocks every request to an out-of-scope host
- Reads a scope-filtered history as everything the browser contacted
- Says scope only matters to the Scanner, not to the Proxy
- Says including subdomains is always safe when one host is authorised