Taylor

Thank you for your contribution! Apologies for missing it, but the check was updated with this PR: https://github.com/bridgecrewio/checkov/pull/6200

@gruebel @ferrarimarco I'm told by the engineer who implemented the baseline feature that we did not include passing checks to save space.

Hi @junhu73, I'd be happy to help, but I'm not clear on your questions. 1. The policies are defined such that if there is a resource of the type mentioned...

Hi @AlexAtkinson thanks for pointing this out! We'll update this listing. Bridgecrew has been merged into Prisma Cloud by Palo Alto Networks and so to use this extension, you will...

We appreciate the feedback, @timoa. Certainly this is not the experience we want you to have. Rest assured that Checkov as an open source tool is and will remain open...

@cloudtriquetra @forstops we have an experimental feature that does take into account `after_unknown`. If you use `EVAL_TF_PLAN_AFTER_UNKNOWN`, such as `EVAL_TF_PLAN_AFTER_UNKNOWN=true checkov -f plan.json`, it will consider this section as part...

@cloudtriquetra thanks for giving it a try. Can you add more details for what's not working? Are you seeing errors or not the results you expected? If the first, can...

We've reversed some of the changes and improved this check. Can you try again? I tested on the code samples given here and they are not flagged anymore.

Glad to hear it! I'm closing this issue but please reopen it if you see a large volume of FPs for this check.

Hi folks, you can increase the entropy level required to flag findings using the env variable `CHECKOV_ENTROPY_KEYWORD_LIMIT`. `CHECKOV_ENTROPY_KEYWORD_LIMIT=3.6` removes many of these FPs. You can also use `--skip-check` to skip...