Trivy
What is Trivy?
Trivy
(tri
pronounced like trigger, vy
pronounced like envy) is a simple and comprehensive vulnerability scanner for containers and other artifacts.
A software vulnerability is a glitch, flaw, or weakness present in the software or in an Operating System.
Trivy
detects vulnerabilities of OS packages (Alpine, RHEL, CentOS, etc.) and application dependencies (Bundler, Composer, npm, yarn, etc.).
Trivy
is easy to use. Just install the binary, and you're ready to scan. All you need to do for scanning is to specify a target such as an image name of the container.
To learn more about the Trivy scanner itself visit Trivy's GitHub Repository.
Deployment
The trivy chart can be deployed via helm:
# Install HelmChart (use -n to configure another namespace)
helm upgrade --install trivy secureCodeBox/trivy
Scanner Configuration
The following security scan configuration example are based on the Trivy Documentation, please take a look at the original documentation for more configuration examples.
Trivy Container Image Scan
Currently we support the follwing 4 scanTypes, corresponding to the trivy scanning modes:
- scanType: "trivy-image"
- parameters:
[YOUR_IMAGE_NAME]
- parameters:
- scanType: "trivy-filesystem"
- parameters:
[YOUR_PATH_TO_FILES]
- parameters:
- scanType: "trivy-repo"
- parameters:
[YOUR_GITHUB_REPO]
- parameters:
- scanType: "trivy-k8s"
- parameters:
[KUBERNETES_RESOURCE]
- parameters:
A complete example of each scanType are listed below in our example docs section.
Simply specify an image name (and a tag) when you use the scanType trivy-image
. But there are also some additional configuration options e.g:
- Filter the vulnerabilities by severities
--severity HIGH,CRITICAL ruby:2.4.0
- Filter the vulnerabilities by type (
os
orlibrary
)--vuln-type os ruby:2.4.0
- Skip update of vulnerability DB:
--skip-update python:3.4-alpine3.9
- Ignore unfixed vulnerabilities:
--ignore-unfixed ruby:2.4.0
By default, Trivy also detects unpatched/unfixed vulnerabilities. This means you can't fix these vulnerabilities even if you update all packages. If you would like to ignore them, use the--ignore-unfixed
option.
A complete scan definition for the secureCodeBox repository may look something like this:
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "trivy-scb"
spec:
scanType: "trivy-image"
parameters:
- bkimminich/juice-shop:v10.2.0
Scanning Many Targets
By default, the docker container of trivy will download the vulnerability database when starting the process. As this download is performed directly from GitHub, you will run into API rate limiting issues after roughly 50 requests. Trivy supports a client-server mode where one process downloads a copy of the vulnerability database and provides it to the others.
This mode is implemented and active by default. A separate Deployment for the trivy server will be created during the installation and the trivy scanTypes are automatically configured to run in client mode and connect to the server.
In case only a single scan or very few are run, and you want to avoid the small performance overhead, client/server mode can be disabled by setting --set="trivyDatabaseCache.enabled=false"
during helm install.
Requirements
Kubernetes: >=v1.11.0-0
Values
Key | Type | Default | Description |
---|---|---|---|
cascadingRules.enabled | bool | false | Enables or disables the installation of the default cascading rules for this scanner |
createAutoDiscoveryScanType | bool | false | Creates a trivy-image-autodiscovery scanType with its own ServiceAccount for the SCB AutoDiscovery, enabled to scan images from both public & private registries. |
imagePullSecrets | list | [] | Define imagePullSecrets when a private registry is used (see: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) |
kubeauditScope | string | "cluster" | Automatically sets up rbac roles for kubeaudit to access the resources it scans. Can be either "cluster" (ClusterRole) or "namespace" (Role) |
parser.affinity | object | {} | Optional affinity settings that control how the parser job is scheduled (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) |
parser.env | list | [] | Optional environment variables mapped into each parseJob (see: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/) |
parser.image.pullPolicy | string | "IfNotPresent" | Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images |
parser.image.repository | string | "docker.io/securecodebox/parser-trivy" | Parser image repository |
parser.image.tag | string | defaults to the charts version | Parser image tag |
parser.resources | object | { requests: { cpu: "200m", memory: "100Mi" }, limits: { cpu: "400m", memory: "200Mi" } } | Optional resources lets you control resource limits and requests for the parser container. See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ |
parser.scopeLimiterAliases | object | {} | Optional finding aliases to be used in the scopeLimiter. |
parser.tolerations | list | [] | Optional tolerations settings that control how the parser job is scheduled (see: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) |
parser.ttlSecondsAfterFinished | string | nil | seconds after which the Kubernetes job for the parser will be deleted. Requires the Kubernetes TTLAfterFinished controller: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/ |
scanner.activeDeadlineSeconds | string | nil | There are situations where you want to fail a scan Job after some amount of time. To do so, set activeDeadlineSeconds to define an active deadline (in seconds) when considering a scan Job as failed. (see: https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-termination-and-cleanup) |
scanner.affinity | object | {} | Optional affinity settings that control how the scanner job is scheduled (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/) |
scanner.backoffLimit | int | 3 | There are situations where you want to fail a scan Job after some amount of retries due to a logical error in configuration etc. To do so, set backoffLimit to specify the number of retries before considering a scan Job as failed. (see: https://kubernetes.io/docs/concepts/workloads/controllers/job/#pod-backoff-failure-policy) |
scanner.env | list | [] | Optional environment variables mapped into each scanJob (see: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/) |
scanner.extraContainers | list | [] | Optional additional Containers started with each scanJob (see: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) |
scanner.extraVolumeMounts | list | [] | Optional VolumeMounts mapped into each scanJob (see: https://kubernetes.io/docs/concepts/storage/volumes/) |
scanner.extraVolumes | list | [] | Optional Volumes mapped into each scanJob (see: https://kubernetes.io/docs/concepts/storage/volumes/) |
scanner.image.pullPolicy | string | "IfNotPresent" | Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images |
scanner.image.repository | string | "docker.io/aquasec/trivy" | Container Image to run the scan |
scanner.image.tag | string | nil | defaults to the charts appVersion |
scanner.nameAppend | string | nil | append a string to the default scantype name. |
scanner.podSecurityContext | object | {} | Optional securityContext set on scanner pod (see: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) |
scanner.resources | object | {} | CPU/memory resource requests/limits (see: https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/, https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/) |
scanner.securityContext | object | {"allowPrivilegeEscalation":false,"capabilities":{"drop":["all"]},"privileged":false,"readOnlyRootFilesystem":false,"runAsNonRoot":false} | Optional securityContext set on scanner container (see: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) |
scanner.securityContext.allowPrivilegeEscalation | bool | false | Ensure that users privileges cannot be escalated |
scanner.securityContext.capabilities.drop[0] | string | "all" | This drops all linux privileges from the container. |
scanner.securityContext.privileged | bool | false | Ensures that the scanner container is not run in privileged mode |
scanner.securityContext.readOnlyRootFilesystem | bool | false | Prevents write access to the containers file system |
scanner.securityContext.runAsNonRoot | bool | false | Enforces that the scanner image is run as a non root user |
scanner.suspend | bool | false | if set to true the scan job will be suspended after creation. You can then resume the job using kubectl resume <jobname> or using a job scheduler like kueue |
scanner.tolerations | list | [] | Optional tolerations settings that control how the scanner job is scheduled (see: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) |
scanner.ttlSecondsAfterFinished | string | nil | seconds after which the Kubernetes job for the scanner will be deleted. Requires the Kubernetes TTLAfterFinished controller: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/ |
trivyDatabaseCache.enabled | bool | true | Enables or disables the use of trivy server in another pod to cache the vulnerability database for all scans. |
trivyDatabaseCache.replicas | int | 1 | amount of replicas to configure for the Deployment |
License
Code of secureCodeBox is licensed under the Apache License 2.0.
CPU architectures
The scanner is currently supported for these CPU architectures:
- linux/amd64
- linux/arm64
- linux/ppc64le
- linux/s390x
Examples
filesystem
This example shows how to use the trivy filesystem
scan with the secureCodeBox. You can use a ìnitContainer
and also volumeMounts
to point to the filesystem you want to scan.
- Scan
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "trivy-filesystem"
spec:
scanType: "trivy-filesystem"
# Define a volume and mount it at /repo in the scan container to have a filesystem in place
volumes:
- name: repo
emptyDir: {}
volumeMounts:
- name: repo
mountPath: "/repo/"
# Define an init container to run the git clone for us
initContainers:
- name: "git-clone"
image: bitnami/git
# Specify that the "repo" volume should also be mounted on the
# initContainer
volumeMounts:
- name: repo
mountPath: "/repo/"
# Clone to /repo in the init container
command:
- git
- clone
# Add access token to the URL for authenticated HTTPS clone
- "https://github.com/yourOrg/yourRepo"
- /repo/
parameters:
- "/repo"
image-juice-shop
This example shows how to use the trivy image
scan with the secureCodeBox.
- Scan
- Findings
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "trivy-juiceshop"
labels:
organization: "OWASP"
spec:
scanType: "trivy-image"
parameters:
- "bkimminich/juice-shop:v10.2.0"
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
[
{
"Target": "bkimminich/juice-shop:v10.2.0 (alpine 3.11.5)",
"Vulnerabilities":
[
{
"VulnerabilityID": "CVE-2020-1967",
"PkgName": "openssl",
"InstalledVersion": "1.1.1d-r3",
"FixedVersion": "1.1.1g-r0",
"Layer":
{
"DiffID": "sha256:beee9f30bc1f711043e78d4a2be0668955d4b761d587d6f60c2c8dc081efb203",
},
"Title": "openssl: Segmentation fault in SSL_check_chain causes denial of service",
"Description": 'Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).',
"Severity": "HIGH",
"References":
[
"http://www.openwall.com/lists/oss-security/2020/04/22/2",
"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967",
"https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=eb563247aef3e83dda7679c43f9649270462e5b1",
"https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44440",
"https://lists.apache.org/thread.html/r66ea9c436da150683432db5fbc8beb8ae01886c6459ac30c2cea7345@%3Cdev.tomcat.apache.org%3E",
"https://lists.apache.org/thread.html/r94d6ac3f010a38fccf4f432b12180a13fa1cf303559bd805648c9064@%3Cdev.tomcat.apache.org%3E",
"https://lists.apache.org/thread.html/r9a41e304992ce6aec6585a87842b4f2e692604f5c892c37e3b0587ee@%3Cdev.tomcat.apache.org%3E",
"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XVEP3LAK4JSPRXFO4QF4GG2IVXADV3SO/",
"https://security.FreeBSD.org/advisories/FreeBSD-SA-20:11.openssl.asc",
"https://security.gentoo.org/glsa/202004-10",
"https://security.netapp.com/advisory/ntap-20200424-0003/",
"https://www.debian.org/security/2020/dsa-4661",
"https://www.openssl.org/news/secadv/20200421.txt",
"https://www.synology.com/security/advisory/Synology_SA_20_05_OpenSSL",
],
},
],
},
{"Target": "juice-shop/frontend/package-lock.json", "Vulnerabilities": null},
{
"Target": "juice-shop/package-lock.json",
"Vulnerabilities":
[
{
"VulnerabilityID": "NSWG-ECO-428",
"PkgName": "base64url",
"InstalledVersion": "0.0.6",
"FixedVersion": "\u003e=3.0.0",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "Out-of-bounds Read",
"Description": "`base64url` allocates uninitialized Buffers when number is passed in input on Node.js 4.x and below",
"Severity": "HIGH",
"References":
[
"https://github.com/brianloveswords/base64url/pull/25",
"https://hackerone.com/reports/321687",
],
},
{
"VulnerabilityID": "NSWG-ECO-17",
"PkgName": "jsonwebtoken",
"InstalledVersion": "0.1.0",
"FixedVersion": "\u003e=4.2.2",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "Verification Bypass",
"Description": 'It is possible for an attacker to bypass verification when "a token digitally signed with an asymetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family)" [1]',
"Severity": "HIGH",
"References":
[
"https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/",
"https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687",
"https://www.timmclean.net/2015/02/25/jwt-alg-none.html",
],
},
{
"VulnerabilityID": "NSWG-ECO-17",
"PkgName": "jsonwebtoken",
"InstalledVersion": "0.4.0",
"FixedVersion": "\u003e=4.2.2",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "Verification Bypass",
"Description": 'It is possible for an attacker to bypass verification when "a token digitally signed with an asymetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family)" [1]',
"Severity": "HIGH",
"References":
[
"https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/",
"https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687",
"https://www.timmclean.net/2015/02/25/jwt-alg-none.html",
],
},
{
"VulnerabilityID": "CVE-2016-1000223",
"PkgName": "jws",
"InstalledVersion": "0.2.6",
"FixedVersion": "\u003e=3.0.0",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "Forgeable Public/Private Tokens",
"Description": "Since \"algorithm\" isn't enforced in `jws.verify()`, a malicious user could choose what algorithm is sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants.\n\nIn addition, there is the `none` algorithm to be concerned about. In versions prior to 3.0.0, verification of the token could be bypassed when the `alg` field is set to `none`.\n\n*Edit ( 7/29/16 ): A previous version of this advisory incorrectly stated that the vulnerability was patched in version 2.0.0 instead of 3.0.0. The advisory has been updated to reflect this new information. Thanks to Fabien Catteau for reporting the error.*",
"Severity": "HIGH",
"References":
[
"https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/",
"https://github.com/brianloveswords/node-jws/commit/585d0e1e97b6747c10cf5b7689ccc5618a89b299#diff-4ac32a78649ca5bdd8e0ba38b7006a1e",
],
},
{
"VulnerabilityID": "CVE-2018-16487",
"PkgName": "lodash",
"InstalledVersion": "2.4.2",
"FixedVersion": "\u003e=4.17.11",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "lodash: Prototype pollution in utilities function",
"Description": "A prototype pollution vulnerability was found in lodash \u003c4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.",
"Severity": "HIGH",
"References":
[
"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16487",
"https://hackerone.com/reports/380873",
"https://security.netapp.com/advisory/ntap-20190919-0004/",
"https://www.npmjs.com/advisories/782",
],
},
{
"VulnerabilityID": "CVE-2018-3721",
"PkgName": "lodash",
"InstalledVersion": "2.4.2",
"FixedVersion": "\u003e=4.17.5",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "lodash: Prototype pollution in utilities function",
"Description": 'lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.',
"Severity": "MEDIUM",
"References":
[
"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3721",
"https://github.com/lodash/lodash/commit/d8e069cc3410082e44eb18fcf8e7f3d08ebe1d4a",
"https://hackerone.com/reports/310443",
"https://security.netapp.com/advisory/ntap-20190919-0004/",
],
},
{
"VulnerabilityID": "CVE-2016-4055",
"PkgName": "moment",
"InstalledVersion": "2.0.0",
"FixedVersion": "\u003e=2.11.2",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "moment.js: regular expression denial of service",
"Description": 'The duration function in the moment package before 2.11.2 for Node.js allows remote attackers to cause a denial of service (CPU consumption) via a long string, aka a "regular expression Denial of Service (ReDoS)."',
"Severity": "HIGH",
"References":
[
"http://www.openwall.com/lists/oss-security/2016/04/20/11",
"http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html",
"http://www.securityfocus.com/bid/95849",
"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4055",
"https://lists.apache.org/thread.html/10f0f3aefd51444d1198c65f44ffdf2d78ca3359423dbc1c168c9731@%3Cdev.flink.apache.org%3E",
"https://lists.apache.org/thread.html/17ff53f7999e74fbe3cc0ceb4e1c3b00b180b7c5afec8e978837bc49@%3Cuser.flink.apache.org%3E",
"https://lists.apache.org/thread.html/52bafac05ad174000ea465fe275fd3cc7bd5c25535a7631c0bc9bfb2@%3Cuser.flink.apache.org%3E",
"https://lists.apache.org/thread.html/54df3aeb4239b64b50b356f0ca6f986e3c4ca5b84c515dce077c7854@%3Cuser.flink.apache.org%3E",
"https://nodesecurity.io/advisories/55",
"https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS",
"https://www.tenable.com/security/tns-2019-02",
],
},
{
"VulnerabilityID": "CVE-2016-1000237",
"PkgName": "sanitize-html",
"InstalledVersion": "1.4.2",
"FixedVersion": "\u003e=1.4.3",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "XSS - Sanitization not applied recursively",
"Description": "sanitize-html before 1.4.3 has XSS.",
"Severity": "MEDIUM",
"References":
[
"https://github.com/punkave/sanitize-html/issues/29",
"https://nodesecurity.io/advisories/135",
"https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000237.json",
],
},
{
"VulnerabilityID": "NSWG-ECO-154",
"PkgName": "sanitize-html",
"InstalledVersion": "1.4.2",
"FixedVersion": "\u003e=1.11.4",
"Layer":
{
"DiffID": "sha256:6de27bb627f066285f0628172e686caf3e388a3bf266606c88d619d87d14aae3",
},
"Title": "Cross Site Scripting",
"Description": "Sanitize-html is a library for scrubbing html input of malicious values.\n\nVersions 1.11.1 and below are vulnerable to cross site scripting (XSS) in certain scenarios:\n\nIf allowed at least one nonTextTags, the result is a potential XSS vulnerability.\nPoC:\n\n```\nvar sanitizeHtml = require('sanitize-html');\n\nvar dirty = '!\u003ctextarea\u003e\u0026lt;/textarea\u0026gt;\u003csvg/onload=prompt`xs`\u0026gt;\u003c/textarea\u003e!';\nvar clean = sanitizeHtml(dirty, {\n allowedTags: [ 'textarea' ]\n});\n\nconsole.log(clean);\n\n// !\u003ctextarea\u003e\u003c/textarea\u003e\u003csvg/onload=prompt`xs`\u003e\u003c/textarea\u003e!\n```",
"Severity": "MEDIUM",
"References":
[
"https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403",
"https://github.com/punkave/sanitize-html/issues/100",
],
},
],
},
]
image-mediawiki
This example shows how to use the trivy image
scan with the secureCodeBox.
- Scan
- Findings
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "trivy-mediawiki"
spec:
scanType: "trivy-image"
parameters:
- "mediawiki:stable"
The findings are too large to display, you may download the file.
k8s
This example shows how to use the trivy k8s
scan with the secureCodeBox.
- Scan
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "trivy-k8s"
spec:
scanType: "trivy-k8s"
parameters:
- "cluster"
repo-github
This example shows how to use the trivy repo
scan with the secureCodeBox.
- Scan
# SPDX-FileCopyrightText: the secureCodeBox authors
#
# SPDX-License-Identifier: Apache-2.0
apiVersion: "execution.securecodebox.io/v1"
kind: Scan
metadata:
name: "trivy-repo-github"
spec:
scanType: "trivy-repo"
parameters:
- "https://github.com/knqyf263/trivy-ci-test"