AWS securityhub documentation change
Summary
Updated 'ELB' to 'Elastic Load Balancing' in the WAF/LB configuration recommendation
Security assessment
Change is terminological only. The existing security guidance about using WAF with load balancers remains unchanged, with no new security features or vulnerability fixes introduced.
Diff
diff --git a/securityhub/latest/userguide/exposure-ec2-instance.md b/securityhub/latest/userguide/exposure-ec2-instance.md index 289fe98ce..4558e8884 100644 --- a//securityhub/latest/userguide/exposure-ec2-instance.md +++ b//securityhub/latest/userguide/exposure-ec2-instance.md @@ -187 +187 @@ Consider the following options for alternative access methods: - * **Use WAF and ELB or Application Load Balancer** – For instances that are running web applications, consider using an LB combined with AWS Web Application Firewall (WAF). LBs can be configured to allow your instances to run in private subnets while the LB runs in a public subnet and handles internet traffic. Adding a WAF to your load balancer provides additional protection against web exploits and bots. + * **Use WAF and Elastic Load Balancing or Application Load Balancer** – For instances that are running web applications, consider using an LB combined with AWS Web Application Firewall (WAF). LBs can be configured to allow your instances to run in private subnets while the LB runs in a public subnet and handles internet traffic. Adding a WAF to your load balancer provides additional protection against web exploits and bots.