Ensure internal load balancers are used for internal services
Internal services should use internal load balancers to prevent internet exposure.
Security Impact
Internet-facing load balancers for internal services expose them to external attacks.
How to Remediate
Create internal load balancers (scheme: internal) for services that should not be internet-accessible.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Elastic Load Balancing (ELB) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elb-14
- Service
- Elastic Load Balancing (ELB)
- Category
- Network Security
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial