Burp Suite Import
Burp Suite Import
Section titled “Burp Suite Import”Import web application security findings from Burp Suite into NEURO. Bring in Scanner results, manually identified issues, and evidence to accelerate your reporting.
Overview
Section titled “Overview”Burp Suite is the leading web application security testing tool. NEURO imports:
- Scanner findings
- Manual issues
- Request/response data
- Severity ratings
- Remediation guidance
Supported Formats
Section titled “Supported Formats”| Format | Source | Recommended |
|---|---|---|
| Burp XML | Export from Burp | - Yes |
| Burp HTML | Report export | Not supported |
Exporting from Burp Suite
Section titled “Exporting from Burp Suite”Export Issues as XML
Section titled “Export Issues as XML”- In Burp Suite, go to Target → Site map
- Right-click on target domain
- Select Issues → Report issues
- Or: Scanner → Scan queue → Right-click → Report
Export Settings
Section titled “Export Settings”Choose these options for best import:
- Format: XML
- Include: All issues or selected
- Details: Full (include request/response)
Export Selected Issues
Section titled “Export Selected Issues”To export specific findings:
- Go to Issues view
- Select issues to export
- Right-click → Report selected issues
- Choose XML format
- Save file
Importing Burp Results
Section titled “Importing Burp Results”Step-by-Step
Section titled “Step-by-Step”- Open your project in NEURO
- Navigate to Findings tab
- Click Import → Burp Suite
- Upload your XML file
- Configure options:
- Severity threshold
- Include confidence levels
- Import evidence?
- Review preview
- Click Import
Import Options
Section titled “Import Options”| Option | Description |
|---|---|
| Minimum Severity | Lowest severity to import |
| Minimum Confidence | Certain, Firm, or Tentative |
| Include Evidence | Import request/response |
| Create Assets | Create web app assets |
| Deduplicate | Merge similar issues |
Severity Mapping
Section titled “Severity Mapping”Burp Suite to NEURO:
| Burp Severity | NEURO Severity |
|---|---|
| High | High |
| Medium | Medium |
| Low | Low |
| Information | Informational |
Confidence Levels
Section titled “Confidence Levels”Burp confidence indicators:
- Certain: Confirmed vulnerability
- Firm: Very likely vulnerability
- Tentative: Possible, needs verification
Consider filtering by confidence:
- Import Certain + Firm for confirmed issues
- Review Tentative manually before including
Imported Data
Section titled “Imported Data”Finding Fields
Section titled “Finding Fields”| Finding Field | Burp Source |
|---|---|
| Title | Issue name |
| Description | Issue detail |
| Severity | Severity rating |
| Remediation | Remediation detail |
| Evidence | Request/response |
| URL | Affected endpoint |
| Parameter | Vulnerable parameter |
Evidence Import
Section titled “Evidence Import”When evidence is included:
- HTTP requests captured
- HTTP responses captured
- Highlighted injection points
- Payload details
Common Burp Findings
Section titled “Common Burp Findings”Imported Issue Types
Section titled “Imported Issue Types”| Issue Category | Examples |
|---|---|
| Injection | SQL injection, XSS, Command injection |
| Authentication | Session issues, weak passwords |
| Information | Version disclosure, verbose errors |
| Configuration | Missing headers, insecure cookies |
| Cryptography | Weak TLS, insecure algorithms |
Issue Enhancement
Section titled “Issue Enhancement”After import, enhance findings:
- Verify the vulnerability manually
- Add specific evidence (screenshots)
- Use AI to improve descriptions
- Add business context
Handling False Positives
Section titled “Handling False Positives”Burp Scanner may report false positives:
Review Process
Section titled “Review Process”- Import all findings
- Review each finding
- Mark false positives appropriately
- Delete or change status
Filtering During Import
Section titled “Filtering During Import”Reduce false positives by:
- Only importing High/Medium severity
- Requiring Certain/Firm confidence
- Reviewing preview before import
Deduplication
Section titled “Deduplication”Same Vulnerability, Multiple URLs
Section titled “Same Vulnerability, Multiple URLs”When same issue found on multiple endpoints:
- Group as single finding
- List all affected URLs
- Maintain evidence for each
Settings
Section titled “Settings”- Merge by issue type: Same vulnerability = one finding
- Keep separate: Each instance = separate finding
- Hybrid: User reviews suggestions
Advanced Import
Section titled “Advanced Import”Request/Response Handling
Section titled “Request/Response Handling”Evidence import options:
- Full request/response
- Highlighted portions only
- None (finding details only)
Large evidence can:
- Increase import time
- Affect finding readability
- Be added manually instead
Burp Extensions
Section titled “Burp Extensions”If using Burp extensions that add custom issues:
- Standard format issues import normally
- Custom format may need manual entry
- Check import preview for missing data
Best Practices
Section titled “Best Practices”Scanning Strategy
Section titled “Scanning Strategy”For best import results:
- Active scan complete target
- Review findings in Burp first
- Remove obvious false positives
- Export remaining issues
- Import into NEURO
Quality Over Quantity
Section titled “Quality Over Quantity”Consider importing in stages:
- High severity + Certain confidence first
- Verify and enhance those findings
- Add Medium severity
- Review Low/Info as needed
Evidence Management
Section titled “Evidence Management”For important findings:
- Import finding without evidence
- Capture clean screenshots manually
- Add annotated evidence
- Write specific reproduction steps
Troubleshooting
Section titled “Troubleshooting”Import Errors
Section titled “Import Errors”“Invalid XML”
- Ensure XML format (not HTML report)
- Check file isn’t corrupted
- Re-export from Burp
“No issues found”
- Check severity/confidence filters
- Verify scan found issues
- Try without filters
“Missing data”
- Some fields may be empty in Burp
- Add details manually
- Enhance with AI
Quality Issues
Section titled “Quality Issues”Poor descriptions
- Burp descriptions may be generic
- Use AI enhancement
- Add manual context
Missing evidence
- Re-export with evidence enabled
- Add manually from Burp
- Capture new screenshots
Next: Learn about API Integration