Skip to main content
Checks that GCP Compute instances are not directly exposed to the internet.

​
About

When you connect Google Cloud Platform (GCP) 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 the appropriate admin role on the project.
Remove public exposure
  1. Sign in to the Google Cloud Console and open the affected resource.
  2. For Compute instances, remove the External IP (set to None) and use Cloud NAT for outbound access.
  3. Review firewall rules and remove any ingress from 0.0.0.0/0 on sensitive ports.
  4. For KMS, remove any IAM binding for allUsers or allAuthenticatedUsers.
Once the resource is no longer publicly exposed, 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 Google Cloud Platform (GCP) 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 Google Cloud Platform (GCP).