Findings and assets

Findings

Findings collects every issue Nebula reports, with its severity, the affected asset and the evidence that supports it. Open a finding to see the full investigation, reproduction steps and remediation guidance, and print it for a ticket or a meeting.

Triage queues

Queue	Contains
Open	Findings that still need action.
All findings	Everything, in any state.
Needs owner	Open findings nobody has picked up.
Work in progress	Findings someone is working on.
Closed	Fixed or accepted findings.
Out of scope	Findings outside the confirmed scope.
Duplicates	Findings that repeat another one.

Filter by severity to focus on Critical and High first, or group findings by domain to see where risk concentrates.

Note

A finding moves to Closed when your team closes it. The console never infers that a fix is verified; use a retest, such as a Weekly fix verification schedule, to confirm it.

Send findings to your tools

• With Jira connected, ask an engineer to file a finding as a Jira issue. Nothing is ticketed automatically.
• With Slack connected, findings alerts post to your channel.

Assets

Assets is your inventory of hosts and services: what Nebula discovered and what you added. Each asset shows its type, domain, assessment state, linked findings, recorded ports, HTTP status, IP addresses, technologies and when it was last seen.

Export the inventory as CSV for your CMDB or a spreadsheet. The export quotes every cell and neutralizes values that a spreadsheet would treat as formulas, because discovered values come from outside your organization.