Skip to main content 首页 创作者 agentsecops secopsagentkit iac-checkov
iac-checkov Infrastructure as Code (IaC) security scanning using Checkov with 750+ built-in policies for Terraform, CloudFormation, Kubernetes, Dockerfile, and ARM templates. Use when: (1) Scanning IaC files for security misconfigurations and compliance violations, (2) Validating cloud infrastructure against CIS, PCI-DSS, HIPAA, and SOC2 benchmarks, (3) Detecting secrets and hardcoded credentials in IaC, (4) Implementing policy-as-code in CI/CD pipelines, (5) Generating compliance reports with remediation guidance for cloud security posture management.
跳到安装 Skills Marketplace 发现并探索由社区构建的 Agent Skills
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AgentSecOps/SecOpsAgentKit --skill iac-checkov命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
下载 Zip 下载中... 同仓库更多 Skills Interactive HTTPS proxy for API security testing with traffic interception, modification, and replay capabilities. Supports HTTP/1, HTTP/2, HTTP/3, WebSockets, and TLS-protected protocols. Includes Python scripting API for automation and multiple interfaces (console, web, CLI). Use when: (1) Intercepting and analyzing API traffic for security testing, (2) Modifying HTTP/HTTPS requests and responses to test API behavior, (3) Recording and replaying API traffic for testing, (4) Debugging mobile app or thick client API communications, (5) Automating API security tests with Python scripts, (6) Exporting traffic in HAR format for analysis.
API specification linting and security validation using Stoplight's Spectral with support for OpenAPI, AsyncAPI, and Arazzo specifications. Validates API definitions against security best practices, OWASP API Security Top 10, and custom organizational standards. Use when: (1) Validating OpenAPI/AsyncAPI specifications for security issues and design flaws, (2) Enforcing API design standards and governance policies across API portfolios, (3) Creating custom security rules for API specifications in CI/CD pipelines, (4) Detecting authentication, authorization, and data exposure issues in API definitions, (5) Ensuring API specifications comply with organizational security standards and regulatory requirements.
Fast web fuzzer for DAST testing with directory enumeration, parameter fuzzing, and virtual host discovery. Written in Go for high-performance HTTP fuzzing with extensive filtering capabilities. Supports multiple fuzzing modes (clusterbomb, pitchfork, sniper) and recursive scanning. Use when: (1) Discovering hidden directories, files, and endpoints on web applications, (2) Fuzzing GET and POST parameters to identify injection vulnerabilities, (3) Enumerating virtual hosts and subdomains, (4) Testing authentication endpoints with credential fuzzing, (5) Finding backup files and sensitive data exposures, (6) Performing comprehensive web application reconnaissance.
name iac-checkov description Infrastructure as Code (IaC) security scanning using Checkov with 750+ built-in policies for Terraform, CloudFormation, Kubernetes, Dockerfile, and ARM templates. Use when: (1) Scanning IaC files for security misconfigurations and compliance violations, (2) Validating cloud infrastructure against CIS, PCI-DSS, HIPAA, and SOC2 benchmarks, (3) Detecting secrets and hardcoded credentials in IaC, (4) Implementing policy-as-code in CI/CD pipelines, (5) Generating compliance reports with remediation guidance for cloud security posture management.
version 0.1.0 maintainer SirAppSec category devsecops tags ["iac","checkov","terraform","kubernetes","cloudformation","compliance","policy-as-code","cloud-security"] frameworks ["PCI-DSS","HIPAA","SOC2","NIST","GDPR"] dependencies {"python":">=3.8","packages":["checkov"]} references ["https://www.checkov.io/","https://github.com/bridgecrewio/checkov","https://docs.paloaltonetworks.com/prisma/prisma-cloud"]
Infrastructure as Code Security with Checkov
Overview
Checkov is a static code analysis tool that scans Infrastructure as Code (IaC) files for security misconfigurations
and compliance violations before deployment. With 750+ built-in policies, Checkov helps prevent cloud security issues
by detecting problems in Terraform, CloudFormation, Kubernetes, Dockerfiles, Helm charts, and ARM templates.
Checkov performs graph-based scanning to understand resource relationships and detect complex misconfigurations that
span multiple resources, making it more powerful than simple pattern matching.
Quick Start
Install Checkov
pip install checkov
brew install checkov
docker pull bridgecrew/checkov
Scan Terraform Directory
checkov -d ./terraform
checkov -f ./terraform/main.tf
checkov -d ./infrastructure --framework terraform
Scan Kubernetes Manifests
checkov -d ./k8s --framework kubernetes
checkov -d ./helm-chart --framework helm
Scan CloudFormation Template
checkov -f ./cloudformation/template.yaml --framework cloudformation
Core Workflow
Step 1: Understand Scan Scope
Identify IaC files and frameworks to scan:
checkov --list-frameworks
Scope Considerations:
Scan entire infrastructure directory for comprehensive coverage
Focus on specific frameworks during initial adoption
Exclude generated or vendor files
Include both production and non-production configurations
Step 2: Run Basic Scan
Execute Checkov with appropriate output format:
checkov -d ./terraform
checkov -d ./terraform -o json
checkov -d ./terraform -o cli -o json -o sarif
checkov -d ./terraform -o json --output-file-path ./reports
Security misconfigurations (unencrypted resources, public access)
Compliance violations (CIS benchmarks, industry standards)
Secrets and hardcoded credentials
Missing security controls (logging, monitoring, encryption)
Insecure network configurations
Resource relationship issues (via graph analysis)
Step 3: Filter and Prioritize Findings Focus on critical issues first:
checkov -d ./terraform --check CKV_AWS_*
checkov -d ./terraform --skip-check CKV_AWS_8,CKV_AWS_21
checkov -d ./terraform --compact --framework terraform \
--check CIS_AWS,CIS_AZURE
checkov -d ./terraform --check HIGH,CRITICAL
CRITICAL : Immediate security risks (public S3 buckets, unencrypted databases)HIGH : Significant security concerns (missing MFA, weak encryption)MEDIUM : Important security best practices (missing tags, logging disabled)LOW : Recommendations and hardening (resource naming conventions)
Step 4: Suppress False Positives Use inline suppression for legitimate exceptions:
# Terraform example
resource "aws_s3_bucket" "example" {
# checkov:skip=CKV_AWS_18:This bucket is intentionally public for static website
bucket = "my-public-website"
acl = "public-read"
}
apiVersion: v1
kind: Pod
metadata:
name: privileged-pod
annotations:
checkov.io/skip: CKV_K8S_16=Legacy application requires privileged mode
spec:
containers:
- name: app
securityContext:
privileged: true
See references/suppression_guide.md for comprehensive suppression strategies.
Step 5: Create Custom Policies Define organization-specific policies:
from checkov.terraform.checks.resource.base_resource_check import BaseResourceCheck
from checkov.common.models.enums import CheckResult, CheckCategories
class S3BucketVersioning (BaseResourceCheck ):
def __init__ (self ):
name = "Ensure S3 bucket has versioning enabled"
id = "CKV_AWS_CUSTOM_001"
supported_resources = ['aws_s3_bucket' ]
categories = [CheckCategories.BACKUP_AND_RECOVERY]
super ().__init__(name=name, id =id , categories=categories,
supported_resources=supported_resources)
def scan_resource_conf (self, conf ):
if 'versioning' in conf:
if conf['versioning' ][0 ].get('enabled' ) == [True ]:
return CheckResult.PASSED
return CheckResult.FAILED
check = S3BucketVersioning()
Run with custom policies:
checkov -d ./terraform --external-checks-dir ./custom_checks
See references/custom_policies.md for advanced policy development.
Step 6: Generate Compliance Reports Create reports for audit and compliance:
checkov -d ./terraform \
-o cli -o json -o junitxml \
--output-file-path ./compliance-reports \
--repo-id my-infrastructure \
--branch main
checkov -d ./terraform -o cyclonedx
checkov -d ./terraform -o sarif --output-file-path ./sarif-report.json
CLI : Human-readable console outputJSON : Machine-readable for automationJUnit XML : CI/CD integration (Jenkins, GitLab)SARIF : GitHub/Azure DevOps Security tabCycloneDX : Software Bill of Materials for IaC Map findings to compliance frameworks using references/compliance_mapping.md.
CI/CD Integration
GitHub Actions Add Checkov scanning to pull request checks:
name: Checkov IaC Security Scan
on: [push , pull_request ]
jobs:
checkov-scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Run Checkov
uses: bridgecrewio/checkov-action@master
with:
directory: infrastructure/
framework: terraform
output_format: sarif
output_file_path: checkov-results.sarif
soft_fail: false
- name: Upload SARIF Report
if: always()
uses: github/codeql-action/upload-sarif@v2
with:
sarif_file: checkov-results.sarif
Pre-Commit Hook Prevent committing insecure IaC:
repos:
- repo: https://github.com/bridgecrewio/checkov
rev: 2.5 .0
hooks:
- id: checkov
args: [--soft-fail ]
files: \.(tf|yaml|yml|json)$
Install pre-commit hooks:
pip install pre-commit
pre-commit install
GitLab CI
checkov_scan:
image: bridgecrew/checkov:latest
stage: security
script:
- checkov -d ./terraform -o json -o junitxml
--output-file-path $CI_PROJECT_DIR/checkov-report
artifacts:
reports:
junit: checkov-report/results_junitxml.xml
paths:
- checkov-report/
when: always
Jenkins Pipeline // Jenkinsfile
pipeline {
agent any
stages {
stage('Checkov Scan') {
steps {
sh 'pip install checkov'
sh '''
checkov -d ./terraform \
-o cli -o junitxml \
--output-file-path ./reports
'''
}
}
}
post {
always {
junit 'reports/results_junitxml.xml'
}
}
}
See assets/ directory for complete CI/CD templates.
Framework-Specific Workflows
Terraform Scan Terraform with Variable Files:
checkov -d ./terraform --var-file ./terraform.tfvars
checkov -d ./terraform --download-external-modules true
checkov -d ./terraform --skip-path terraform.tfstate
CKV_AWS_19: Ensure S3 bucket has server-side encryption
CKV_AWS_21: Ensure S3 bucket has versioning enabled
CKV_AWS_23: Ensure Security Group ingress is not open to 0.0.0.0/0
CKV_AWS_40: Ensure IAM policies don't use wildcard actions
CKV_AWS_61: Ensure RDS database has encryption at rest enabled
Kubernetes Scan Kubernetes Manifests:
checkov -d ./k8s --framework kubernetes
checkov -d ./helm-chart --framework helm
kustomize build ./overlay/prod | checkov -f - --framework kubernetes
Common Kubernetes Checks:
CKV_K8S_8: Ensure Liveness Probe is configured
CKV_K8S_10: Ensure CPU requests are set
CKV_K8S_11: Ensure CPU limits are set
CKV_K8S_14: Ensure container image is not latest
CKV_K8S_16: Ensure container is not privileged
CKV_K8S_22: Ensure read-only root filesystem
CKV_K8S_28: Ensure container capabilities are minimized
CloudFormation Scan CloudFormation Templates:
checkov -f ./cloudformation/stack.yaml --framework cloudformation
checkov -f ./sam-template.yaml --framework serverless
Dockerfile Scan Dockerfiles for Security Issues:
checkov -f ./Dockerfile --framework dockerfile
Baseline and Drift Detection
Create Security Baseline Establish baseline for existing infrastructure:
checkov -d ./terraform --create-baseline
Detect New Issues (Drift) Compare subsequent scans against baseline:
checkov -d ./terraform --baseline .checkov.baseline
Gradual remediation of legacy infrastructure
Focus on preventing new security debt
Phased compliance adoption
Secret Scanning Detect hardcoded secrets in IaC:
checkov -d ./terraform --framework secrets
Security Considerations
Policy Suppression Governance : Require security team approval for suppressing CRITICAL/HIGH findingsCI/CD Failure Thresholds : Configure --hard-fail-on for severity levels that should block deploymentCustom Policy Management : Version control custom policies and review changesCompliance Alignment : Map organizational requirements to Checkov policiesSecrets Management : Never commit secrets; use secret managers and rotation policiesAudit Logging : Log all scan results and policy suppressions for compliance auditsFalse Positive Review : Regularly review suppressed findings to ensure they remain validPolicy Updates : Keep Checkov updated to receive new security policies
Bundled Resources
Scripts (scripts/)
checkov_scan.py - Comprehensive scanning script with multiple frameworks and output formatscheckov_terraform_scan.sh - Terraform-specific scanning with variable file supportcheckov_k8s_scan.sh - Kubernetes manifest scanning with cluster comparisoncheckov_baseline_create.sh - Baseline creation and drift detection workflowcheckov_compliance_report.py - Generate compliance reports (CIS, PCI-DSS, HIPAA, SOC2)ci_integration.sh - CI/CD integration examples for multiple platforms
References (references/)
compliance_mapping.md - Mapping of Checkov checks to CIS, PCI-DSS, HIPAA, SOC2, NISTcustom_policies.md - Guide for writing custom Python and YAML policiessuppression_guide.md - Best practices for suppressing false positivesterraform_checks.md - Comprehensive list of Terraform checks with remediationkubernetes_checks.md - Kubernetes security checks and pod security standardscloudformation_checks.md - CloudFormation security checks with examples
Assets (assets/)
checkov_config.yaml - Checkov configuration file templategithub_actions.yml - Complete GitHub Actions workflowgitlab_ci.yml - Complete GitLab CI pipelinejenkins_pipeline.groovy - Jenkins pipeline templatepre_commit_config.yaml - Pre-commit hook configurationcustom_policy_template.py - Template for custom Python policiespolicy_metadata.yaml - Policy metadata for organization-specific policies
Common Patterns
Pattern 1: Progressive Compliance Adoption Gradually increase security posture:
checkov -d ./terraform --soft-fail
checkov -d ./terraform --hard-fail-on CRITICAL
checkov -d ./terraform --hard-fail-on CRITICAL,HIGH
checkov -d ./terraform --baseline .checkov.baseline
Pattern 2: Multi-Framework Infrastructure Scan complete infrastructure stack:
python3 scripts/checkov_scan.py \
--infrastructure-dir ./infrastructure \
--frameworks terraform,kubernetes,dockerfile \
--output-dir ./security-reports \
--compliance CIS,PCI-DSS
Pattern 3: Policy-as-Code Repository Maintain centralized policy repository:
policies/
├── custom_checks/
│ ├── aws/
│ │ ├── require_encryption.py
│ │ └── require_tags.py
│ ├── kubernetes/
│ │ └── require_psp.py
├── .checkov.yaml # Global config
└── suppression_list.txt # Approved suppressions
Pattern 4: Compliance-Driven Scanning Focus on specific compliance requirements:
checkov -d ./terraform --check CIS_AWS
checkov -d ./terraform --framework terraform \
--check CKV_AWS_19,CKV_AWS_21,CKV_AWS_61 \
-o json --output-file-path ./pci-dss-report
checkov -d ./terraform --framework terraform \
--compact --check CKV_AWS_17,CKV_AWS_19,CKV_AWS_61,CKV_AWS_93
Integration Points
CI/CD : GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, Bitbucket PipelinesVersion Control : Pre-commit hooks, pull request checks, branch protection rulesCloud Platforms : AWS, Azure, GCP, OCI, Alibaba CloudIaC Tools : Terraform, Terragrunt, CloudFormation, ARM, PulumiContainer Orchestration : Kubernetes, OpenShift, EKS, GKE, AKSPolicy Engines : OPA (Open Policy Agent), SentinelSecurity Platforms : Prisma Cloud, Bridgecrew PlatformSIEM/Logging : Export findings to Splunk, Elasticsearch, CloudWatch
Troubleshooting
Issue: Too Many Findings Overwhelming Team Solution : Use progressive adoption with baselines:
checkov -d ./terraform --create-baseline
checkov -d ./terraform --baseline .checkov.baseline --soft-fail-on LOW,MEDIUM
Issue: False Positives for Legitimate Use Cases Solution : Use inline suppressions with justification:
# Provide clear business justification
resource "aws_security_group" "allow_office" {
# checkov:skip=CKV_AWS_23:Office IP range needs SSH access for developers
ingress {
from_port = 22
to_port = 22
protocol = "tcp"
cidr_blocks = ["203.0.113.0/24"] # Office IP range
}
}
Issue: Scan Takes Too Long Solution : Optimize scan scope:
checkov -d ./terraform \
--skip-path .terraform/ \
--skip-path modules/vendor/ \
--skip-framework secrets
checkov -d ./terraform --compact --quiet
Issue: Custom Policies Not Loading Solution : Verify policy structure and loading:
python3 custom_checks/my_policy.py
checkov -d ./terraform \
--external-checks-dir ./custom_checks \
--list
checkov -d ./terraform --external-checks-dir ./custom_checks -v
Issue: Integration with Private Terraform Modules Solution : Configure module access:
export TF_TOKEN_app_terraform_io="your-token"
checkov -d ./terraform --download-external-modules true
cd ./terraform && terraform init
checkov -d .
References 