Skip to content

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.

Burp Suite is the leading web application security testing tool. NEURO imports:

  • Scanner findings
  • Manual issues
  • Request/response data
  • Severity ratings
  • Remediation guidance
FormatSourceRecommended
Burp XMLExport from Burp- Yes
Burp HTMLReport exportNot supported
  1. In Burp Suite, go to TargetSite map
  2. Right-click on target domain
  3. Select IssuesReport issues
  4. Or: ScannerScan queue → Right-click → Report

Choose these options for best import:

  • Format: XML
  • Include: All issues or selected
  • Details: Full (include request/response)

To export specific findings:

  1. Go to Issues view
  2. Select issues to export
  3. Right-click → Report selected issues
  4. Choose XML format
  5. Save file
  1. Open your project in NEURO
  2. Navigate to Findings tab
  3. Click ImportBurp Suite
  4. Upload your XML file
  5. Configure options:
    • Severity threshold
    • Include confidence levels
    • Import evidence?
  6. Review preview
  7. Click Import
OptionDescription
Minimum SeverityLowest severity to import
Minimum ConfidenceCertain, Firm, or Tentative
Include EvidenceImport request/response
Create AssetsCreate web app assets
DeduplicateMerge similar issues

Burp Suite to NEURO:

Burp SeverityNEURO Severity
HighHigh
MediumMedium
LowLow
InformationInformational

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
Finding FieldBurp Source
TitleIssue name
DescriptionIssue detail
SeveritySeverity rating
RemediationRemediation detail
EvidenceRequest/response
URLAffected endpoint
ParameterVulnerable parameter

When evidence is included:

  • HTTP requests captured
  • HTTP responses captured
  • Highlighted injection points
  • Payload details
Issue CategoryExamples
InjectionSQL injection, XSS, Command injection
AuthenticationSession issues, weak passwords
InformationVersion disclosure, verbose errors
ConfigurationMissing headers, insecure cookies
CryptographyWeak TLS, insecure algorithms

After import, enhance findings:

  1. Verify the vulnerability manually
  2. Add specific evidence (screenshots)
  3. Use AI to improve descriptions
  4. Add business context

Burp Scanner may report false positives:

  1. Import all findings
  2. Review each finding
  3. Mark false positives appropriately
  4. Delete or change status

Reduce false positives by:

  • Only importing High/Medium severity
  • Requiring Certain/Firm confidence
  • Reviewing preview before import

When same issue found on multiple endpoints:

  • Group as single finding
  • List all affected URLs
  • Maintain evidence for each
  • Merge by issue type: Same vulnerability = one finding
  • Keep separate: Each instance = separate finding
  • Hybrid: User reviews suggestions

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

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

For best import results:

  1. Active scan complete target
  2. Review findings in Burp first
  3. Remove obvious false positives
  4. Export remaining issues
  5. Import into NEURO

Consider importing in stages:

  1. High severity + Certain confidence first
  2. Verify and enhance those findings
  3. Add Medium severity
  4. Review Low/Info as needed

For important findings:

  1. Import finding without evidence
  2. Capture clean screenshots manually
  3. Add annotated evidence
  4. Write specific reproduction steps

“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

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