Skip to main content
Checks that Azure PostgreSQL servers enforce SSL connections.

​
About

When you connect Microsoft Azure 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

Database connections without SSL can be intercepted, exposing credentials and data in transit. Requiring SSL/TLS on every connection protects sensitive traffic and is expected under SOC 2, ISO 27001, and PCI DSS.

​
How to Fix

Before you begin
  • Ensure you have Contributor access to the Azure subscription.
Enforce SSL on PostgreSQL
  1. Sign in to the Azure Portal and open Azure Database for PostgreSQL → your server.
  2. Go to Connection security.
  3. Set Enforce SSL connection to ENABLED and Minimum TLS version to 1.2.
  4. Save, and update your connection strings to use sslmode=require.
Once SSL 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 Microsoft Azure 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 Microsoft Azure.