prowler: Error when executing group secrets

When executing the group secrets (with or without the -m option), when reaching the lambda section, an error appears saying: [scan] ERROR No plugins to scan with!

Everything was being scanned fine, until it reached that point. Did I miss anything? Some requirements maybe?

After those errors (a lot of them, trust me), Prowler keeps scanning just fine actually.

Executed Prowler like this: ./prowler -g secrets -m 200 ./prowler -g secrets

Thank you!

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 17 (17 by maintainers)

Commits related to this issue

Most upvoted comments

[scan] ERROR No plugins to scan with! is given when the zip file is in the folder. Seems like detect-secrets is not working as it was before. Looking at it.

I have updated README.md, util/Dockerfile and Pipfile with the proper version.

We have done some tests with the IBM fork and seems pretty good, stable and it is active so the idea is to switch to that one and adapt documentation accordingly.

whispers seems to be a potential candidate to replace detect-secrets but I would keep it as it is now since it works fine using the IBM fork. I have detected false positives thoug, for example in these cases:

  • Random strings generated from CloudFormation created resources like in: arn:aws:secretsmanager:us-east-1:123456789012:secret:DBkey-jNwT8bfXoSL6-53YNmj (in a Lambda variable) That string is not a secret at all but the heuristic of detect-secrets get it as it is.
  • In an EC2 user data detects as secret the string after ssh_authorized_keys which is the ssh public key and shouldn’t be taken as secret.

To close it we should add that version constraint to the README, Dockerfile and Pipfile. Otherwise better to keep it open.

I found the issue, seems to be a matter of python version https://github.com/Yelp/detect-secrets/issues/452