ELBs Should Use Latest AWS Security Policies

More Info:

Elastic Load Balancers should be using the latest AWS predefined security policies.

Risk Level

Medium

Address

Security

Compliance Standards

• APRA CPS 234 (Australia)
• AWS Well Architected Framework
• BSI C5 (Germany)
• Brazil LGPD
• CCPA / CPRA (California)
• CIS Critical Security Controls v8
• CMMC 2.0
• CSA Cloud Controls Matrix v4
• DPDPA
• Digital Operational Resilience Act (EU)
• Essential 8
• ISO/IEC 27017
• ISO/IEC 27018
• ISO/IEC 27701
• KSA PDPL
• MAS Technology Risk Management (Singapore)
• MITRE ATT&CK (Cloud)
• NIS2 Directive
• NIST SP 800-171
• NYDFS 23 NYCRR 500
• PCI
• SWIFT Customer Security Controls Framework
• Sarbanes-Oxley IT General Controls
• UK NCSC Cyber Assessment Framework

Triage and Remediation

Remediation

Remediation

Using Console

To remediate the misconfiguration “ELBs Must Use Latest AWS Security Policies” for AWS, you can follow the below steps using the AWS Console:

1. Log in to the AWS Management Console.
2. Navigate to the EC2 service and select “Load Balancers” from the left-hand menu.
3. Select the ELB that needs to be remediated.
4. Click on the “Listeners” tab.
5. Check if the “HTTPS” protocol is being used. If it is, then click on the “Edit” button next to the listener.
6. Under “Security Policy”, select the latest security policy from the drop-down list.
7. Click on the “Save” button to apply the changes.

By following these steps, you will remediate the misconfiguration “ELBs Must Use Latest AWS Security Policies” for AWS using the AWS console.

Using CLI

To remediate the misconfiguration “ELBs Must Use Latest AWS Security Policies” for AWS using AWS CLI, follow the below steps:

1. Check the current security policy of the ELB using the following command:

aws elb describe-load-balancers --load-balancer-names <ELB_Name> --query "LoadBalancerDescriptions[].PolicyNames[]"

2. Check the latest security policy available using the following command:

aws elb describe-load-balancer-policies --policy-names AWSConsole-SSLNegotiationPolicy-2016-08

3. Create a new policy using the latest security policy available using the following command:

aws elb create-load-balancer-policy --load-balancer-name <ELB_Name> --policy-name AWSConsole-SSLNegotiationPolicy-2016-08 --policy-type-name SSLNegotiationPolicyType --policy-attributes AttributeName=Reference-Security-Policy,AttributeValue=ELBSecurityPolicy-TLS-1-2-2017-01

4. Apply the newly created policy to the ELB using the following command:

aws elb set-load-balancer-policies-for-backend-server --load-balancer-name <ELB_Name> --instance-port 443 --policy-names AWSConsole-SSLNegotiationPolicy-2016-08

5. Verify that the new policy is applied to the ELB using the following command:

aws elb describe-load-balancers --load-balancer-names <ELB_Name> --query "LoadBalancerDescriptions[].PolicyNames[]"

After following these steps, the ELB will be using the latest AWS security policies.

Using Python

To remediate the ELBs Must Use Latest AWS Security Policies misconfiguration for AWS using Python, you can follow these steps:

1. First, make sure you have the AWS SDK for Python (Boto3) installed and configured on your local machine.

2. Next, you need to identify the ELBs that are not using the latest AWS security policies. You can do this by using the describe_load_balancers method of the boto3.client('elbv2') object. This method returns a list of all the load balancers in your account.

3. For each load balancer, you need to check if it is using the latest AWS security policy. You can do this by using the describe_load_balancer_attributes method of the boto3.client('elbv2') object. This method returns a dictionary of the load balancer attributes.

4. Check if the load balancer is using the latest security policy by looking for the ssl_policy attribute in the dictionary. If the value of this attribute is not ELBSecurityPolicy-2016-08, then the load balancer is not using the latest security policy.

5. To update the load balancer to use the latest security policy, you can use the modify_load_balancer_attributes method of the boto3.client('elbv2') object. You need to set the ssl_policy attribute to ELBSecurityPolicy-2016-08.

Here’s the Python code to remediate the ELBs Must Use Latest AWS Security Policies misconfiguration:

import boto3

# create an ELB client object
elbv2 = boto3.client('elbv2')

# get a list of all the load balancers in your account
load_balancers = elbv2.describe_load_balancers()

# iterate through each load balancer
for lb in load_balancers['LoadBalancers']:
    # get the load balancer attributes
    lb_attributes = elbv2.describe_load_balancer_attributes(LoadBalancerArn=lb['LoadBalancerArn'])
    
    # check if the load balancer is using the latest security policy
    if lb_attributes['Attributes']['SslPolicy'] != 'ELBSecurityPolicy-2016-08':
        # update the load balancer to use the latest security policy
        elbv2.modify_load_balancer_attributes(
            LoadBalancerArn=lb['LoadBalancerArn'],
            Attributes=[
                {
                    'Key': 'ssl_policy',
                    'Value': 'ELBSecurityPolicy-2016-08'
                },
            ]
        )

Note: This code only updates the ELBs that are not using the latest AWS security policies. If all your ELBs are already using the latest security policy, then this code will not make any changes.

Using Terraform

resource "aws_elb" "example" {
  name               = "EXISTING_ELB_NAME" # replace with your Classic ELB name
  availability_zones = ["us-east-1a"]      # replace with your AZs

  listener {
    instance_port      = 80
    instance_protocol  = "http"
    lb_port            = 443               # listener port being remediated
    lb_protocol        = "https"
    ssl_certificate_id = "ARN_OF_EXISTING_ACM_OR_IAM_CERT"
  }

  # ...other existing ELB arguments...
}

# Attach the latest AWS predefined security policy to the ELB listener.
# Include *all* policies that must remain (e.g., proxy protocol), not just TLS.
resource "aws_load_balancer_listener_policy" "elb_tls_policy_443" {
  load_balancer_name = aws_elb.example.name
  load_balancer_port = 443

  policy_names = [
    "ELBSecurityPolicy-TLS-1-2-2017-01", # required by the check
    # "OTHER_EXISTING_POLICY_NAME_IF_ANY", # keep any non-TLS policies you already use
  ]
}

This change updates the listener’s policy in place and does not force replacement of the ELB itself, but it does replace the entire policy set on that listener; ensure every policy you want to keep is listed in policy_names.

To verify, terraform plan should show an aws_load_balancer_listener_policy.elb_tls_policy_443 resource being created or updated so that policy_names contains ELBSecurityPolicy-TLS-1-2-2017-01 (plus any other existing policies you chose to retain).

Additional Reading:

• https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-security-policy-table.html