mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 09:55:06 +03:00
Stephen Morgan
b17a33fb26
Some light copy cleanup for privatelink documentation based on feedback. Fixes PRODSEC-232 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated PrivateLink guidance with revised architecture, supported ports, routing, and security group instructions. * Added labeled connectivity tests for direct PostgreSQL and PgBouncer connections. * Added connection-string examples for both connection methods. * Replaced public-connectivity instructions with optional network restriction steps and reorganized limitations guidance. * Refined PrivateLink availability wording across platform security documentation. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
67 lines
2.8 KiB
Plaintext
67 lines
2.8 KiB
Plaintext
---
|
|
id: 'platform-security'
|
|
title: 'Secure configuration of Supabase platform'
|
|
description: 'Supabase provides a secure yet flexible platform. Here is how to adjust various security settings across the platform.'
|
|
---
|
|
|
|
The Supabase hosted platform provides a secure by default configuration. Some organizations may however require further security controls to meet their own security policies or compliance requirements.
|
|
|
|
Access to additional security controls can be found under the [security tab](/dashboard/org/_/security) for organizations.
|
|
|
|
## Available controls
|
|
|
|
<Admonition type="note">
|
|
|
|
Additional security controls are under active development. Any changes will be published here and
|
|
in our [changelog](/changelog).
|
|
|
|
</Admonition>
|
|
|
|
### Enforce multi-factor authentication (MFA)
|
|
|
|
Organization owners can choose to enforce MFA for all team members.
|
|
|
|
For configuration information, see [Enforce MFA on Organization](/docs/guides/platform/mfa/org-mfa-enforcement)
|
|
|
|
### SSO for organizations
|
|
|
|
Supabase offers single sign-on (SSO) as a login option to provide additional account security for your team. This allows company administrators to enforce the use of an identity provider when logging into Supabase.
|
|
|
|
For configuration information, see [Enable SSO for Your Organization](/docs/guides/platform/sso).
|
|
|
|
### Postgres SSL enforcement
|
|
|
|
Supabase projects support connecting to the Postgres DB without SSL enforced to maximize client compatibility. For increased security, you can prevent clients from connecting if they're not using SSL.
|
|
|
|
For configuration information, see [Postgres SSL Enforcement](/docs/guides/platform/ssl-enforcement)
|
|
|
|
<Admonition type="note">
|
|
|
|
Controlling this at the organization level is on our roadmap.
|
|
|
|
</Admonition>
|
|
|
|
### Network restrictions
|
|
|
|
Each Supabase project comes with configurable restrictions on the IP ranges that are allowed to connect to Postgres and its pooler ("your database"). These restrictions are enforced before traffic reaches the database. If a connection is not restricted by IP, it still needs to authenticate successfully with valid database credentials.
|
|
|
|
For configuration information, see [Network Restrictions](/docs/guides/platform/network-restrictions)
|
|
|
|
<Admonition type="note">
|
|
|
|
Controlling this at the organization level is on our roadmap.
|
|
|
|
</Admonition>
|
|
|
|
### PrivateLink
|
|
|
|
PrivateLink provides enterprise-grade private network connectivity between your AWS VPC and your Supabase database using AWS VPC Lattice. This eliminates exposure to the public internet by creating a secure, private connection that keeps your database traffic within the AWS network backbone.
|
|
|
|
For configuration information, see [PrivateLink](/docs/guides/platform/privatelink)
|
|
|
|
<Admonition type="note">
|
|
|
|
To establish PrivateLink with a Read Replica, reach out to your account rep.
|
|
|
|
</Admonition>
|