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

Glossary

The terms these docs use, and what each one means in Konvu.

Findings and sources

Term
Meaning

Finding

Anything Konvu triages: a dependency, code, container, or secret finding, or a vulnerability report. See Finding Types.

Vulnerability report

A finding that arrives as a document: a bug bounty submission, a pentest report, a scanner export, or the output of an AI code security tool. See Vulnerability Reports.

Scanner

A tool that produces findings, such as Snyk, Semgrep, or Wiz.

Integration

A connection between Konvu and another tool, set up on the Integrations page.

Source

Where a finding came from: a scanner, a bug bounty program, an upload, or the API.

Program

The scope and rules a vulnerability report is triaged against.

Triage

Term
Meaning

Triage

Deciding which findings are real and exploitable. Konvu triages with two methods: exploitability assessment and exploit reproduction. See Triage.

Exploitability assessment

The first triage method. An agent checks the conditions for an exploit against your code and environment. See Exploitability Assessment.

Assessment

What an exploitability assessment produces: an assessment result and the evidence behind it.

Assessment result

One of Exploitable, False Positive, Needs input, or Inconclusive. A finding Konvu has not assessed yet is Not assessed.

Exploitability checklist

The conditions that must all hold for a vulnerability to be exploitable. See Vulnerability Enrichment.

Exploit reproduction

The second triage method. Konvu deploys your application in an isolated sandbox and an agent runs the exploit. See Exploit Reproduction.

Reproduction result

One of Reproduced, Not Exploitable, Hardening, or Inconclusive. See Reading a Reproduction.

Sandbox

The isolated environment where Konvu deploys your application for an exploit reproduction. Nothing runs against your infrastructure.

Dismiss

Close a finding as a false positive in Konvu. Konvu can write the dismissal back to your scanner.

Assessment scope

The severities and repositories Konvu assesses automatically.

Remediation and delivery

Term
Meaning

Remediation plan

Konvu's plan to fix a finding: the target version or code change, and what it affects.

Fix pull request

A pull request Konvu opens to fix an exploitable finding. See Fix Pull Requests.

Fix prompt

A prompt you copy into your coding agent to fix a reproduced vulnerability report.

Forwarding

Sending assessments automatically to another tool, such as ArmorCode or Wiz. See Data Forwarding.

Delivery

One assessment sent to a destination, listed under Delivery activity.

Write-back

Updating a finding's state in your scanner from Konvu, such as a dismissal.

Your account

Term
Meaning

Organization

Your company's Konvu tenant. Settings that apply to everyone live under Organization Settings.

Credits

The budget that pays for assessments and reproductions. One balance per organization, shared by every product. See Assessment Credits.

Source code analysis

How Konvu reads your repositories once connected, either managed by Konvu or self-hosted. See Connect Your Environment.

Last updated