aquasecurity / aquasecurity/cloudsploit

GCP CIS benchmark - "Nothing to collect"

Open
#526 5 comments 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
3.8k
Forks
751
Avg merge
11d 9h
Merged PRs (30d)
3

Description

Hello,

After triggering the CIS compliance check nothing is being retrieved. I am passing the path to the config file. It doesn't matter which switch was used ("cis","cis","cis2"). The console output is multiple "Skipped plugin (...)" then "Nothing to collect".

Command used: **./index.js --config ./config.js --compliance=cis**

[output.txt](https://github.com/aquasecurity/cloudsploit/files/5904295/output.txt)

Contributor guide

Open the contributing guide

Research direction

Start with index.js and the config.js path used in ./index.js --config ./config.js --compliance=cis, then review output.txt alongside the repeated "Skipped plugin" messages. Reproduce the CIS check and trace why it ends with "Nothing to collect"; done means the GCP CIS check retrieves findings instead of skipping all plugins.

Written by the indexing model from the issue text.

Assessment

Tech stack
gcp, javascript
Domain
cloud, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.