dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix: update encryption requirements for hipaa (#18672)

Browse Source
This commit is contained in:
Inian authored and GitHub committed 2023-11-02 20:19:14 +00:00
1 parent 1054739b5e
commit e7ad151ecd
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/pages/guides/platform/shared-responsibility-model.mdx
+1 -1
View File
@@ -55,7 +55,7 @@ You can use Supabase to store and process Protected Health Information (PHI). Yo
- Turning on [SSL Enforcement](/docs/guides/platform/ssl-enforcement).
- Enabling [Network Restrictions](/docs/guides/platform/network-restrictions).
- Disabling [Supabase AI editor](https://supabase.com/dashboard/org/_/general) in our dashboard.
- Encrypting PHI in your database. Consider using pgsodium's [Transparent Column Encryption](https://github.com/michelp/pgsodium#transparent-column-encryption) which comes bundled in with every Supabase project.
- Complying with encryption requirements in the HIPAA Security Rule. Data is encrypted at rest and in transit by Supabase. You can consider encrypting the data at your application layer.
- Not using [Edge functions](/docs/guides/functions) to process PHI.
- Not storing PHI in [public Storage buckets](/docs/guides/storage/buckets/fundamentals#public-buckets).