For the complete documentation index, see llms.txt. This page is also available as Markdown.

Finding Types

What Konvu does for each kind of finding, from assessment to reproduction and fixes.

Konvu handles five kinds of findings. Each follows the same path: bring it in, triage it, fix it. What Konvu checks, and what it can do after triage, depends on the type. Each page below covers one type end to end.

Assessed
Reproduced
Fix pull requests
Write-back to source

Yes

Early access

Yes

Dismissals, assessments (ArmorCode)

Yes

Early access, CodeQL only

Yes

Dismissals (CodeQL, GitLab), assessments (ArmorCode)

Containers (beta)

Yes

No

No

Assessment notes (Wiz)

Validity, impact, exposure

No

No

No

Triage against program rules

Yes

No, fix prompt instead

No

What each type checks

  • Dependencies: whether the conditions for exploiting the vulnerability hold in your code: installed version, environment, reachability, and attacker-controlled input.

  • Code: where the flagged input comes from, whether an attacker controls it, and what stands between it and the flagged code.

  • Containers: whether the operating-system conditions for the vulnerability hold in the image.

  • Secrets: whether the credential works, what it grants access to, and how an attacker could obtain it.

  • Vulnerability reports: whether the report is in scope, whether it duplicates another report, and whether the exploit fires against your application.

Last updated