aquasecurity / aquasecurity/cloudsploit
CIS Checks return "Nothing to collect" when running against GCP
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 751
- Avg merge
- 11d 9h
- Merged PRs (30d)
- 3
Description
Every check works fine (HIPAA, PCI, etc.) or even default cloudsploit checks, but when I give CIS to the `--compliance=` flag, I get the following output from running `./index.js --config ./config.js --compliance=cis` - The same happens for cis1, cis2.
(I'm only showing the last 7 lines in stdout because it's too much and it's the same DEBUG: * ourtput for every check)
```
DEBUG: Skipping plugin Restrict VPN Peer IPs because it is not used for compliance programs
DEBUG: Skipping plugin Disable VM IP Forwarding because it is not used for compliance programs
DEBUG: Skipping plugin Trusted Image Projects because it is not used for compliance programs
DEBUG: Skipping plugin Skip Default Network Creation because it is not used for compliance programs
DEBUG: Skipping plugin Location-Based Service Restriction because it is not used for compliance programs
DEBUG: Skipping plugin Disable Service Account Creation because it is not used for compliance programs
ERROR: Nothing to collect.
```
Should I do something extra? Or why is Cloudsploit skipping every check?
Contributor guide
Research direction
Start with the reported command in index.js using config.js and --compliance=cis, then compare its behavior with the working default and other compliance checks. Reproduce the output and trace why CIS checks are skipped; done means CIS, cis1, or cis2 collects checks against GCP instead of reporting "Nothing to collect."
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, javascript
- Domain
- cli, cloud, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100