ci-cd-security

Execute and interpret seven security checks in CI/CD pipelines.

2|Updated Apr 9, 2025
One-click install
npx skills add https://github.com/PP-Namias/Portfolio --skill ci-cd-security-pp-namias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-security
Source: https://github.com/PP-Namias/Portfolio/tree/main/.agents/skills/ci-cd-security
Command: npx skills add https://github.com/PP-Namias/Portfolio --skill ci-cd-security-pp-namias

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill manages and automates the execution of seven key security checks in the CI/CD pipeline of a project, reducing manual efforts and enhancing security posture.

Core Features & Use Cases

  • Automated Security Checks: Integrates with CI/CD pipeline to automate Gitleaks, OSV-Scanner, Trivy, Checkov, zizmor, Cosign, and Scorecard security tools.
  • Workflow Hardening: Provides guidance for pipeline hardening practices such as action SHA pinning and permission declaration.
  • Local Execution Instructions: Includes steps to execute security checks locally for testing and troubleshooting.

Quick Start

Execute a full security check of the local project repository by running the gitleaks detect command provided in the skill instructions.

Frequently Asked Questions about ci-cd-security

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

FAQPage Schema
How do I automate security checks in a CI/CD pipeline?

Automating CI/CD pipeline security checks involves integrating tools like Gitleaks, OSV-Scanner, and Trivy to continuously scan for secrets, CVEs, and configuration misconfigurations during active development. This reduces manual effort and enforces compliance automatically within the workflow.

What security tools are needed for CI/CD pipeline hardening?

CI/CD pipeline hardening utilizes tools like Gitleaks for secret detection, Trivy for vulnerability scanning, Checkov for configuration audits, and Scorecard for overall security posture. These tools automate security compliance and identify risks during active repository development.

Can I run CI/CD security checks locally before pushing code?

Running CI/CD security checks locally is possible and recommended for troubleshooting. You can execute specific tools like `gitleaks detect` directly on your local project repository to identify secret detection issues and configuration audits before triggering the full pipeline.

What is the best way to scan repositories for secrets and CVEs?

The best way to scan repositories for secrets and CVEs is automating security checks within the CI/CD pipeline. Integrating Gitleaks for secret detection and OSV-Scanner for CVE scanning ensures continuous security auditing and immediate remediation strategies during active development.

How do I interpret configuration audit results from CI/CD security scanners?

Interpreting configuration audit results from CI/CD security scanners like Checkov involves analyzing the identified misconfigurations against compliance standards. The process targets repositories undergoing active development, providing actionable remediation strategies to improve code quality and pipeline security posture.

Why should I pin action SHAs and declare permissions in CI/CD pipelines?

Pinning action SHAs and declaring permissions are workflow hardening practices that prevent supply chain attacks and enforce least privilege in CI/CD pipeline automation. These security checks ensure configuration compliance and protect the pipeline from unauthorized modifications.