enforce-slsa

Add an SLSA Verification step to Harness pipelines for provenance attestations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Add an SLSA Verification step to an existing Harness pipeline to verify SLSA provenance attestations and optionally enforce OPA policy sets on provenance data. Supports CI and CD (Deployment) including CI-only pipelines — append a Deploy stage via Phase 3b when verifying before deploy. Supports Docker, ECR, GCR, GAR, ACR, HAR, and Local artifacts. Only works with existing pipelines. Use when asked to verify SLSA, enforce SLSA policies, add SLSA verification step, validate SLSA attestation, or gate deploy on SLSA provenance. Trigger phrases: enforce SLSA, SLSA verification, verify SLSA, SLSA policy enforcement, SlsaVerification, verify SLSA attestation, add SLSA verify step.

Core Features & Use Cases

  • The wizard-based interaction guides users through the entire SLSA verification workflow, including placement, source inference, attestation verification, policy enforcement, and submission.
  • Supports CI, CD (including containerized step groups for Deploy) and Security stages, with the ability to gate deployment on provenance attestations.
  • Reuses the SLSA generation source to map provenance to verification fields and preserves consistency between generation and verification steps.
  • Never executes pipelines during configuration; instructs users to run /run-pipeline to validate verifications after setup.
  • Encourages complementary workflows: generate SLSA with /generate-slsa and manage policy sets via /create-policy.

Quick Start

Run /enforce-slsa to configure SLSA verification on an existing pipeline.

Frequently Asked Questions about enforce-slsa

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

FAQPage Schema
How do I add SLSA verification to an existing Harness pipeline?

Run /enforce-slsa to launch a wizard that appends an SLSA verification step to your existing Harness pipeline, validating provenance attestations and enforcing OPA policies without executing the pipeline.

What is SLSA provenance verification and when do I need it?

SLSA provenance verification validates attestations to secure the software supply chain. You need it to gate deployments and verify artifact integrity across CI and CD workflows before releasing.

Can I gate deployments on SLSA attestation validation in Harness?

Yes, you can gate deployments by adding an SLSA verification step to your CD pipeline. This validates provenance attestations before deployment and supports containerized step groups for Deploy stages.

Do I need an existing SLSA generation step before verifying attestations?

Yes, SLSA verification requires an existing provenance generation step. The verification process reuses the SLSA generation source to map provenance fields and maintain consistency between generation and verification.

What artifact types are supported for SLSA provenance verification?

SLSA provenance verification supports Docker, ECR, GCR, GAR, ACR, HAR, and Local artifacts. This allows you to validate attestations across various container registries and artifact repositories in your pipelines.

How do I enforce OPA policy sets on SLSA provenance data?

You can enforce OPA policy sets on SLSA provenance data by using the /enforce-slsa command to optionally integrate policy enforcement into your verification step, gating deploys based on policy evaluation results.