Ensure application load balancer does not have unrestricted security group attached
Error: Application load balancer has unrestricted security group attached
Bridgecrew Policy ID: BC_AWS_NETWORKING_16
Application load balancer has unrestricted security group attached
A publicly accessible load balancer is vulnerable to brute force login attempts and subsequent data leak/loss. Unauthorized access attempts should be restricted to minimize security risks.
We recommend your load balancer can communicate with registered targets on both the listener port and the health check port. Whenever you add a listener to your load balancer or update the health check port for a target group used by the load balancer to route requests, you must verify that the security groups associated with the load balancer allow traffic on the new port in both directions. If they do not, you can edit the rules for the currently associated security groups or associate different security groups with the load balancer.
Fix - Runtime
To restrict access to any publicly accessible load balancer, you must disable the database Publicly Accessible flag and update the VPC security group associated with the instance.
- Log in to the AWS Management Console at https://console.aws.amazon.com/.
- Open the Amazon EC2 console.
- On the navigation pane, under LOAD BALANCING, select Load Balancers.
- Select the load balancer.
- Naviagate to the Description tab.
- Navigate to the Security section, select Edit security groups.
- To associate a security group with your load balancer, select it. To remove a security group from your load balancer, clear it.
- Click Save.
To associate a security group with a load balancer, use the following command:
aws elbv2 set-security-groups --load-balancer-arn arn:aws:elasticloadbalancing:us-west-2:123456789012: loadbalancer/app/my-load-balancer/50dc6c495c0c9188 --security-groups sg-5943793c
Updated over 1 year ago