build-yaml-misconfiguration

Analyze CI/CD pipeline YAML files for security misconfigurations.

47|5|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/RedHatProductSecurity/prodsec-skills --skill build-yaml-misconfiguration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-yaml-misconfiguration
Source: https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/build-yaml-misconfiguration
Command: npx skills add https://github.com/RedHatProductSecurity/prodsec-skills --skill build-yaml-misconfiguration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, json, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify security issues and misconfigurations in build YAML files for CI/CD pipelines, preventing potential leaks and privilege escalations.

Core Features & Use Cases

  • Scan GitLab CI and Tekton YAML files for common security pitfalls such as secret exposure, privileged runners, and unpinned images.
  • Enforce best practices by recommending secure configuration patterns, including secret management and image pinning.
  • Use Case: A security engineer reviews pipeline configurations to ensure no secrets are hardcoded and images are verified before deployment.

Quick Start

Review the provided YAML pipeline file and identify any insecure configurations upon request.

Frequently Asked Questions about build-yaml-misconfiguration

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

FAQPage Schema
How do I check CI/CD YAML files for security misconfigurations?

To check CI/CD YAML files for security misconfigurations, analyze pipeline definitions for insecure secret handling, unpinned images, privileged runners, and risky include directives to prevent potential leaks and privilege escalations.

What CI/CD pipeline security issues should I look for in GitLab CI YAML?

Common CI/CD pipeline security issues in GitLab CI YAML include hardcoded secrets, privileged runner configurations, unpinned deployment images, and unverified include directives that can introduce vulnerabilities during execution.

How do I scan Tekton YAML for insecure secret handling and image security risks?

Scanning Tekton YAML for insecure secret handling and image security risks involves reviewing pipeline configurations to ensure secrets are managed securely and container images are pinned and verified before deployment.

Can I enforce secure configuration patterns for CI/CD pipelines using YAML analysis?

You can enforce secure configuration patterns for CI/CD pipelines through YAML analysis by recommending best practices for secret management and image pinning to enhance overall pipeline security against misconfigurations.

Do I need PyYAML to analyze build YAML files for insecure configurations?

Yes, analyzing build YAML files for insecure configurations requires PyYAML and JSON dependencies to parse pipeline definitions and evaluate them against security best practices for secret exposure and runner privileges.

Why does my CI/CD pipeline YAML configuration cause privilege escalation risks?

CI/CD pipeline YAML configurations cause privilege escalation risks when runners are granted excessive privileges or when include directives pull untrusted external code, allowing unauthorized access to pipeline resources.