Ensure ELB access logging is enabled
Elastic Load Balancer access logging should be enabled to capture detailed information about requests for security analysis.
Security Impact
Without access logs, security incidents and traffic patterns cannot be analyzed.
How to Remediate
Enable access logging on load balancers with logs stored in an S3 bucket. Configure appropriate bucket policies.
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 CIS AWS v1.5.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elb-1
- Service
- Elastic Load Balancing (ELB)
- Category
- Logging
- Severity
- MEDIUM
- CIS Benchmark
- 2.4
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial