Skip to main content
MEDIUMELBSecurity

ELB Security Policy Outdated

elb-security-policy-outdated

What this rule checks

Detects load balancers using outdated TLS security policies.

How to fix it

  1. 1Update to ELBSecurityPolicy-TLS13-1-2-2021-06 or newer
  2. 2Remove support for deprecated protocols
FlaggedThe HTTPS listener omits SslPolicy, so it falls back to ELB's default ELBSecurityPolicy-2016-08, which still permits TLS 1.0 and is on the check's outdated list. An omitted SSL policy on an HTTPS/TLS listener now flags for this reason.
import * as ec2 from 'aws-cdk-lib/aws-ec2';
import * as elbv2 from 'aws-cdk-lib/aws-elasticloadbalancingv2';
import * as acm from 'aws-cdk-lib/aws-certificatemanager';

const vpc = new ec2.Vpc(this, 'Vpc');
const cert = new acm.Certificate(this, 'Cert', { domainName: 'example.com', validation: acm.CertificateValidation.fromDns() });
const alb = new elbv2.ApplicationLoadBalancer(this, 'Alb', { vpc, deletionProtection: true });
alb.addListener('Https', {
  port: 443,
  certificates: [elbv2.ListenerCertificate.fromCertificateManager(cert)],
  defaultAction: elbv2.ListenerAction.fixedResponse(200),
});
FixedsslPolicy: SslPolicy.RECOMMENDED_TLS (ELBSecurityPolicy-TLS13-1-2-2021-06) is a modern policy not on the outdated list, so the finding clears.
import * as ec2 from 'aws-cdk-lib/aws-ec2';
import * as elbv2 from 'aws-cdk-lib/aws-elasticloadbalancingv2';
import * as acm from 'aws-cdk-lib/aws-certificatemanager';

const vpc = new ec2.Vpc(this, 'Vpc');
const cert = new acm.Certificate(this, 'Cert', { domainName: 'example.com', validation: acm.CertificateValidation.fromDns() });
const alb = new elbv2.ApplicationLoadBalancer(this, 'Alb', { vpc, deletionProtection: true });
alb.addListener('Https', {
  port: 443,
  certificates: [elbv2.ListenerCertificate.fromCertificateManager(cert)],
  sslPolicy: elbv2.SslPolicy.RECOMMENDED_TLS,
  defaultAction: elbv2.ListenerAction.fixedResponse(200),
});

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

AWS::ElasticLoadBalancingV2::Listener

Compliance frameworks

SOC2HIPAAPCI-DSSNIST

AWS documentation

Read the AWS guidance

Intentional? Suppress this finding

Sometimes a flag is deliberate โ€” a genuinely public endpoint, say. You can dismiss elb-security-policy-outdated and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "elb-security-policy-outdated", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::elb-security-policy-outdated',
  reason: 'Why this is intentional',
});

Use the rule ID elb-security-policy-outdated shown above โ€” not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs โ†’

Catch this in your stack

$ npx cdk-insights scan

CDK Insights runs this and 118+ other rules locally against your synthesised CDK app โ€” free, no account, your code never leaves your machine.

More ELB rules