-
Notifications
You must be signed in to change notification settings - Fork 460
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
AFT VPC default security group should have no inbound/outbound rules #275
Comments
Thanks for the request @domestic-fennec, I'll make a backlog with the team to discuss this enhancement. |
we are facing the same issue in our current production environment and would like to see this fixed soon as well. Thanks in advance. |
As of now, any account using AFT will trigger the AWS Security Hub Control EC2.2 It would be much appreciated if this could be resolved. Especially if nothing is using the default group, and everything is instead using the Adding the relevant documentation from the AWS Security Hub Controls Reference
https://docs.aws.amazon.com/securityhub/latest/userguide/ec2-controls.html#ec2-2 Thank you! |
We've addressed this now in the latest release of AFT! |
Describe the outcome you'd like
The default sg for the AFT VPC should have no inbound or outbound rules so that it follows AWS Foundational Security Best Practices
Is your feature request related to a problem you are currently experiencing? If so, please describe.
AWS security hub (and other cloud infosec tools) generate security warnings when setting up the AFT.
Additional context
Please note that I'm referring to the default security group that all VPC's have, not the
aft-default-sg
one thats created hereHaving done some limited research into this, it seems that using the aws_default_security_group resource with no egress and ingress blocks is a way of fixing this.
The text was updated successfully, but these errors were encountered: