Compliance & operations
Check scan history and troubleshoot a scan
Use Secorvia Scan History to separate pending, running, completed, failed, and cancelled cloud scans before interpreting findings.
Reviewed
Before you start
Connect a cloud account and trigger a scan. The first scan starts automatically when an account is connected.
Open the relevant scan history
Open Scan History for your organization, or follow the link from a cloud account detail to preserve account scope. Confirm which account the scan belongs to.
Filter by lifecycle state
Use the status filter: Pending, Running, Completed, Failed, or Cancelled. Pending means work has not yet completed; Running means the assessment is still in progress. A failure should be investigated before relying on absence of findings.
Inspect failures with the connection context
Review the information provided for the scan and check the account’s Connection Status and Last Validated. If credentials or permissions changed, correct the connection before starting another assessment.
Verify results after completion
Open Inventory and Findings for the same account after completion. Compare resource Last Seen with the scan and review relevant findings. For graph-based analysis, also ensure the graph has been rebuilt with the current data.
Where you are now
You know whether an assessment completed and whether its findings are current enough for the decision you are making.
WHEN SOMETHING LOOKS OFF
A few things to check
No scan jobs yet
Confirm an account was connected and a scan was triggered.
No jobs match the filter
Clear the status filter and confirm the account scope.
PUT IT INTO PRACTICE
Make your next move in Secorvia.
Open the app and follow along with your own organization.