Load balancers must have access logging enabled
Medium
Cross-cloud
General
appgw-diagnostics-2
Applies to
Microsoft.Network/applicationGatewaysAWS::ElasticLoadBalancingV2::LoadBalancer
What CGPulse checks
A resource passes this rule when diagnosticSettings.hasLogs must equal true OR accessLogsEnabled must equal true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Enable logging to capture audit and operational events for security investigation. In AWS Console: Resource > Settings > enable logging. See: https://docs.aws.amazon.com/prescriptive-guidance/latest/logging-monitoring-best-practices/welcome.html
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Cross-cloud rules
- Block storage volumes must be encrypted
- Cache service security hardening
- Cache services must enforce TLS encryption in transit
- Container registry security hardening
- Database authentication must use managed identities
- Databases must not be publicly accessible
- IAM password policy must require minimum length of 14
- Key management service security hardening