This rule highlights the necessity of enabling logging for ELB application and classic load balancers.
Rule | ELB application and classic load balancer logging should be enabled |
Framework | RBI Cyber Security Framework |
Severity | ✔ High |
Rule Description:
Enabling logging for the Elastic Load Balancer (ELB) application and Classic Load Balancer is a requirement of the RBI (Reserve Bank of India) Cyber Security Framework. This rule ensures that logs for the load balancers are captured and retained for analysis, monitoring, and auditing purposes in compliance with the framework.
Troubleshooting Steps:
If logging for ELB application and Classic Load Balancer is not enabled, follow these troubleshooting steps:
Necessary Codes:
If the load balancer logging configuration needs to be updated, use the following AWS CLI command:
aws elbv2 modify-load-balancer-attributes --load-balancer-arn <load_balancer_arn> --attributes file://logging-attributes.json
Ensure you replace
<load_balancer_arn>
with the actual ARN (Amazon Resource Name) of the load balancer. Create a JSON file named logging-attributes.json
with the desired logging configuration settings, including the Amazon S3 bucket name and optional S3 prefix.Step-by-Step Guide for Remediation:
Follow these steps to enable logging for ELB application and Classic Load Balancer:
Ensure that you regularly monitor the logs to detect any security issues, identify performance bottlenecks, or troubleshoot operational problems. The logs should be retained for the minimum required duration as mandated by the RBI Cyber Security Framework.
Note: Remember to comply with the RBI regulations and guidelines while setting up and configuring logging for ELB application and Classic Load Balancer.