π§ Smart Scan
Smart Scan is one of the most powerful features of Burp Bounty Pro. It uses Rules to automatically trigger active scanning profiles when specific passive conditions are detected β creating intelligent, context-aware scanning workflows.
π‘ Concept
Smart Scan follows an IF-THEN pattern:
IF passive profile(s) match β THEN execute active profile(s)This means:
ποΈ Passive profiles continuously analyze all traffic (requests and responses)
π When a passive profile matches, rules check if conditions are met
π― If conditions are met, active profiles are automatically executed against the matched request
β Why Smart Scan?
Instead of running all active profiles against every request (which is slow and noisy), Smart Scan:
β‘ Reduces scan time β Only tests relevant vulnerabilities for each target
π― Reduces false positives β Only scans when context suggests a vulnerability is likely
π€ Automates workflows β No manual intervention needed to target specific technologies
π₯οΈ Enables technology-specific testing β Detects WordPress, Jira, Spring, etc. and runs their CVE profiles
βοΈ How It Works
π Example: WordPress Detection
ποΈ Passive Response profile
Wordpress detectionmatches responses containing WordPress indicators (e.g.,wp-content,wp-includes)π Rule
Wordpress_Ruleis configured:IF: Passive Response profile
Wordpress detectionmatchesTHEN: Execute active profiles:
Wordpress_user_enum_oembed,Wordpress_user_enum_json,Wordpress_directory_listing,Wordpress_Path_Traversal,Wordpress_Config_Accessible, etc.
π― Active scanning automatically begins on the matched request with WordPress-specific profiles
π Example: SQL Injection Parameter Detection
ποΈ Passive Request profile
SQLi_Parametersdetects parameters likeid=,user_id=,query=π Rule
SQLi_Ruleis configured:IF: Passive Request profile
SQLi_ParametersmatchesTHEN: Execute active profiles:
SQLi,SQLi_Timebased_Encoded_Space
π― Active scanning targets only the requests with suspicious parameters
π Rule Structure
Each rule consists of:
π Match Conditions (IF)
One or more passive profile matches that must be satisfied:
π¨ Passive Request profiles β Match patterns in HTTP requests
π© Passive Response profiles β Match patterns in HTTP responses
π Logic operators β Combine conditions with AND/OR:
AND β All conditions must match
OR β At least one condition must match
π― Execute Actions (THEN)
What to do when conditions are met:
π Execute specific profiles β Run named active profiles
π·οΈ Execute profiles by tag β Run all active profiles with a specific tag (e.g., all profiles tagged "XSS")
π― Match scope β Execute on "All Matches" or "First Match" only
π Smart Scan Flow
βοΈ Configuration
β‘ Scanner Settings
When Smart Scan rules trigger active scans automatically, they use default scanner settings (10 threads, 10 concurrency, 10 RPS). These defaults are suitable for most scenarios.
When you manually launch a Smart Scan via the context menu, the URL Filter popup appears and you can configure per-scan settings (Threads, Concurrency, Requests per second) just like with Active Scan.
See Scan Control for details on per-scan performance configuration.
β
Enabling/Disabling Rules
Go to Burp Bounty Pro > Rules tab
Enable/disable individual rules with the checkbox
Only enabled rules participate in Smart Scan
π¦ Default Rules
Burp Bounty Pro ships with 27 pre-configured rules covering:
π₯οΈ Technology detection β WordPress, Jira, Spring Boot, Drupal, Symfony, Weblogic, CouchDB, etc.
π Vulnerability parameters β SQLi, XSS, RCE, LFI, SSRF, SSTI, Open Redirect
π Bulk scanning β Disabled by default: scan all requests with specific profile groups
See Default Rules for the complete list.
π Creating Custom Rules
See Creating Rules for a step-by-step guide.
Last updated