-
Notifications
You must be signed in to change notification settings - Fork 1
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
security info page #3
Comments
Does #22 address this enough or should there be a separate page? |
I don't remember what I had in mind when creating this issue 😅 Maybe we need to clarify a bit more the security status of different workspace types, although this probably comes down to: SANE workspaces for highly sensitive data and 'the rest', or can we make some distinction in between? Is there a demand for that? I am thinking about e.g. datasets with commercial value. Maybe SANE is overkill, but would it be okay to use all other catalogue items or only certain catalog items... So short answer, I think #22 addresses this enough, but maybe we can discuss at some point whether the "geschiktheidsclassficatie" the was done for the platform applies to all catalogue items, or if not, for which it applies, and which catalogue items are used at users responsibility? |
Yes, good idea. 👍 I've briefly mentioned SANE in #22, but we should think about how to present all the security aspects to users. Let's just keep this issue open as a reminder of that! |
No description provided.
The text was updated successfully, but these errors were encountered: