Interface and context menus

Find the right tab, context menu and result view for each task.

Main areas

Area	Use
Dashboard	Overview of scan progress and findings; batch controls.
Scanners → Active	Local and server active scan entries, progress and evidence views.
Scanners → Passive	Passive scan entries and matched profiles, including server passive findings.
Scanners → Smart	Rule matches and the active profiles launched from them.
Scanners → AI	AI analysis status, structured results, request/response and provider settings.
Scanners → Live	Activity produced by live scanning.
Rules	Create, edit, enable, duplicate, import and export Smart Scan rules.
Profiles	Active, Passive Request and Passive Response tables, plus Tags Manager.
Settings → General	Data directory, reload and live scanner configuration.
Settings → Variables	Built-in tokens and editable custom values.
Settings → Burp Bounty Servers	Server URLs, credentials, enablement and health.
License	Activation, current status and expiration.
About	Build information and update controls.

Right-click menu

Burp Bounty Pro
├── Local Scanner
│   ├── Active Scan → tags
│   ├── Passive Scan → All / Passive Request / Passive Response → tags
│   ├── Smart Scan
│   └── AI Scanner
└── Burp Bounty Server Scanner
    ├── Active Scan → tags
    └── Passive Scan → categories / tags

Tag entries display the profiles available for that choice. A menu count is not a prediction of the number of HTTP requests: payloads, insertion points, steps and early stopping also affect the work.

Scan dialog

Review URL selection, duplicate removal, scope, excluded extensions and regex filters. Removing parameterless URLs can also remove requests useful for path discovery or raw-request profiles. Match/replace settings modify the input used for scanning; inspect the result when changing headers or session data.

The local Active dialog has Concurrency and Requests per second. Passive, Smart and AI workflows still expose their own worker/analysis settings. The Server dialog additionally selects servers and whether each budget is per server or overall. See scan control.

Profile editors are opened from the corresponding table. Keep profile names unique so rule references and MCP selections remain unambiguous.