Rule: ELB Application and Classic Load Balancer Logging Enabled

Rule Description:

Troubleshooting Steps:

2. 1.
   Verify GxP Compliance Requirements:

   • Confirm that your organization needs to comply with GxP regulations and 21 CFR Part 11.
4. 2.
   Check Load Balancer Type:

   • Determine if you are using an ELB application or classic load balancer.
6. 3.
   Enable Logging:

   • If logging is not already enabled, proceed with the following steps based on the type of load balancer:

     ELB Application Load Balancer:

     • Open the AWS Management Console and navigate to the EC2 service.
     • Go to the "Load Balancers" section and select the appropriate ALB (Application Load Balancer).
     • Click on the "Description" tab and then select "Edit attributes".
     • Scroll down to the "Access logs" section and choose "Enabled".
     • Specify the S3 bucket where logs will be stored.
     • Optionally, you can customize the log format and log interval.
     • Click "Save" to enable logging for the ALB.

     Classic Load Balancer:

     • Open the AWS Management Console and navigate to the EC2 service.
     • Go to the "Load Balancers" section and select the relevant Classic Load Balancer.
     • Click on the "Attributes" tab and choose "Configure Access Logs" under the "Logs" section.
     • Select "Enable access logs".
     • Specify the S3 bucket and prefix for log storage.
     • Optionally, you can customize the log format and log interval.
     • Click "Save" to enable logging for the Classic Load Balancer.
8. 4.
   Verify Logging:

   • After enabling logging, you should validate that the logs are being generated and stored in the specified S3 bucket.

     ELB Application Load Balancer:

     • Open the S3 service in the AWS Management Console.
     • Navigate to the specified S3 bucket for storing the logs.
     • Look for log files with the appropriate naming convention and timestamp.
     • Confirm that log files are being regularly updated and contain the relevant log data.

     Classic Load Balancer:

     • Open the S3 service in the AWS Management Console.
     • Navigate to the specified S3 bucket and prefix for storing the logs.
     • Look for log files with the appropriate naming convention and timestamp.
     • Validate that log files are being generated and continuously updated.

Necessary Codes (if applicable):

Remediation Steps:

2. 1.
   Verify GxP Compliance Requirements:

   • Determine if your organization needs to comply with GxP regulations and 21 CFR Part 11.
4. 2.
   Enable Logging:

   • Ensure that you follow the logging enablement steps provided in the troubleshooting section based on the type of load balancer being used (ELB application or classic load balancer).
6. 3.
   Verify Logging:

   • After enabling logging, validate that the logs are being generated and stored in the specified S3 bucket by following the verification steps described in the troubleshooting section for the respective load balancer type.
8. 4.
   Document Logging Configuration:

   • Maintain proper documentation of the logging configuration for future reference and compliance audits.
10. 5.
    Regularly Monitor Logs:

    • Regularly review the generated logs to ensure continuous compliance and identify any potential issues or discrepancies.
    • Create a process for periodically reviewing and analyzing the logs.
12. 6.
    Periodically Audit Log Retention:

    • Ensure that the logs are retained for the required duration as mandated by GxP regulations and 21 CFR Part 11.
    • Perform regular audits to validate log retention and archiving practices.