[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9886":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":25,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":40,"readmeContent":41,"aiSummary":42,"trendingCount":16,"starSnapshotCount":16,"syncStatus":43,"lastSyncTime":44,"discoverSource":45},9886,"checkov","bridgecrewio\u002Fcheckov","bridgecrewio","Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.","https:\u002F\u002Fwww.checkov.io\u002F",null,"Python",8783,1351,56,81,0,4,21,86,20,40.39,"Apache License 2.0",false,"main",true,[27,28,29,30,31,32,33,34,35,36,37,38,39],"aws","aws-security","azure","cloudformation","compliance","devops","gcp","hacktoberfest","infrastructure-as-code","kubernetes","scans","static-analysis","terraform","2026-06-12 02:02:14","[![checkov](https:\u002F\u002Fraw.githubusercontent.com\u002Fbridgecrewio\u002Fcheckov\u002Fmain\u002Fdocs\u002Fweb\u002Fimages\u002Fcheckov_blue_logo.png)](#)\n       \n[![Maintained by Prisma Cloud](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fmaintained_by-Prisma_Cloud-blue)](https:\u002F\u002Fprismacloud.io\u002F?utm_source=github&utm_medium=organic_oss&utm_campaign=checkov)\n[![build status](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fworkflows\u002Fbuild\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Factions?query=workflow%3Abuild)\n[![security status](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fworkflows\u002Fsecurity\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Factions?query=event%3Apush+branch%3Amaster+workflow%3Asecurity)\n[![code_coverage](https:\u002F\u002Fraw.githubusercontent.com\u002Fbridgecrewio\u002Fcheckov\u002Fmain\u002Fcoverage.svg?sanitize=true)](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Factions?query=workflow%3Acoverage)\n[![docs](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fdocs-passing-brightgreen)](https:\u002F\u002Fwww.checkov.io\u002F1.Welcome\u002FWhat%20is%20Checkov.html?utm_source=github&utm_medium=organic_oss&utm_campaign=checkov)\n[![PyPI](https:\u002F\u002Fimg.shields.io\u002Fpypi\u002Fv\u002Fcheckov)](https:\u002F\u002Fpypi.org\u002Fproject\u002Fcheckov\u002F)\n[![Python Version](https:\u002F\u002Fimg.shields.io\u002Fpypi\u002Fpyversions\u002Fcheckov)](#)\n[![Terraform Version](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Ftf-%3E%3D0.12.0-blue.svg)](#)\n[![Downloads](https:\u002F\u002Fstatic.pepy.tech\u002Fbadge\u002Fcheckov)](https:\u002F\u002Fpepy.tech\u002Fproject\u002Fcheckov)\n[![Docker Pulls](https:\u002F\u002Fimg.shields.io\u002Fdocker\u002Fpulls\u002Fbridgecrew\u002Fcheckov.svg)](https:\u002F\u002Fhub.docker.com\u002Fr\u002Fbridgecrew\u002Fcheckov)\n[![slack-community](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FSlack-4A154B?style=plastic&logo=slack&logoColor=white)](https:\u002F\u002Fcodifiedsecurity.slack.com\u002F)\n\n\n**Checkov** is a static code analysis tool for infrastructure as code (IaC) and also a software composition analysis (SCA) tool for images and open source packages.\n\nIt scans cloud infrastructure provisioned using [Terraform](https:\u002F\u002Fterraform.io\u002F), [Terraform plan](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FTerraform%20Plan%20Scanning.md), [Cloudformation](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FCloudformation.md), [AWS SAM](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FAWS%20SAM.md), [Kubernetes](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FKubernetes.md), [Helm charts](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FHelm.md), [Kustomize](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FKustomize.md), [Dockerfile](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FDockerfile.md),  [Serverless](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FServerless%20Framework.md), [Bicep](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FBicep.md), [OpenAPI](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FOpenAPI.md), [ARM Templates](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F7.Scan%20Examples\u002FAzure%20ARM%20templates.md), or [OpenTofu](https:\u002F\u002Fopentofu.org\u002F) and detects security and compliance misconfigurations using graph-based scanning.\n\nIt performs [Software Composition Analysis (SCA) scanning](docs\u002F7.Scan%20Examples\u002FSca.md) which is a scan of open source packages and images for Common Vulnerabilities and Exposures (CVEs).\n \nCheckov also powers [**Prisma Cloud Application Security**](https:\u002F\u002Fwww.prismacloud.io\u002Fprisma\u002Fcloud\u002Fcloud-code-security\u002F?utm_source=github&utm_medium=organic_oss&utm_campaign=checkov), the developer-first platform that codifies and streamlines cloud security throughout the development lifecycle. Prisma Cloud identifies, fixes, and prevents misconfigurations in cloud resources and infrastructure-as-code files. \n\n\u003Ca href=\"https:\u002F\u002Fwww.prismacloud.io\u002Fprisma\u002Frequest-a-prisma-cloud-trial\u002F?utm_campaign=checkov-github-repo&utm_source=github.com&utm_medium=get-started-button\" title=\"Try_Prisma_Cloud\">\n    \u003Cimg src=\"https:\u002F\u002Fdabuttonfactory.com\u002Fbutton.png?t=Try+Prisma+Cloud&f=Open+Sans-Bold&ts=26&tc=fff&hp=45&vp=20&c=round&bgt=unicolored&bgc=00c0e8\" align=\"right\" width=\"120\">\n\u003C\u002Fa>\n\n\n\u003Ca href=\"https:\u002F\u002Fdocs.prismacloud.io\u002Fen\u002Fenterprise-edition\u002Fuse-cases\u002Fsecure-the-source\u002Fsecure-the-source\" title=\"Docs\">\n    \u003Cimg src=\"https:\u002F\u002Fdabuttonfactory.com\u002Fbutton.png?t=Read+the+Docs&f=Open+Sans-Bold&ts=26&tc=fff&hp=45&vp=20&c=round&bgt=unicolored&bgc=00c0e8\" align=\"right\" width=\"120\">\n\u003C\u002Fa>\n\n## **Table of contents**\n\n- [Features](#features)\n- [Screenshots](#screenshots)\n- [Getting Started](#getting-started)\n- [Disclaimer](#disclaimer)\n- [Support](#support)\n- [Migration - v2 to v3](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F1.Welcome\u002FMigration.md)\n\n ## Features\n\n * [Over 1000 built-in policies](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F5.Policy%20Index\u002Fall.md) cover security and compliance best practices for AWS, Azure and Google Cloud.\n * Scans Terraform, Terraform Plan, Terraform JSON, CloudFormation, AWS SAM, Kubernetes, Helm, Kustomize, Dockerfile, Serverless framework, Ansible, Bicep, ARM, and OpenTofu template files.\n * Scans Argo Workflows, Azure Pipelines, BitBucket Pipelines, Circle CI Pipelines, GitHub Actions and GitLab CI workflow files\n * Supports Context-awareness policies based on in-memory graph-based scanning.\n * Supports Python format for attribute policies and YAML format for both attribute and composite policies.\n * Detects [AWS credentials](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F2.Basics\u002FScanning%20Credentials%20and%20Secrets.md) in EC2 Userdata, Lambda environment variables and Terraform providers.\n * [Identifies secrets](https:\u002F\u002Fwww.prismacloud.io\u002Fprisma\u002Fcloud\u002Fsecrets-security) using regular expressions, keywords, and entropy based detection.\n * Evaluates [Terraform Provider](https:\u002F\u002Fregistry.terraform.io\u002Fbrowse\u002Fproviders) settings to regulate the creation, management, and updates of IaaS, PaaS or SaaS managed through Terraform.\n * Policies support evaluation of [variables](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F2.Basics\u002FHandling%20Variables.md) to their optional default value.\n * Supports in-line [suppression](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F2.Basics\u002FSuppressing%20and%20Skipping%20Policies.md) of accepted risks or false-positives to reduce recurring scan failures. Also supports global skip from using CLI.\n * [Output](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F2.Basics\u002FReviewing%20Scan%20Results.md) currently available as CLI, [CycloneDX](https:\u002F\u002Fcyclonedx.org), JSON, JUnit XML, CSV, SARIF and github markdown and link to remediation [guides](https:\u002F\u002Fdocs.prismacloud.io\u002Fen\u002Fenterprise-edition\u002Fpolicy-reference\u002F).\n \n## Screenshots\n\nScan results in CLI\n\n![scan-screenshot](https:\u002F\u002Fraw.githubusercontent.com\u002Fbridgecrewio\u002Fcheckov\u002Fmain\u002Fdocs\u002Fcheckov-recording.gif)\n\nScheduled scan result in Jenkins\n\n![jenikins-screenshot](https:\u002F\u002Fraw.githubusercontent.com\u002Fbridgecrewio\u002Fcheckov\u002Fmain\u002Fdocs\u002Fcheckov-jenkins.png)\n\n## Getting started\n\n### Requirements\n * Python >= 3.9, \u003C=3.12\n * Terraform >= 0.12\n\n### Installation\n\nTo install pip follow the official [docs](https:\u002F\u002Fpip.pypa.io\u002Fen\u002Fstable\u002Fcli\u002Fpip_install\u002F)\n\n```sh\npip3 install checkov\n```\n\nCertain environments (e.g., Debian 12) may require you to install Checkov in a virtual environment\n\n```sh\n# Create and activate a virtual environment\npython3 -m venv \u002Fpath\u002Fto\u002Fvenv\u002Fcheckov\ncd \u002Fpath\u002Fto\u002Fvenv\u002Fcheckov\nsource .\u002Fbin\u002Factivate\n\n# Install Checkov with pip\npip install checkov\n\n# Optional: Create a symlink for easy access\nsudo ln -s \u002Fpath\u002Fto\u002Fvenv\u002Fcheckov\u002Fbin\u002Fcheckov \u002Fusr\u002Flocal\u002Fbin\u002Fcheckov\n```\n\nor with [Homebrew](https:\u002F\u002Fformulae.brew.sh\u002Fformula\u002Fcheckov) (macOS or Linux)\n\n```sh\nbrew install checkov\n```\n\n### Enabling bash autocomplete\n```sh\nsource \u003C(register-python-argcomplete checkov)\n```\n### Upgrade\n\nif you installed checkov with pip3\n```sh\npip3 install -U checkov\n```\n\nor with Homebrew\n\n```sh\nbrew upgrade checkov\n```\n\n### Configure an input folder or file\n\n```sh\ncheckov --directory \u002Fuser\u002Fpath\u002Fto\u002Fiac\u002Fcode\n```\n\nOr a specific file or files\n\n```sh\ncheckov --file \u002Fuser\u002Ftf\u002Fexample.tf\n```\nOr\n```sh\ncheckov -f \u002Fuser\u002Fcloudformation\u002Fexample1.yml -f \u002Fuser\u002Fcloudformation\u002Fexample2.yml\n```\n\nOr a terraform plan file in json format\n```sh\nterraform init\nterraform plan -out tf.plan\nterraform show -json tf.plan  > tf.json\ncheckov -f tf.json\n```\n\nNote: `terraform show` output file `tf.json` will be a single line. \nFor that reason all findings will be reported line number 0 by Checkov\n\n\n```sh\ncheck: CKV_AWS_21: \"Ensure all data stored in the S3 bucket have versioning enabled\"\n\tFAILED for resource: aws_s3_bucket.customer\n\tFile: \u002Ftf\u002Ftf.json:0-0\n\tGuide: https:\u002F\u002Fdocs.prismacloud.io\u002Fen\u002Fenterprise-edition\u002Fpolicy-reference\u002Faws-policies\u002Fs3-policies\u002Fs3-16-enable-versioning\n  ```\n\nIf you have installed `jq` you can convert json file into multiple lines with the following command:\n```sh\nterraform show -json tf.plan | jq '.' > tf.json\n```\nScan result would be much user friendly.\n```sh\ncheckov -f tf.json\nCheck: CKV_AWS_21: \"Ensure all data stored in the S3 bucket have versioning enabled\"\n\tFAILED for resource: aws_s3_bucket.customer\n\tFile: \u002Ftf\u002Ftf1.json:224-268\n\tGuide: https:\u002F\u002Fdocs.prismacloud.io\u002Fen\u002Fenterprise-edition\u002Fpolicy-reference\u002Faws-policies\u002Fs3-policies\u002Fs3-16-enable-versioning\n\n\t\t225 |               \"values\": {\n\t\t226 |                 \"acceleration_status\": \"\",\n\t\t227 |                 \"acl\": \"private\",\n\t\t228 |                 \"arn\": \"arn:aws:s3:::mybucket\",\n\n```\n\nAlternatively, specify the repo root of the hcl files used to generate the plan file, using the `--repo-root-for-plan-enrichment` flag, to enrich the output with the appropriate file path, line numbers, and codeblock of the resource(s). An added benefit is that check suppressions will be handled accordingly.\n```sh\ncheckov -f tf.json --repo-root-for-plan-enrichment \u002Fuser\u002Fpath\u002Fto\u002Fiac\u002Fcode\n```\n\n\n### Scan result sample (CLI)\n\n```sh\nPassed Checks: 1, Failed Checks: 1, Suppressed Checks: 0\nCheck: \"Ensure all data stored in the S3 bucket is securely encrypted at rest\"\n\u002Fmain.tf:\n\t Passed for resource: aws_s3_bucket.template_bucket\nCheck: \"Ensure all data stored in the S3 bucket is securely encrypted at rest\"\n\u002F..\u002FregionStack\u002Fmain.tf:\n\t Failed for resource: aws_s3_bucket.sls_deployment_bucket_name\n```\n\nStart using Checkov by reading the [Getting Started](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F1.Welcome\u002FQuick%20Start.md) page.\n\n### Using Docker\n\n\n```sh\ndocker pull bridgecrew\u002Fcheckov\ndocker run --tty --rm --volume \u002Fuser\u002Ftf:\u002Ftf --workdir \u002Ftf bridgecrew\u002Fcheckov --directory \u002Ftf\n```\nNote: if you are using Python 3.6(Default version in Ubuntu 18.04) checkov will not work, and it will fail with `ModuleNotFoundError: No module named 'dataclasses'`  error message. In this case, you can use the docker version instead.\n\nNote that there are certain cases where redirecting `docker run --tty` output to a file - for example, if you want to save the Checkov JUnit output to a file - will cause extra control characters to be printed. This can break file parsing. If you encounter this, remove the `--tty` flag.\n\nThe `--workdir \u002Ftf` flag is optional to change the working directory to the mounted volume. If you are using the SARIF output `-o sarif` this will output the results.sarif file to the mounted volume (`\u002Fuser\u002Ftf` in the example above). If you do not include that flag, the working directory will be \"\u002F\".\n\n### Running or skipping checks\n\nBy using command line flags, you can specify to run only named checks (allow list) or run all checks except\nthose listed (deny list). If you are using the platform integration via API key, you can also specify a severity threshold to skip and \u002F or include.\nMoreover, as json files can't contain comments, one can pass regex pattern to skip json file secret scan.\n\nSee the docs for more detailed information about how these flags work together.\n\n\n## Examples\n\nAllow only the two specified checks to run:\n```sh\ncheckov --directory . --check CKV_AWS_20,CKV_AWS_57\n```\n\nRun all checks except the one specified:\n```sh\ncheckov -d . --skip-check CKV_AWS_20\n```\n\nRun all checks except checks with specified patterns:\n```sh\ncheckov -d . --skip-check CKV_AWS*\n```\n\nRun all checks that are MEDIUM severity or higher (requires API key):\n```sh\ncheckov -d . --check MEDIUM --bc-api-key ...\n```\n\nRun all checks that are MEDIUM severity or higher, as well as check CKV_123 (assume this is a LOW severity check):\n```sh\ncheckov -d . --check MEDIUM,CKV_123 --bc-api-key ...\n```\n\nSkip all checks that are MEDIUM severity or lower:\n```sh\ncheckov -d . --skip-check MEDIUM --bc-api-key ...\n```\n\nSkip all checks that are MEDIUM severity or lower, as well as check CKV_789 (assume this is a high severity check):\n```sh\ncheckov -d . --skip-check MEDIUM,CKV_789 --bc-api-key ...\n```\n\nRun all checks that are MEDIUM severity or higher, but skip check CKV_123 (assume this is a medium or higher severity check):\n```sh\ncheckov -d . --check MEDIUM --skip-check CKV_123 --bc-api-key ...\n```\n\nRun check CKV_789, but skip it if it is a medium severity (the --check logic is always applied before --skip-check)\n```sh\ncheckov -d . --skip-check MEDIUM --check CKV_789 --bc-api-key ...\n```\n\nFor Kubernetes workloads, you can also use allow\u002Fdeny namespaces.  For example, do not report any results for the\nkube-system namespace:\n```sh\ncheckov -d . --skip-check kube-system\n```\n\nRun a scan of a container image. First pull or build the image then refer to it by the hash, ID, or name:tag:\n```sh\ncheckov --framework sca_image --docker-image sha256:1234example --dockerfile-path \u002FUsers\u002Fpath\u002Fto\u002FDockerfile --repo-id ... --bc-api-key ...\n\ncheckov --docker-image \u003Cimage-name>:tag --dockerfile-path \u002FUser\u002Fpath\u002Fto\u002FDockerfile --repo-id ... --bc-api-key ...\n```\n\nYou can use --image flag also to scan container image instead of --docker-image for shortener:\n```sh\ncheckov --image \u003Cimage-name>:tag --dockerfile-path \u002FUser\u002Fpath\u002Fto\u002FDockerfile --repo-id ... --bc-api-key ...\n```\n\nRun an SCA scan of packages in a repo:\n```sh\ncheckov -d . --framework sca_package --bc-api-key ... --repo-id \u003Crepo_id(arbitrary)>\n```\n\nRun a scan of a directory with environment variables removing buffering, adding debug level logs:\n```sh\nPYTHONUNBUFFERED=1 LOG_LEVEL=DEBUG checkov -d .\n```\nOR enable the environment variables for multiple runs\n```sh\nexport PYTHONUNBUFFERED=1 LOG_LEVEL=DEBUG\ncheckov -d .\n```\n\nRun secrets scanning on all files in MyDirectory. Skip CKV_SECRET_6 check on json files that their suffix is DontScan\n```sh\ncheckov -d \u002FMyDirectory --framework secrets --repo-id ... --bc-api-key ... --skip-check CKV_SECRET_6:.*DontScan.json$\n```\n\nRun secrets scanning on all files in MyDirectory. Skip CKV_SECRET_6 check on json files that contains \"skip_test\" in path\n```sh\ncheckov -d \u002FMyDirectory --framework secrets --repo-id ... --bc-api-key ... --skip-check CKV_SECRET_6:.*skip_test.*json$\n```\n\nOne can mask values from scanning results by supplying a configuration file (using --config-file flag) with mask entry.\nThe masking can apply on resource & value (or multiple values, separated with a comma).\nExamples:\n```sh\nmask:\n- aws_instance:user_data\n- azurerm_key_vault_secret:admin_password,user_passwords\n```\nIn the example above, the following values will be masked:\n- user_data for aws_instance resource\n- both admin_password &user_passwords for azurerm_key_vault_secret\n\n\n### Suppressing\u002FIgnoring a check\n\nLike any static-analysis tool it is limited by its analysis scope.\nFor example, if a resource is managed manually, or using subsequent configuration management tooling,\nsuppression can be inserted as a simple code annotation.\n\n#### Suppression comment format\n\nTo skip a check on a given Terraform definition block or CloudFormation resource, apply the following comment pattern inside it's scope:\n\n`checkov:skip=\u003Ccheck_id>:\u003Csuppression_comment>`\n\n* `\u003Ccheck_id>` is one of the [available check scanners](docs\u002F5.Policy Index\u002Fall.md)\n* `\u003Csuppression_comment>` is an optional suppression reason to be included in the output\n\n#### Example\n\nThe following comment skips the `CKV_AWS_20` check on the resource identified by `foo-bucket`, where the scan checks if an AWS S3 bucket is private.\nIn the example, the bucket is configured with public read access; Adding the suppress comment would skip the appropriate check instead of the check to fail.\n\n```hcl-terraform\nresource \"aws_s3_bucket\" \"foo-bucket\" {\n  region        = var.region\n    #checkov:skip=CKV_AWS_20:The bucket is a public static content host\n  bucket        = local.bucket_name\n  force_destroy = true\n  acl           = \"public-read\"\n}\n```\n\nThe output would now contain a ``SKIPPED`` check result entry:\n\n```bash\n...\n...\nCheck: \"S3 Bucket has an ACL defined which allows public access.\"\n\tSKIPPED for resource: aws_s3_bucket.foo-bucket\n\tSuppress comment: The bucket is a public static content host\n\tFile: \u002Fexample_skip_acl.tf:1-25\n\n...\n```\nTo skip multiple checks, add each as a new line.\n\n```\n  #checkov:skip=CKV2_AWS_6\n  #checkov:skip=CKV_AWS_20:The bucket is a public static content host\n```\n\nTo suppress checks in Kubernetes manifests, annotations are used with the following format:\n`checkov.io\u002Fskip#: \u003Ccheck_id>=\u003Csuppression_comment>`\n\nFor example:\n\n```bash\napiVersion: v1\nkind: Pod\nmetadata:\n  name: mypod\n  annotations:\n    checkov.io\u002Fskip1: CKV_K8S_20=I don't care about Privilege Escalation :-O\n    checkov.io\u002Fskip2: CKV_K8S_14\n    checkov.io\u002Fskip3: CKV_K8S_11=I have not set CPU limits as I want BestEffort QoS\nspec:\n  containers:\n...\n```\n\n#### Logging\n\nFor detailed logging to stdout set up the environment variable `LOG_LEVEL` to `DEBUG`.\n\nDefault is `LOG_LEVEL=WARNING`.\n\n#### Skipping directories\nTo skip files or directories, use the argument `--skip-path`, which can be specified multiple times. This argument accepts regular expressions for paths relative to the current working directory. You can use it to skip entire directories and \u002F or specific files.\n\nBy default, all directories named `node_modules`, `.terraform`, and `.serverless` will be skipped, in addition to any files or directories beginning with `.`.\nTo cancel skipping directories beginning with `.` override `CKV_IGNORE_HIDDEN_DIRECTORIES` environment variable `export CKV_IGNORE_HIDDEN_DIRECTORIES=false`\n\nYou can override the default set of directories to skip by setting the environment variable `CKV_IGNORED_DIRECTORIES`.\n Note that if you want to preserve this list and add to it, you must include these values. For example, `CKV_IGNORED_DIRECTORIES=mynewdir` will skip only that directory, but not the others mentioned above. This variable is legacy functionality; we recommend using the `--skip-file` flag.\n\n#### Console Output\n\nThe console output is in colour by default, to switch to a monochrome output, set the environment variable:\n`ANSI_COLORS_DISABLED`\n\n#### VS Code Extension\n\nIf you want to use Checkov within VS Code, give the [Prisma Cloud extension](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=PrismaCloud.prisma-cloud) a try.\n\n### Configuration using a config file\n\nCheckov can be configured using a YAML configuration file. By default, checkov looks for a `.checkov.yaml` or `.checkov.yml` file in the following places in order of precedence:\n* Directory against which checkov is run. (`--directory`)\n* Current working directory where checkov is called.\n* User's home directory.\n\n**Attention**: it is a best practice for checkov configuration file to be loaded from a trusted source composed by a verified identity, so that scanned files, check ids and loaded custom checks are as desired.\n\nUsers can also pass in the path to a config file via the command line. In this case, the other config files will be ignored. For example:\n```sh\ncheckov --config-file path\u002Fto\u002Fconfig.yaml\n```\nUsers can also create a config file using the `--create-config` command, which takes the current command line args and writes them out to a given path. For example:\n```sh\ncheckov --compact --directory test-dir --docker-image sample-image --dockerfile-path Dockerfile --download-external-modules True --external-checks-dir sample-dir --quiet --repo-id prisma-cloud\u002Fsample-repo --skip-check CKV_DOCKER_3,CKV_DOCKER_2 --skip-framework dockerfile secrets --soft-fail --branch develop --check CKV_DOCKER_1 --create-config \u002FUsers\u002Fsample\u002Fconfig.yml\n```\nWill create a `config.yaml` file which looks like this:\n```yaml\nbranch: develop\ncheck:\n  - CKV_DOCKER_1\ncompact: true\ndirectory:\n  - test-dir\ndocker-image: sample-image\ndockerfile-path: Dockerfile\ndownload-external-modules: true\nevaluate-variables: true\nexternal-checks-dir:\n  - sample-dir\nexternal-modules-download-path: .external_modules\nframework:\n  - all \noutput: cli \nquiet: true \nrepo-id: prisma-cloud\u002Fsample-repo \nskip-check: \n  - CKV_DOCKER_3 \n  - CKV_DOCKER_2 \nskip-framework:\n  - dockerfile\n  - secrets\nsoft-fail: true\n```\n\nUsers can also use the `--show-config` flag to view all the args and settings and where they came from i.e. commandline, config file, environment variable or default. For example:\n```sh\ncheckov --show-config\n```\nWill display:\n```sh\nCommand Line Args:   --show-config\nEnvironment Variables:\n  BC_API_KEY:        your-api-key\nConfig File (\u002FUsers\u002Fsample\u002F.checkov.yml):\n  soft-fail:         False\n  branch:            master\n  skip-check:        ['CKV_DOCKER_3', 'CKV_DOCKER_2']\nDefaults:\n  --output:          cli\n  --framework:       ['all']\n  --download-external-modules:False\n  --external-modules-download-path:.external_modules\n  --evaluate-variables:True\n```\n\n## Contributing\n\nContribution is welcomed!\n\nStart by reviewing the [contribution guidelines](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002FCONTRIBUTING.md). After that, take a look at a [good first issue](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fissues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).\n\nYou can even start this with one-click dev in your browser through Gitpod at the following link:\n\n[![Open in Gitpod](https:\u002F\u002Fgitpod.io\u002Fbutton\u002Fopen-in-gitpod.svg)](https:\u002F\u002Fgitpod.io\u002F#https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov)\n\nLooking to contribute new checks? Learn how to write a new check (AKA policy) [here](https:\u002F\u002Fgithub.com\u002Fbridgecrewio\u002Fcheckov\u002Fblob\u002Fmain\u002Fdocs\u002F6.Contribution\u002FContribution%20Overview.md).\n\n## Disclaimer\n`checkov` does not save, publish or share with anyone any identifiable customer information.  \nNo identifiable customer information is used to query Prisma Cloud's publicly accessible guides.\n`checkov` uses Prisma Cloud's API to enrich the results with links to remediation guides.\nTo skip this API call use the flag `--skip-download`.\n\n## Support\n\n[Prisma Cloud](https:\u002F\u002Fwww.prismacloud.io\u002F?utm_source=github&utm_medium=organic_oss&utm_campaign=checkov) builds and maintains Checkov to make policy-as-code simple and accessible. \n\nStart with our [Documentation](https:\u002F\u002Fwww.checkov.io\u002F1.Welcome\u002FQuick%20Start.html) for quick tutorials and examples.\n\n## Python Version Support\nWe follow the official support cycle of Python, and we use automated tests for supported versions of Python.\nThis means we currently support Python 3.9 - 3.13, inclusive.\nNote that Python 3.8 reached EOL on October 2024 and Python 3.9 will reach EOL in October 2025.\nIf you run into any issues with any non-EOL Python version, please open an Issue.\n","Checkov 是一个用于基础设施即代码（IaC）的静态代码分析工具，同时也是一个软件组成分析（SCA）工具，适用于镜像和开源包。它能够扫描使用Terraform、CloudFormation、Kubernetes等多种配置文件定义的云基础设施，并在构建时发现潜在的安全漏洞和配置错误。该工具支持多种编程语言和技术栈，如Python、Terraform >= 0.12.0等，并且提供了丰富的插件和集成选项。Checkov特别适合于DevOps团队，在持续集成\u002F持续部署(CI\u002FCD)流程中自动检测安全问题，确保云环境的安全性和合规性。",2,"2026-06-11 03:25:13","top_topic"]