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

Determine security strategy for correctly limiting data visibility and manipulation[ENG] #300

Open
KCCPMG opened this issue Mar 7, 2024 · 0 comments

Comments

@KCCPMG
Copy link
Contributor

KCCPMG commented Mar 7, 2024

As things generally stand currently, users who can access the application can view and modify information about students or goals which have not been assigned to them. On the backend, there is a check in the routers/iep file on the editGoal mutation (pending PR #272), but this otherwise seems largely unaddressed. We should determine what level of security is needed, and whether the approach in editGoal should be repeated or replaced with a more robust solution, such as RLS as previously mentioned by @codetheweb .

@KCCPMG KCCPMG added this to Compass Mar 7, 2024
@KCCPMG KCCPMG converted this from a draft issue Mar 7, 2024
@KCCPMG KCCPMG moved this from Todo to Blocked / On hold in Compass Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Blocked / On hold
Development

No branches or pull requests

1 participant