Executes the Boost Security Scanner cli tool to scan repositories for vulnerabilities and uploads results to the Boost Security API.
Add the following to your azure-pipelines.yml
:
variables:
- group: boost-prod
- name: api_token
value: $[variables.BOOST_API_TOKEN]
steps:
- checkout: self
clean: "true"
fetchDepth: "1"
persistCredentials: "true"
- task: BoostSecurityScan@1
inputs:
apiToken: $(api_token)
registryModule: boostsecurityio/native-scanner
Additional CLI args to pass to the boost
cli.
Enable or disable boost uploading results to the boost api
Overrides the API endpoint url
The Boost Security API token secret.
NOTE: We recommend you not put the API token directly in your pipeline.yml file. Instead, it should be exposed via a secret.
Overrides the cli version to download when performing scans. If undefined, this will default to pulling "1".
Ignore any non-zero exit status and always return a success.
Change the CLI logging level.
The name of the main branch that PRs would merge into. This is automatically detected by querying the git server.
Optional command to execute prior to scanning. This may be used to generate additional files that are not tracked in git.
The relative path towards a module within the Scanner Registry. To streamline the configuration, both the scanners prefix and module.yaml suffix may be omitted.
Optional identifier to uniquely identify the scanner
Optional identifier to identify a monorepo component
Optional path within the git repository to execute scanners in.
When this parameter is specified, you must also provide a scan_label
to identify the component.
The optional timeout after which the Github check will be marked as failed. This defaults to 120 seconds.
The optional timeout for non-main scans after which the Github check will be marked as failed. This defaults to 120 seconds.
The optional timeout for main scans after which the Github check will be marked as failed. This defaults to 2 hours.
Optional path to change into before executing any commands.