Integration · Security scanning
Trivy + OrchestrAI
Catalog exported 2026-09-02 · Trivy website
Scan container images, repos, and directories with Trivy from chat and generate an SBOM on request.
OrchestrAI exposes 5 Trivy operations: 5 are low-risk (read-only or low-impact).
What teams use it for
Before a release someone asks OrchestrAI to scan ghcr.io/acme/api:1.14 with Trivy and list the critical CVEs with fixed versions available, or to scan a git repository for vulnerable dependencies and hand back the report as JSON or a table. Generating a software bill of materials for an image satisfies a customer security questionnaire without a separate toolchain. Every Trivy operation is read-only and low risk. Trivy's misconfiguration and secret scanning modes, and scanning a live Kubernetes cluster, are not exposed, so an IaC misconfiguration pass needs Checkov or the trivy CLI directly.
Every Trivy operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Trivy Generate SBOM |
Generate Software Bill of Materials | Low risk | No |
Trivy Get Report |
Get scan report in various formats | Low risk | No |
Trivy Scan Container Image |
Scan container image for vulnerabilities | Low risk | No |
Trivy Scan Filesystem |
Scan filesystem/directory for vulnerabilities | Low risk | No |
Trivy Scan Repository |
Scan git repository for vulnerabilities | Low risk | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
What you connect
No Trivy-specific credential; these operations run against your connected cloud account. Connected-service tokens are envelope-encrypted with a per-record key wrapped by a cloud KMS.
Prompts that work
- Scan ghcr.io/acme/api:1.14 with Trivy and show only critical and high CVEs that have a fix
- Generate a CycloneDX SBOM for the checkout-service:latest image
- Scan the payments-service repo for vulnerable dependencies
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI scan a Docker image with Trivy before I deploy it?
- Yes, trivy_scan_image runs against the image reference you give and trivy_get_report returns the findings in the format you ask for. Both are low-risk, read-only operations.
- Does the Trivy integration check Terraform or Kubernetes manifests for misconfigurations?
- No, The five Trivy operations cover image, filesystem, and repository vulnerability scans, report retrieval, and SBOM generation. Misconfiguration scanning is not included.
- How does OrchestrAI authenticate to Trivy?
- You add a Trivy credential once in the connections screen. It is envelope-encrypted with a per-record key wrapped by a cloud KMS and is only decrypted inside the run that needs it.
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.