skills.rest
harness
harnessOFFICIAL
Explore all skills by this author →
WebsiteGitHub

configure-secret-scan

Automate secret scanning integration into existing Harness pipelines via MCP.

80|16|Updated Mar 11, 2026
Search Tags:#MCP#secret detection#secret scanning#pipeline security#Harness STO#Gitleaks#CI/CD secrets
One-click install
npx skills add https://github.com/harness/harness-skills --skill configure-secret-scan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: configure-secret-scan
Source: https://github.com/harness/harness-skills/tree/main/skills/configure-secret-scan
Command: npx skills add https://github.com/harness/harness-skills --skill configure-secret-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add secret detection steps to existing Harness pipelines using STO security scanners. Scans code repositories for exposed credentials, API keys, tokens, and other sensitive information.

Core Features & Use Cases

  • Automatically identify the correct pipeline stage and insert a secret scan step early in CI.
  • Support multiple scanners (Harness Code by default, Gitleaks as a standalone option, and other commercial scanners) with authentication handling for required credentials.
  • Ensure scans run against the repository codebase with access to source via cloneCodebase on CI stages.

Quick Start

Configure secret scanning on an existing pipeline by selecting a scanner and adding the generated step before build steps.

Frequently Asked Questions about configure-secret-scan

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

FAQPage Schema
How do I add secret scanning to a Harness pipeline?▼

Add secret scanning to a Harness pipeline by inserting a security scanner step early in the CI stage before build steps. The step scans the cloned codebase to detect exposed credentials and sensitive information.

Can I use Gitleaks for secret detection in Harness CI?▼

Yes, Gitleaks is supported as a standalone scanner option for secret detection in Harness CI. Harness Code is used by default, and other commercial scanners are also supported with automated authentication handling.

How does secret scanning access the repository codebase in CI stages?▼

Secret scanning accesses the repository codebase in CI stages by running the scanner step with cloneCodebase enabled. This ensures the security scanner has direct access to the repository source code to detect exposed tokens.

Does this secret scan step support commercial scanner authentication?▼

Yes, the secret scan step supports commercial scanner authentication by automatically handling required credentials. This allows you to integrate commercial security scanners into your Harness pipelines without manual auth configuration.

When should I insert a secret detection step in the CI pipeline?▼

Insert the secret detection step early in the CI pipeline, specifically before any build steps. Running the scanner against the repository codebase at this stage ensures exposed API keys and tokens are caught before compilation.

Related Skills

Explore More Software Engineering Skills→
harnessharness
80

configure-repo-scan

Insert code scanning steps into existing Harness pipeline YAML.

Official
Intermediate
fulviomanentefulviomanente

trace-qr-scan

Trace a QR code through server logs across Received, Lookup, Found, Sent, and MQTT stages.

Community
Intermediate
thisrohanguptathisrohangupta
1

security-report

Generate security compliance reports from Harness SCS and STO vulnerability data.

Community
Advanced
manastalukdarmanastalukdar
1

secrets-scan

Scan codebases and Git history for exposed secrets using Gitleaks and TruffleHog.

Community
Advanced