Home / Help centre / Targets & repositories
Targets & repositories
What do the coloured dots in the Results column of the Targets list mean?
Each coloured dot in the Results column stands for one severity level, and the number beside it counts the findings at that level. Red is critical, orange high, violet medium, blue low, grey informational and dark grey best practice. A dash means never scanned.
The short version
The Results column is a quick health check for each target. Every dot has a colour and a count, so you can see how many findings a target has and how serious they are without opening it.
How it works in Cyberlop
| Dot colour | Severity |
|---|---|
| Red | Critical |
| Orange | High |
| Violet | Medium |
| Blue | Low |
| Grey | Informational |
| Dark grey | Best practice |
Only the severities a target actually has show up as dots, so a target with no critical findings has no red dot. The number beside a dot counts findings at that level. It does not count scans, so a target scanned ten times still shows only its current set of findings.
The dots come from the rolling set of issues for the target, which persist across scans. A fixed issue is marked fixed when a later scan no longer finds it. Severity is not the same as confidence. Severity says how bad a finding is, and confidence says how sure the scan is about it.
What to do next
Open the target, then use Issues to filter by severity, class or target and read each finding. Start with red and orange, because those are the findings most worth fixing first. See why a target shows a dash if a row has no dots, or read about severity and confidence. Need help reading a result? Use /contact.
Related questions
- Why does a target show a dash in the Results column?
- How do I see how many findings are still open across all my targets?
- How do I see findings for just one target?
- How do I see a target's repository, branch and environment?
- How do I start a scan straight from the Targets list?
Severity vs confidence in Cyberlop: how to read and prioritise findings
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.