Skip to main content
Checks that GCP redirects HTTP traffic to HTTPS.

​
About

When you connect Google Cloud Platform (GCP) to DSALTA, the platform evaluates this control on every sync using read-only API access. If the requirement is not met, DSALTA activates this check.

​
Why This Matters

Traffic sent over plain HTTP can be intercepted or tampered with in transit. Enforcing HTTPS with a current TLS version protects data confidentiality and integrity and is a baseline requirement for PCI DSS, SOC 2, and GDPR.

​
How to Fix

Before you begin
  • Ensure you have administrator access to Google Cloud Platform (GCP).
Enforce HTTPS
  1. Open the relevant endpoint or load balancer configuration in Google Cloud Platform (GCP).
  2. Ensure all traffic is served over HTTPS with a valid TLS certificate (TLS 1.2 or higher).
  3. Configure a 301 redirect from HTTP to HTTPS and disable deprecated protocols (SSLv3, TLS 1.0/1.1).
  4. Verify with curl -I http://yourdomain — you should receive a 301 to the HTTPS URL.
Once HTTPS is enforced, 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).