Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insecure Default Configuration #16

Open
hija opened this issue May 20, 2024 · 0 comments
Open

Insecure Default Configuration #16

hija opened this issue May 20, 2024 · 0 comments

Comments

@hija
Copy link

hija commented May 20, 2024

Hi there,

if one runs the default migration security warnings pop up in supabase. These security warnings are related to Row-Level-Security and the Security Definer View.

As a developer, I would like to have a migration which avoids these errors in the first place, so it is easier to have a safe supabase environment without the manual effort which is necessary now.

I am not 100% sure, but I think some steps to achieve this would be:

RLS

  1. Enable RLS on all tables
  2. Determine which tables need anonymous access (and which level of access specifically)
  3. Create policies for those

Security Definer View
(I am not sure about this yet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant