#030Guide1 min

Understand severity levels

Danger, To fix, To watch: what each level means and what it does not.

Hackaiz team · updated 18/11/2026

Illustration: a team reads a security report and marks priorities.
Illustration: a team reads a security report and marks priorities. Illustrative photo, not a screenshot.

01Three levels, only one in red

Hackaiz sorts each finding into three levels. Only Danger is shown in red, so real urgency stands out instead of being drowned.

  1. 1Danger: an exploitable risk with significant impact, for example data anyone can read. Handle first.
  2. 2To fix: a real weakness, less direct or less severe. Plan it soon.
  3. 3To watch: a signal worth attention that is not a proven flaw on its own.

02What the level does not say

The level describes a finding’s risk, not the state of the whole app. An app with no Danger but low coverage is not necessarily safe. Always read the level together with evidence and coverage.

03Level and confidence

A finding also has a confidence level. When evidence is weak, confidence is lowered rather than the finding removed: you still see it, with what remains to be confirmed.

04How to act

Handle Danger findings touching data or secrets first, then publicly exposed To fix items, then the rest. For each fix, verify it is gone with a new analysis.

Tip: A Danger on an exposed secret key is handled in two steps: rotate the key, then remove the old one from code.

Frequently asked questions

Take the next step

Was this article helpful?

Related articles