Coverage and partial scans
Every scan records which steps completed, failed and were skipped. A scan that could not finish says so.
Coverage is the part of a security report most tools leave out, and it is the part that decides whether you can trust the rest. AppScan records it per scan and shows it on the report.
- Completed
- The step ran and produced evidence.
- Failed
- The step ran and could not finish - a timeout, a refused connection, a malformed response. The error code is kept.
- Skipped
- The step was not applicable: no repository connected, no lockfile found, the plan does not include it.
- Budget exhausted
- The scan hit its time or work budget before finishing. What was done still counts; what was not is listed.
A scan whose outcome is PARTIAL_COVERAGE tells you what it could not look at. Read that list before treating a short findings list as good news.
Billing follows coverage
A manual scan that ends partial settles at half the credits it reserved rather than charging in full.
Questions
My scan says partial. What should I do?
Open the coverage list. If a step failed because the site was slow or briefly down, run it again. If it was skipped because something is not connected or not on your plan, the report says which.
Am I charged for a scan that failed?
A failed scan releases its reservation. A partial one settles at half. You are never charged in full for work that did not happen.
Something here wrong, missing or out of date? Tell us and we will fix the page.