configure-container-scan

Automate container image scan step insertion into Harness pipelines.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill configure-container-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-container-scan
Source: https://github.com/harness/harness-skills/tree/main/skills/configure-container-scan
Command: npx skills add https://github.com/harness/harness-skills --skill configure-container-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the integration of container image scanning into your Harness pipelines, ensuring vulnerabilities are detected early.

Core Features & Use Cases

  • Supports multiple scanners (Harness SCA, Aqua Trivy, Grype, Snyk, Prisma Cloud, Anchore, Black Duck, Wiz) to cover diverse security needs.
  • Can insert the scan step into an existing CI stage or create a dedicated SecurityTests stage for isolated scanning.
  • Generates the appropriate Harness STO step YAML and handles required authentication details for commercial scanners.

Quick Start

Provide your pipeline name, image details, and preferred scanner to configure a container image scan.

Frequently Asked Questions about configure-container-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a container image scan to a Harness pipeline?

To add a container image scan to a Harness pipeline, you provide your pipeline name, image details, and preferred scanner. The configuration generates the appropriate Harness STO step YAML to automate vulnerability detection.

Can I use Aqua Trivy or Snyk for container scanning in Harness STO?

Yes, you can use Aqua Trivy, Snyk, Grype, Prisma Cloud, Anchore, Black Duck, Wiz, or Harness SCA for container scanning. The configuration generates the appropriate STO step YAML with proper authentication blocks when credentials exist.

Does the container scanner insert into an existing CI stage or create a new one?

The container scanner can insert the scan step directly into an existing CI stage. Alternatively, it can create a dedicated SecurityTests stage to isolate your container image scanning workflow within the pipeline.

What details are required to configure a commercial scanner in Harness pipelines?

Configuring a commercial scanner requires selecting your scanner, providing image registry details, and supplying credentials. The configuration uses these inputs to generate Harness STO step YAML with proper authentication blocks.

Why generate dedicated STO step YAML for container image vulnerability scanning?

Generating dedicated STO step YAML for container image vulnerability scanning ensures vulnerabilities are detected early in the pipeline. It standardizes security testing across supported scanners like Wiz, Anchore, and Black Duck.