devsecops

Integrate security scanning into CI/CD pipelines with blocking gates.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill devsecops-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devsecops
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/devsecops
Command: npx skills add https://github.com/arbazkhan971/godmode --skill devsecops-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrates comprehensive security testing and enforcement into CI/CD pipelines to prevent vulnerabilities, secrets, and misconfigurations from reaching production, reducing risk and remediation overhead.

Core Features & Use Cases

  • Pipeline-wide scanning: Add SAST (Semgrep, CodeQL), DAST (OWASP ZAP), SCA (Snyk, Dependabot), container scanning (Trivy), and secret scanning (gitleaks/trufflehog) into PR and pre-deploy stages.
  • Security gates & enforcement: Define blocking policies for CRITICAL/HIGH findings, SBOM generation per release, and automated remediation workflows with ticketing and override rules.
  • IaC and container hardening: Scan Terraform, Kubernetes manifests, Dockerfiles and enforce least-privilege, pinned images, and non-root containers.
  • Use case: Automatically block merges with critical CVEs and secrets while generating remediation tasks and SBOMs for every release to meet compliance SLAs.

Quick Start

Use the devsecops skill to add Semgrep for SAST, Trivy for container scans, and gitleaks for secret scanning to your repository's GitHub Actions workflows and enforce blocking on critical findings.

Frequently Asked Questions about devsecops

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

FAQPage Schema
How do I integrate SAST and secret scanning into GitHub Actions workflows?

To integrate SAST and secret scanning into GitHub Actions, you configure Semgrep and gitleaks to run on pull requests, automatically detecting and blocking exposed secrets and critical vulnerabilities before deployment.

What is the best way to block merges with critical CVEs in a CI/CD pipeline?

The best way to block merges with critical CVEs in a CI/CD pipeline is by implementing security gates that enforce blocking policies for CRITICAL and HIGH findings, preventing vulnerable code from reaching production environments.

Does this approach support adding DAST and SCA to Jenkins and GitLab CI?

Yes, this approach supports adding DAST and SCA to Jenkins and GitLab CI, allowing you to run comprehensive security testing including OWASP ZAP and Snyk across pre-deploy stages to catch runtime and dependency vulnerabilities.

How do I generate an SBOM for every release using CI/CD security tools?

To generate an SBOM for every release using CI/CD security tools, you configure Software Composition Analysis stages to produce software bills of materials alongside automated remediation workflows and ticketing for compliance tracking.

Can I scan Terraform and Kubernetes manifests for misconfigurations in CI pipelines?

Yes, you can scan Terraform and Kubernetes manifests for misconfigurations in CI pipelines to enforce least-privilege, pinned images, and non-root containers, hardening your infrastructure as code before deployment.

How do I configure security gates to enforce blocking policies for high findings?

To configure security gates to enforce blocking policies for HIGH findings, you define threshold rules within your pipeline that trigger automated remediation workflows and block merges when SAST or DAST scans detect severe vulnerabilities.