Skip to main content
Checks that AWS application load balancers are not directly exposed to the internet.

​
About

When you connect Amazon Web Services (AWS) to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.

​
Why This Matters

Resources reachable directly from the internet are constantly scanned and probed for weaknesses. Removing public exposure and placing resources behind private networks or tight firewall rules dramatically shrinks your attack surface — a fundamental control in SOC 2, ISO 27001, and PCI DSS.

​
How to Fix

Before you begin
  • Ensure you have Admin access to the AWS account.
Protect the load balancer
  1. Sign in to the AWS Console and navigate to EC2 → Load Balancers.
  2. Select the load balancer and review its security group inbound rules.
  3. Restrict inbound traffic to specific IP ranges instead of 0.0.0.0/0 where possible, or change the scheme to internal for non-public services.
  4. Consider adding AWS WAF for an additional protection layer.
Once the load balancer is protected, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Amazon Web Services (AWS) integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Amazon Web Services (AWS).