> 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/get-started/connect-your-environment.md).

# Connect Your Environment

Connect your source code so Konvu can assess findings in context.

Connecting your environment gives Konvu the context it needs to assess your findings accurately. Without environment data, Konvu can only work with the vulnerability metadata from your scanners. With it, Konvu can determine whether vulnerabilities are actually reachable and exploitable in your specific setup.

## Source Code (required)

Connect your SCM (GitHub or GitLab) so Konvu can analyze whether vulnerable dependencies are actually reachable in your codebase. Konvu identifies your technology stack -- languages, frameworks, operating systems, package managers -- and cross-references it against exploit conditions to filter out inapplicable findings.

Two paths:

* [**Managed Analysis**](/konvu/get-started/connect-your-environment/source-code/managed-analysis.md) -- Install a GitHub App or connect GitLab. Konvu handles the analysis infrastructure.
* [**Self-Hosted Analysis**](/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis.md) -- Deploy the analysis components in your own Kubernetes cluster for full control over code access.

[Set up source code analysis](/konvu/get-started/connect-your-environment/source-code.md)

## Cloud (optional)

Connect your AWS account so Konvu can read container vulnerability findings from AWS Inspector and Amazon ECR basic scanning, including the images in your Amazon ECR container registry.

[Set up cloud connections](/konvu/get-started/connect-your-environment/cloud.md)

## Next steps

Once your environment is connected, [triage your findings](/konvu/triage-and-remediation/exploitability-assessment.md) to see which vulnerabilities are actually exploitable.


---

# 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/get-started/connect-your-environment.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.