Nessus Import
Nessus Import
Section titled “Nessus Import”Import Nessus scan results to bring vulnerability findings and asset information into your NEURO projects. Automatically map Nessus severity ratings and include remediation guidance.
Overview
Section titled “Overview”Nessus is a widely-used vulnerability scanner. NEURO imports:
- Vulnerability findings
- Asset information
- CVSS scores
- Remediation guidance
- Plugin output
Supported Formats
Section titled “Supported Formats”| Format | Extension | Recommended |
|---|---|---|
| Nessus native | .nessus | - Yes |
| Nessus CSV | .csv | Partial support |
Exporting from Nessus
Section titled “Exporting from Nessus”Export .nessus File
Section titled “Export .nessus File”- Open your Nessus scan
- Click Export
- Select Nessus format
- Choose All results or specific hosts
- Download the
.nessusfile
Export Options
Section titled “Export Options”For best import results:
- Include all findings
- Export as .nessus (not PDF/HTML)
- Include plugin output if needed
Importing Nessus Results
Section titled “Importing Nessus Results”Step-by-Step
Section titled “Step-by-Step”- Open your project in NEURO
- Navigate to Findings tab
- Click Import → Nessus
- Upload your
.nessusfile - Configure import options:
- Severity threshold
- Include informational?
- Import assets?
- Review findings preview
- Click Import
Import Options
Section titled “Import Options”| Option | Description |
|---|---|
| Minimum Severity | Lowest severity to import |
| Include Informational | Import info-level findings |
| Import Assets | Create assets from scan targets |
| Deduplicate | Merge similar findings |
| Add Tags | Tag imported findings |
Severity Mapping
Section titled “Severity Mapping”Nessus to NEURO severity:
| Nessus Severity | NEURO Severity |
|---|---|
| Critical | Critical |
| High | High |
| Medium | Medium |
| Low | Low |
| Info | Informational |
CVSS Score Mapping
Section titled “CVSS Score Mapping”- Nessus CVSS scores are imported directly
- Base scores preserved
- Vector strings included when available
Imported Finding Data
Section titled “Imported Finding Data”Fields Populated
Section titled “Fields Populated”| Finding Field | Nessus Source |
|---|---|
| Title | Plugin name |
| Description | Plugin description |
| Severity | Risk factor / CVSS |
| CVSS Score | CVSS base score |
| Remediation | Solution text |
| References | CVE, BID, links |
| Affected Assets | Target hosts |
Additional Data
Section titled “Additional Data”- Plugin ID
- Plugin family
- Plugin output
- Port/protocol
- First/last seen dates
Handling Duplicates
Section titled “Handling Duplicates”Same Finding, Multiple Hosts
Section titled “Same Finding, Multiple Hosts”When a finding affects multiple hosts:
- Single finding created
- All affected hosts linked
- Port details preserved per host
Previous Import
Section titled “Previous Import”When importing over existing data:
- Matched by plugin ID + project
- Updates existing if found
- Creates new if not found
- Option to skip existing
Finding Quality Enhancement
Section titled “Finding Quality Enhancement”After Import
Section titled “After Import”Imported findings may need:
- Description enhancement - Use AI to improve
- Context addition - Add project-specific details
- Evidence - Add screenshots if available
- Verification - Confirm finding validity
Using AI Enhancement
Section titled “Using AI Enhancement”- Open imported finding
- Click Enhance with AI
- Review improvements
- Apply changes
Import Filtering
Section titled “Import Filtering”Severity Filtering
Section titled “Severity Filtering”Import only findings above a threshold:
- Critical only
- High and above
- Medium and above
- All findings
Plugin Family Filtering
Section titled “Plugin Family Filtering”Filter by Nessus plugin family:
- Web servers
- Databases
- Windows
- Linux
- Network
Host Filtering
Section titled “Host Filtering”Import findings for specific hosts only:
- Select target IPs
- Use IP ranges
- Exclude specific hosts
Best Practices
Section titled “Best Practices”Before Import
Section titled “Before Import”- Review scan coverage - Ensure complete scan
- Export correct format - Use .nessus, not PDF
- Create target project - Have project ready
- Set severity threshold - Decide what to import
Import Strategy
Section titled “Import Strategy”For large scans:
- Start with Critical/High - Import highest severity first
- Review and enhance - Quality check top findings
- Add Medium - Import medium severity
- Informational last - If needed for completeness
After Import
Section titled “After Import”- Deduplicate - Remove false duplicates
- Verify key findings - Confirm critical issues
- Add evidence - Screenshot important findings
- Enhance descriptions - Use AI for better content
Troubleshooting
Section titled “Troubleshooting”Import Errors
Section titled “Import Errors”“Invalid file format”
- Ensure .nessus format (not CSV/PDF)
- Check file isn’t corrupted
- Re-export from Nessus
“No findings found”
- Check scan actually found vulnerabilities
- Verify severity threshold isn’t too high
- Check for empty scan
“File too large”
- Export specific hosts only
- Import in batches
- Contact support for limit increase
Data Quality Issues
Section titled “Data Quality Issues”Missing descriptions
- Some plugins have minimal text
- Use AI enhancement
- Manually add context
Wrong severity
- Nessus may rate differently than your assessment
- Adjust severity after import
- Document reasoning
Duplicate findings
- Review deduplication settings
- Merge manually if needed
- Use bulk operations
Advanced: Nessus API Integration
Section titled “Advanced: Nessus API Integration”For automated workflows, consider API integration:
# Example: Export scan via API and importcurl -X GET "https://nessus:8834/scans/{scan_id}/export" \ -H "X-ApiKeys: accessKey=xxx;secretKey=xxx" \ -o scan.nessus
# Then upload to NEURO via APIcurl -X POST "https://{tenant}.nforged.com/api/v1/projects/{id}/import/nessus" \ -H "Authorization: Bearer {token}" \ -F "file=@scan.nessus"See API Integration for details.
Next: Learn about Burp Suite Import