mirror of
https://github.com/supabase/supabase.git
synced 2026-10-11 12:25:05 +03:00
*Summary* - reorganize the navigation menu to highlight modules, consolidate API security content, and move guide entries (auto-generated docs, type generation, security topics) to the intended sections - relocate the Data API hardening and custom claims RBAC guides into the API subtree, updating internal references and redirects, and fixing cross-links (including adjusting the Security reference order) - adjust data API topic references (e.g., securing guide and role management) to point to the new paths and ensure the helper link ordering follows the requested layout *Testing* - Not run (not requested) Change 1 <img width="1286" height="576" alt="image" src="https://github.com/user-attachments/assets/d903e9b0-bbfc-403f-bcb9-eee540e466db" /> Change 2 <img width="1176" height="666" alt="image" src="https://github.com/user-attachments/assets/82b3ea4c-b8d4-4cb9-ad90-6c39c8a1a997" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Reorganized API documentation structure, consolidating REST and GraphQL API guides under a dedicated API section. * Moved security-related guides to API documentation paths for better organization. * Implemented automatic redirects for old documentation links to new locations. * Updated navigation menu to reflect the restructured documentation layout. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Chris Chinchilla <chris.ward@supabase.io> Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com>
39 lines
2.0 KiB
Plaintext
39 lines
2.0 KiB
Plaintext
---
|
|
id: 'product-security'
|
|
title: 'Secure configuration of Supabase products'
|
|
description: 'Supabase provides a secure yet flexible set of products. Here is how to adjust various security settings across the various products.'
|
|
---
|
|
|
|
The Supabase [production checklist](/docs/guides/deployment/going-into-prod) provides detailed advice on preparing an app for production. While our [SOC 2](/docs/guides/security/soc-2-compliance) and [HIPAA](/docs/guides/security/hipaa-compliance) compliance documents outline the roles and responsibilities for building a secure and compliant app.
|
|
|
|
Various products at Supabase have their own hardening and configuration guides, below is a definitive list of these to help guide your way.
|
|
|
|
## Auth
|
|
|
|
- [Password security](/docs/guides/auth/password-security)
|
|
- [Rate limits](/docs/guides/auth/rate-limits)
|
|
- [Bot detection / Prevention](/docs/guides/auth/auth-captcha)
|
|
- [JWTs](/docs/guides/auth/jwts)
|
|
|
|
## Database
|
|
|
|
- [Row Level Security](/docs/guides/database/postgres/row-level-security)
|
|
- [Column Level Security](/docs/guides/database/postgres/column-level-security)
|
|
- [Hardening the Data API](/docs/guides/api/hardening-data-api)
|
|
- [Additional security controls for the Data API](/docs/guides/api/securing-your-api)
|
|
- [Custom claims and role based access control](/docs/guides/api/custom-claims-and-role-based-access-control-rbac)
|
|
- [Managing Postgres roles](/docs/guides/database/postgres/roles)
|
|
- [Managing secrets with Vault](/docs/guides/database/vault)
|
|
- [Superuser access and unsupported operations](docs/guides/database/postgres/roles-superuser)
|
|
|
|
## Storage
|
|
|
|
- [Object ownership](/docs/guides/storage/security/ownership)
|
|
- [Access control](/docs/guides/storage/security/access-control)
|
|
- The Storage API docs contain hints about required [RLS policy permissions](/docs/reference/javascript/storage-createbucket)
|
|
- [Custom roles with the storage schema](/docs/guides/storage/schema/custom-roles)
|
|
|
|
## Realtime
|
|
|
|
- [Authorization](docs/guides/realtime/authorization)
|