Overview Q & A Rating & Review
trivy
An Azure DevOps Pipelines Task for Trivy , with an integrated UI.
Installation
Install the Trivy task in your Azure DevOps organization (hit the Get it free button above).
Add the task to your azure-pipelines.yml in a project where you'd like to run trivy:
- task: trivy@1
Configuration
You can supply several inputs to customise the task.
Input
Description
versionThe version of Trivy to use. Currently defaults to latest.
dockerRun Trivy using the aquasec/trivy docker image. Alternatively the Trivy binary will be run natively. Defaults to true.
loginDockerConfigSet this to true if the Docker login task is used to access private repositories. Defaults to false.
debugEnable debug logging in the build output.
pathThe path to scan relative to the root of the repository being scanned, if an fs scan is required. Cannot be set if image is set.
severitiesThe severities (CRITICAL,HIGH,MEDIUM,LOW,UNKNOWN) to include in the scan (comma sperated). Defaults to CRITICAL,HIGH,MEDIUM,LOW,UNKNOWN.
ignoreUnfixedWhen set to true all unfixed vulnerabilities will be skipped. Defaults to false.
imageThe image to scan if an image scan is required. Cannot be set if path is set.
exitCodeThe exit-code to use when Trivy detects issues. Set to 0 to prevent the build failing when Trivy finds issues. Defaults to 1.
aquaKeyThe Aqua API Key to use to link scan results to your Aqua Security account (not required) .
aquaSecretThe Aqua API Secret to use to link scan results to your Aqua Security account (not required) .
optionsAdditional flags to pass to trivy. Example: --timeout 10m0s (not required) .
Example of scanning multiple targets
trigger:
- main
pool:
vmImage: ubuntu-latest
jobs:
- job: Scan the local project
steps:
- task: trivy@1
inputs:
path: .
- job: Scan the ubuntu image
steps:
- task: trivy@1
inputs:
image: ubuntu
Scanning Images in Private Registries
You can scan images in private registries by using the image input after completing a docker login. For example:
steps:
- task: Docker@2
displayName: Login to ACR
inputs:
command: login
containerRegistry: dockerRegistryServiceConnection1
- task: trivy@1
inputs:
image: my.private.registry/org/my-image:latest
# Needed to access private repo
loginDockerConfig: true
