Import Data

Hawkra can import scan results from popular security tools, automatically creating assets, ports, and vulnerabilities in your workspace. This eliminates the need to manually enter findings from your scans and ensures that your workspace stays synchronized with your actual assessment data.

Supported Formats

Format	File Extension	Available To
Nmap XML	.xml	All tiers
Nessus	.nessus, .xml	Premium / Self-Hosted
OpenVAS	.xml	Premium / Self-Hosted
OWASP ZAP	.xml	Premium / Self-Hosted
BloodHound JSON	.json, .zip	Premium / Self-Hosted
WingSpan (JSON)	.json	Premium / Self-Hosted
Nuclei (JSON)	.json	Premium / Self-Hosted

Tier Restrictions

Nmap imports are available on all tiers; every other format requires Premium or Self-Hosted. Attempting to import a restricted format on a lower tier returns an error message indicating that a Premium subscription is required.

How It Works

Imports are processed as background jobs. When you submit an import, Hawkra creates a job record, queues it to a Redis job queue, and a background worker picks it up for processing. This means you can continue working in the platform while your import runs. The import job tracks its progress and provides detailed results when complete.

Each import is scoped to a specific network within a workspace. The assets, ports, and vulnerabilities created by the import are associated with that network.

Import Workflow

1. Choose the network and format -- Open the workspace's Imports tab, pick the network the data belongs to, and choose the import format.
2. Upload the scan file -- Upload the scan output file in the Imports tab. It is stored in encrypted workspace storage.
3. Configure options -- Optionally enable host filtering (ignore hosts with no open ports).
4. Submit -- The import job is created with a Pending status and queued for background processing.
5. Monitor progress -- The import transitions through statuses as it is processed:
   • Pending -- queued, waiting for a worker
   • Processing -- actively being parsed and imported
   • Completed -- finished successfully with result statistics
   • Failed -- an error occurred (error message is provided)

Key Actions

Starting an Import

1. Open the Imports tab of your workspace.
2. Select the target network.
3. Choose the correct import format from the dropdown. Formats your plan does not include are marked (Premium).
4. Upload the scan file.
5. Optionally check Ignore hosts with no open ports to skip hosts that have no port data.
6. Click Import to submit the job.

The system returns the import job with a status of Pending and a 202 Accepted response. The job will be processed in the background.

Permission Required

Starting an import requires the EditAssets permission and an active workspace subscription.

Host Filtering

When the Ignore hosts with no open ports option is enabled, the import parser skips any hosts that do not have associated port data. This is useful for Nmap scans that discover many hosts via ping sweep but only have detailed port information for a subset of them.

Viewing Import History

Navigate to the Imports section of your workspace to see a list of all import jobs. Each entry shows:

• Import Type -- the format that was imported (Nmap, Nessus, etc.)
• Status -- Pending, Processing, Completed, or Failed
• Created Date -- when the import was submitted
• Start / Completion Time -- when processing began and ended

Viewing Import Results

Click on a completed import to see detailed statistics:

Metric	Description
Assets Created	New assets created.
Assets Updated	Existing assets updated.
Assets Skipped	Assets skipped (e.g., host filtering).
Ports Created	New ports recorded.
Ports Updated	Existing ports updated.
Vulnerabilities Created	New vulnerabilities added.
Vulnerabilities Skipped	Duplicates skipped.
Vulnerability Links Created	New vuln-asset associations.

Failed Imports

If an import fails, the job status is set to Failed and an error message is provided describing what went wrong. Common causes include:

• Malformed or corrupt scan files
• Unsupported file format for the selected import type
• Missing required data in the scan file

Review the error message, fix the source file if needed, and submit a new import.

Quota Enforcement

Import jobs respect the asset limit of the workspace owner's tier (15 assets per workspace on Free, 5,000 on Premium). If creating another asset would exceed that limit, the import stops and the job is marked Failed with an error naming the limit. Check your current asset count before running large imports.