> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/monitor-and-deliver/data-forwarding.md).

# Data Forwarding

Send Konvu's assessments to the tools your team already works in, and check that every delivery arrived.

Data forwarding writes Konvu's assessments onto the matching findings in your other security tools, so your team sees them without opening Konvu. Configure it in **Organization Settings > Data Forwarding**.

{% hint style="info" %}
Every signed-in member of a hosted organization can open Data Forwarding and change its settings. It is not available for self-hosted (on-premises) organizations.
{% endhint %}

## Destinations

| Destination                                                                                                             | Finding types                   | What Konvu writes                                                  | Setup                                                   |
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------- |
| [**ArmorCode**](/konvu/get-started/bring-in-findings/armorcode.md#send-assessments-back-to-armorcode)                   | Dependencies (SCA), Code (SAST) | A comment with the assessment, and a `konvu.assessment_result` tag | API key with findings read and bulk update access       |
| [**Wiz**](/konvu/get-started/bring-in-findings/container-and-cloud-scanners/wiz.md#forward-assessments-to-wiz-optional) | Containers                      | A Konvu assessment note on the matching Wiz finding                | Service account with the `update:vulnerabilities` scope |

Konvu only updates findings that already exist in the destination. It never creates findings there, and it never changes a finding's native status or severity.

Konvu does not forward secrets or vulnerability reports, and it has no ticketing (Jira, Linear), webhook, or SIEM destination.

## Turn on forwarding

Connecting a tool in **Integrations** never turns forwarding on. You opt in separately:

1. Open **Organization Settings > Data Forwarding**.
2. Find the destination's row. If it is not connected, select **Connect in Integrations** first.
3. Turn on the switch. Konvu starts sending eligible completed assessments.
4. For ArmorCode, choose **Compact** (the default) or **Detailed** comments. **Compact** summarizes the assessment and evidence. **Detailed** adds the investigation steps and supporting code evidence, which can include file paths and code snippets.

Changes save immediately. Turning the switch off pauses automatic delivery. The connection and anything already written to the destination stay in place.

Importing findings and forwarding assessments are independent. Pausing an ArmorCode import does not stop forwarding, and turning off forwarding does not stop imports.

## Send one assessment

You can send a single assessment without turning on automatic forwarding. Open the finding and select **Send to ArmorCode** (SCA findings) or **Send note to Wiz** (container findings). Review the preview, then send. Sending once never changes your forwarding settings.

See [Send a single assessment](/konvu/get-started/bring-in-findings/armorcode.md#send-a-single-assessment) for the ArmorCode drawer step by step.

## Delivery activity

The **Delivery activity** feed at the bottom of Data Forwarding lists every outgoing delivery, automatic or manual. Filter by **All**, **ArmorCode**, or **Wiz**. The feed refreshes on its own every few seconds.

Each row shows the finding, the delivery status and destination, and when it happened. The destination links to the matching finding in that tool when Konvu has its URL. **N matching findings** means one assessment applied to several findings in the destination.

| Status        | Meaning                                                                                      |
| ------------- | -------------------------------------------------------------------------------------------- |
| **Queued**    | Waiting to be sent.                                                                          |
| **Sending**   | A delivery attempt is in progress. The destination may be rate-limiting or still processing. |
| **Retrying**  | An attempt failed and Konvu will try again.                                                  |
| **Delivered** | The destination accepted the assessment.                                                     |
| **Failed**    | Every attempt failed. The row shows the error when one is available.                         |

A successful import on the Integrations page only confirms that Konvu read findings from a tool. Delivery activity is where you confirm that assessments went back.

## Retries and failures

* **Automatic retries.** Konvu makes up to three delivery attempts, five minutes apart, before marking the delivery **Failed**.
* **Only changed assessments are sent.** Konvu sends an assessment again only when its content changed. If an assessment changes before a delivery goes out, the newer assessment replaces the older one.
* **No matching finding.** If the destination has no finding that matches the Konvu finding, the delivery fails with "No matching finding was found in ArmorCode" and is not retried. For SAST, ArmorCode needs a finding with the same scanner source, scanner finding ID, and repository URL. See [Forward SAST assessments](/konvu/get-started/bring-in-findings/armorcode.md#forward-sast-assessments).
* **Customer notes are preserved.** Konvu skips Wiz findings that already carry a note you wrote.

For ArmorCode-specific problems, see [ArmorCode troubleshooting](/konvu/get-started/bring-in-findings/armorcode.md#troubleshooting).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konvu.com/konvu/triage-and-remediation/monitor-and-deliver/data-forwarding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.