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 -- Install a GitHub App or connect GitLab. Konvu handles the analysis infrastructure.
Self-Hosted Analysis -- Deploy the analysis components in your own Kubernetes cluster for full control over code access.
Private packages (optional)
If your applications depend on private packages in GitHub Packages or JFrog, connect the package registry so Konvu can read those dependencies during an assessment. Package access is configured separately from source code access.
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.
Next steps
Once your environment is connected, triage your findings to see which vulnerabilities are actually exploitable.
Last updated

