Risk Level: High
Cloud Entity: Application Load Balancer
CloudGuard Rule ID: D9.AWS.NET.AG2.3.ApplicationLoadBalancer.3000.TCP
Covered by Spectral: No
Category: Networking & Content Delivery
ApplicationLoadBalancer where isPublic=true and nics contain [ subnet.routeTable.associations length()>0 ] and nics contain [ subnet.routeTable.routes contain [ destinationCidrBlock='0.0.0.0/0' and gatewayId regexMatch /gw/ ] ] should not have inboundRules contain [ port<=3000 and portTo>=3000 and protocol in ('TCP', 'ALL') and scope isPublic() and scope numberOfHosts()>=32 ]
Limit the access scope for ApplicationLoadBalancer with service 'Prevalent known internal port to only allow access in internal networks and limited scope.
If public interface exists, remove it and limit the access scope within the VPC only to applications or instances that requires access.
As a further protection, use CloudGuard Dynamic Access Leasing to limit access to SSH/Remote Desktop only from allowed sources and only when needed.
For more information please refer to: https://sc1.checkpoint.com/documents/CloudGuard_Dome9/Documentation/Network-Security/DynAccessLease.html?tocpath=Network%20Security%7C_____3
An Application Load Balancer functions at the application layer, the seventh layer of the Open Systems Interconnection (OSI) model. After the load balancer receives a request, it evaluates the listener rules in priority order to determine which rule to apply, and then selects a target from the target group for the rule action. You can configure listener rules to route requests to different target groups based on the content of the application traffic. Routing is performed independently for each target group, even when a target is registered with multiple target groups.
Updated 16 days ago