aquasecurity / aquasecurity/cloudsploit
RFC-1918
Open
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 751
- Avg merge
- 11d 9h
- Merged PRs (30d)
- 3
Description
Can someone please explain this check and how it is relevant to aws security groups?
I have private subnet servers and this is triggering as failed for allowing 192.168.0.0/16 traffic on their SGs.
Contributor guide
Research direction
Start by locating the RFC-1918 check and its AWS security-group handling. Review why allowing 192.168.0.0/16 is reported as failed, then document how the check relates to private subnet servers and what configuration is expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100