-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make two new checks to discern between egress and ingress SG rules #4945
Comments
Hey @pedrooot, could I work on this issue Thanks! |
hey! @abant07 sure! It would be great! |
Sounds good. I will do like I have done before. I will give a write up on the issue and how I intend to implement it. |
Just to clarify, is the issue asking to make two separate checks for ec2_securitygroup_allow_wide_open_public_ipv4. One for ingress and the other for egress. Does the ec2_securitygroup_allow_wide_open_public_ipv4 check currently combine both ingress and egress check in 1 file? Or does it only contain ingress? |
We are not sure about the development of these checks. Would you mind waiting until we decide what to do with them? This way, we won't discard your work. I'll let you know as soon as we make a decision, thanks for all Amogh |
Sure no problem |
Sure! It would be great! @abant07 |
Hey @pedrooot Am I okay to go forward with this issue? |
New feature motivation
This check:
ec2_securitygroup_allow_wide_open_public_ipv4
check if the security group has any rules that allow ingress or egress traffic. It does not differentiate between the two cases.Solution Proposed
Make two new checks, one for egress and other for ingress.
Describe alternatives you've considered
Additional context
#4936
The text was updated successfully, but these errors were encountered: