AWSOverview
Use secure listeners to support encrypted communication between clients and your load balancers. You can use AWS Certificate Manager (ACM) or AWS Identity and Access Management (IAM) to manage the server certificates installed on your load balancer. You can use the Server Name Indication (SNI) protocol to serve multiple secure websites using a single secure listener. SNI is automatically enabled for your load balancer when you associate more than one server certificate with a secure listener.
Remediation guidance
AWS remediation
Console
- Open NLB listeners.
- Add TLS listener on port 443.
- Attach ACM certificate.
AWS CLI
aws elbv2 create-listener \
--load-balancer-arn <nlb-arn> \
--protocol TLS \
--port 443 \
--certificates CertificateArn=<acm-certificate-arn> \
--default-actions Type=forward,TargetGroupArn=<target-group-arn>
References
- https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-tls-listener.html
- https://docs.aws.amazon.com/cli/latest/reference/elbv2/create-listener.html
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
AWS
Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Network Load Balancer uses TLS Listener
Connectors
Covered asset types
Expected check: eq []
{loadBalancers(where:{type:"network",listensOnHTTPListener_NONE:{hasCertificate:true}}){...AssetFragment}}
