Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Results & findings

Results & findings

Why aren't any of my findings marked Confirmed?

Quick answer

Confirmed means an exploitation agent proved the issue against the live target. If Run exploitation phase is off, the scan is static analysis only, so nothing reaches Confirmed. A login the scan could not use, or an app it could not reach, gives the same result.

Why this happens

Proof comes from the fourth phase of a scan. For each hypothesis, an exploitation agent tries to demonstrate the issue safely against the live target, using a real browser. It captures the request, the response, the payload and, where it helps, a screenshot. Each finding then gets a grade of Confirmed, Likely or Unconfirmed, depending on how strongly the agent proved the issue.

So Confirmed needs that phase to run and to succeed. It can fail to do so for three reasons:

  • The phase was off. The tooltip on the checkbox says that leaving it clear means "SAST only", which is static source-code analysis with no live testing.
  • The agents could not sign in. Without a working role, they only reach public pages.
  • The app was out of reach. A cloud scan cannot open an internal URL.

How to fix it

  1. Go to Scan Profiles and click the pencil icon on the profile you used.
  2. On Scope, tick Run exploitation phase. It is on by default, so someone may have cleared it.
  3. On Authentication, check that a role exists if the app needs a login. Use Complete authentication to test an OAuth 2.0 role.
  4. Check Scan location. For an app on a private network, which the Cyberlop cloud cannot reach, choose a self-hosted scan agent that sits inside that network.
  5. Click Save, then Scan. Open the new findings and read the Status field.

Still not working?

Some findings stay Likely even after a full run. A flaw can be real and still be hard to demonstrate safely on a live system, so the agent stops short of forcing it. Read the Evidence tab to see what the agent did try. Static-only findings are still useful. They point to a file and line, which gives your developers a place to start even before anything has been proven live. Our page on the exploitation phase has more, and the status values explain each grade. Profile looks right and still nothing is Confirmed? Contact us. The exploitation phase tutorial goes deeper.

Full tutorial

The exploitation phase: on or off, and safe in production

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.