Mend (formerly Whitesource) scanner reference
You can scan container images and repositories using Mend.
Before you begin
To scan a container image, you must have Docker-in-Docker running as a background service in the stage where you're running the scan.
Set up a Docker-in-Docker background step
In the Execution tab, do the following:
- Click Add Step and then choose Background.
- Configure the Background step as follows:
- Dependency Name =
- Container Registry = The Docker connector to download the DinD image. If you don't have one defined, go to Docker connector settings reference.
- Image =
- Under Optional Configuration, select the Privileged checkbox.
Mend step configuration
The recommended workflow is add a Mend step to a Security Tests or CI Build stage and then configure it as described below.
- UI configuration support is currently limited to a subset of scanners. Extending UI support to additional scanners is on the Harness engineering roadmap.
- Each step palette shows only the options that apply to a specific scan. If you're setting up a repository scan, for example, the UI won't show Container Image settings.
- Docker-in-Docker is not required for these steps unless you're scanning a container image. If you're scanning a repository using Bandit, for example, you don't need to set up a Background step running DinD.
- Support is currently limited to Kubernetes and Harness Cloud AMD64 build infrastructures only.
The orchestration mode to use for the scan. The following list includes the UI and YAML values for the supported options.
- Orchestrated A fully-orchestrated scan. A Security step in the Harness pipeline orchestrates a scan and then normalizes and compresses the results.
- Extraction A partially-orchestrated scan. The Security step pulls scan results from an external SaaS service and then normalizes and compresses the data.
- Ingestion Ingestion scans are not orchestrated. The Security step ingest results from a previous scan (for a scan run in an previous step) and then normallizes and compresses the results.
The predefined configuration to use for the scan. All scan steps have at least one configuration.
The target type to scan for vulnerabilities.
- Repository Scan a codebase repo.
- Container Image Scan the layers, libraries, and packages in a container image.
The Identifier that you want to assign to the target you’re scanning in the pipeline. Use a unique, descriptive name such as
An identifier for a specific variant to scan, such as the branch name or image tag. This identifier is used to differentiate or group results for a target. Harness maintains a historical trend for each variant.
The workspace path on the pod running the Security step. The workspace path is
/harness by default.
You can override this if you want to scan only a subset of the workspace. For example, suppose the pipeline publishes artifacts to a subfolder
/tmp/artifacts and you want to scan these artifacts only. In this case, you can specify the workspace path as
The results data file to use when running an Ingestion scan. Generally an Ingestion scan consists of a scan step (to generate the data file) and an ingestion step (to ingest the data file).
The fully-qualified URL to the scanner.
The step and the scanner communicate over SSL by default. Set this to false to disable SSL (not safe).
The scanner API version. Some scanners require this.
The scanner API version. Specify one of the following:
- Username & Password
- API Key
Username to log in to the scanner.
The access token to log in to the scanner. In most cases this is a password or an API key.
You should create a Harness text secret with your encrypted token and reference the secret using the format
<+secrets.getValue(project.container-access-id>. For more information, go to Add and Reference Text Secrets.
The type of key used to look up the object to scan: password or API key.
The name of the scan project as defined in the scanner. This is the also the target name in the Harness UI (Security Tests > Test Targets).
The initial scope for the scan. This should match the format required by the scanner.
Exclusions to the initial scope for the scan. This should match the format required by the scanner.
The version of the scan project, as defined in the scanner.
Log Level, CLI flags, and Fail on Severity
The minimum severity of the messages you want to include in your scan logs. You can specify one of the following:
Fail on Severity
Every Security step has a Fail on Severity setting. If the scan finds any vulnerability with the specified severity level or higher, the pipeline fails automatically. You can specify one of the following:
NONE— Do not fail on severity
The YAML definition looks like this:
fail_on_severity : critical # | high | medium | low | info | none
You can add a
tool_args setting to run the Unified Agent binary with specific command-line arguments. For example, you can exclude certain files from the scan like this:
In the Additional Configuration settings, you can use the following options:
In the Advanced settings, you can use the following options:
Security step configuration (deprecated)
Set up a Mend scan in a Security step
You can set up Mend scans using a Security step: create a CI Build or Security Tests stage, add a Security step, and then add the
setting:value pairs as specified below.
Security step dialog box
Here's an example of how to set up a scan in a Security step.
policy_type are scanner-specific; the other settings are common to scans of container images.
product_domain(optional) — The default is
- Accepted value(s) when
policy_typeis set to
- Accepted value(s) when
policy_typeis set to
fail_on_severity- See Fail on Severity.
You must configure the following settings depending on the product lookup type — i.e., whether you are using the names or tokens to reference the Mend product:
Container image scan settings
The following settings apply to all scanners where the
- accepted value(s):
container_region: AWS default region
- accepted value(s):
|Target Name||Target Type|
Ingestion scan settings
The following settings are required for Security steps where the
target nameThe Identifier that you want to assign to the target you’re scanning in the pipeline. Use a unique, descriptive name such as codebaseAlpha or jsmith/myalphaservice.
variantAn identifier for a specific target to scan, such as the branch name or image tag. This identifier is used to differentiate or group results for a target. Harness maintains a historical trend for each variant.
ingestion_fileThe results data file to use when running an Ingestion scan. You should specify the full path to the data file in your workspace, such as
The following steps outline the general workflow for ingesting scan data into your pipeline:
Specify a shared folder for your scan results, such as
/shared/customer_artifacts. You can do this in the Overview tab of the Security stage where you're ingesting your data.
Create a Run step that copies your scan results to the shared folder. You can run your scan externally, before you run the build, or set up the Run step to run the scan and then copy the results.
Add a Security step after the Run step and add the
ingestion_filesettings as described above.
For a complete workflow description and example, go to Ingest Scan Results into an STO Pipeline.