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 / Getting started

Getting started

What's the difference between a target, a scan profile and a scan?

Quick answer

A target is the application you test. A scan profile is a reusable configuration that belongs to one target: scope, logins and reporting rules. A scan is one run of a profile, ending as Completed, Failed or Cancelled. One target can have many profiles, and each profile many scans.

The short version

Think of it as what, how and when, in that order, with each one resting on the one before it. The target is what you test. The scan profile is how. The scan is each time you run it.

How it works in Cyberlop

TermWhat it holdsCan you change it?
TargetName, Main URL, backend URLs, repository and branch, environment, teamNo. Delete it and create it again.
Scan profileVulnerability classes, exploitation on or off, scan location, focus and avoid rules, login roles, reporting rulesYes, but its target is fixed.
ScanResult, trigger, cost, tokens, lines of code, findingsNo. It is a record of one run.

A profile belongs to one target, and that link is fixed the moment you create the profile, so a profile can never be pointed at another application later. To test another target, make another profile.

A scan's result is Completed, Failed or Cancelled. Its trigger is Manual, or it can come from a schedule or from CI.

Findings are kept per target, not per scan. When you delete a scan, the target's findings stay. When you delete a target, its profiles, schedules, scans and findings all go with it.

Two related terms are worth knowing. A group collects profiles, by choice or by tag. A schedule runs a profile once or on a repeat.

What to do next

  1. Add a target with these steps.
  2. Build a profile from the target page, which preselects the target.
  3. Press Scan, then read results in Recent Scans.

A tidy habit is to name profiles after their purpose, such as a quick check or a full audit, and to keep one target per application and environment. That way the list on the target page reads like a menu of ways to test it.

See also why targets cannot be edited and the key terms tutorial. Unsure? Contact us.

Full tutorial

Cyberlop key terms: targets, profiles, scans and issues

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.