Skip to main content

Vulnerability Status: Managing Scenarios and Errors

S
Written by Shannon DeLange
Updated this week

Scenario

What is Visible

Suggested next steps

A scanned asset with no vulnerabilities found

"No actionable vulnerabilities" status is seen in findings by the asset table:

"Congratulations" message is displayed in the Asset -> packages drill-down:

No action is needed. This is the ideal scenario

Scanned asset with vulnerabilities found

Severity status is seen in findings by the asset table:

Asset -> packages drill down table example:

Solve the vulnerability or deactivate monitoring on it to have an asset with no vulnerabilities

An unscanned asset with no vulnerabilities

"No vulnerability data received" status is seen in findings by the asset table

"Get started with managing vulnerabilities" message displayed in asset drill down.

If monitoring vulns on this asset is intended, navigate to the Vulnerabilities Settings and into the Vulnerability Scanners tab to check if the integration is configured correctly. Some integrations allow you to control (enable or disable) vuln scanning separately, aside from the rest of the resources we might be able to fetch. If this is correctly connected, the issue might be on the scanner configuration or on our side.

For AWS-specific instructions, see No vulnerability data received (AWS)

If monitoring is not intended, leave it as it is.

Unscanned asset with vulnerabilities

This scenario is not supported since an unscanned asset will not have vulnerabilities registered anywhere.

No assets to scan

The connected integration appears in the Source dropdown, while "No results found" message displays in the asset drill-down:

If expecting to see assets from the integration:

If there are no scannable assets on the integration, then no action is needed.

Additional Resources