Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

Checks that GCP services are accessible over HTTPS.

​
Why This Matters

Unencrypted HTTP traffic exposes data in transit to interception, man-in-the-middle attacks, and eavesdropping. Enforcing HTTPS with current TLS versions (1.2+) ensures data integrity and confidentiality. This is a baseline requirement for PCI DSS, SOC 2, and GDPR.

​
What DSALTA Checks

DSALTA connects to your Google Cloud Platform (GCP) environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → Google Cloud Platform (GCP).

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Navigate to your Google Cloud Platform (GCP) console or load balancer configuration.
  2. Ensure all endpoints serve traffic over HTTPS (port 443) with a valid TLS certificate.
  3. Configure HTTP to HTTPS redirect rules so that any HTTP (port 80) request is automatically redirected with a 301 status.
  4. Set the minimum TLS version to TLS 1.2 (TLS 1.3 preferred).
  5. Disable any deprecated protocols (SSLv3, TLS 1.0, TLS 1.1).
  6. Verify the configuration by testing with curl -I http://yourdomain.com — you should receive a 301 redirect to the HTTPS URL.
  7. Once configured, DSALTA will detect the change on the next sync cycle and update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the Google Cloud Platform (GCP) integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in Google Cloud Platform (GCP).