cicd-security

Harden CI/CD pipelines with secret management, runner isolation, and artifact verification.

Updated Oct 31, 2024
One-click install
npx skills add https://github.com/thesammykins/dotfiles --skill cicd-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cicd-security
Source: https://github.com/thesammykins/dotfiles/tree/main/.agents/skills/cicd-security
Command: npx skills add https://github.com/thesammykins/dotfiles --skill cicd-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI/CD pipelines frequently suffer from insecure secret handling, weak supply chain controls, non-isolated runners, and unverified artifacts, which together heighten risk across builds and deployments.

Core Features & Use Cases

  • Secrets management and rotation across CI configurations and logs.
  • Runner isolation with ephemeral environments and restricted network access.
  • Artifact signing, provenance checks, and secure supply chain governance.
  • Use Case: protect GitHub Actions workflows from credential leakage and unauthorized deployments.

Quick Start

Enable least-privilege CI identities, enforce secrets management, and isolate runners within your pipeline.

Frequently Asked Questions about cicd-security

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

FAQPage Schema
How do I harden secrets and prevent credential leakage in GitHub Actions workflows?

To harden secrets in GitHub Actions, you configure least-privilege CI identities and enforce managed secret stores to handle secrets management and rotation across CI configurations and logs, preventing credential leakage.

What is runner isolation and how does it secure CI/CD pipelines?

Runner isolation secures CI/CD pipelines by using ephemeral environments and restricted network access for build agents. This minimizes the attack surface by ensuring runners are temporary and isolated from unauthorized network traffic.

How do I implement artifact signing and provenance checks for supply chain integrity?

You implement supply chain integrity by configuring artifact signing and provenance checks within your pipeline. This verifies artifact origin and enforces secure supply chain governance across the build lifecycle.

Does this CI/CD security hardening approach work with GitLab CI and Jenkins?

Yes, this CI/CD security hardening applies to GitHub Actions, GitLab CI, Jenkins, and other CI systems. It standardizes least-privilege access, managed secrets, and runner isolation across diverse pipeline configurations.

What is the best way to protect build pipelines from unauthorized deployments?

The best way to prevent unauthorized deployments is enforcing least-privilege CI identities and isolating runners. This restricts deployment capabilities and secures the pipeline against unauthorized access attempts.

Do I need ephemeral runners to secure my CI/CD pipeline?

You need ephemeral runners to secure CI/CD pipelines because they provide isolated, temporary environments that restrict network access. This prevents persistent vulnerabilities and limits potential supply chain attacks.