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

security info page #3

Open
jelletreep opened this issue Feb 13, 2023 · 3 comments
Open

security info page #3

jelletreep opened this issue Feb 13, 2023 · 3 comments

Comments

@jelletreep
Copy link
Member

No description provided.

@dometto
Copy link
Member

dometto commented Apr 30, 2024

Does #22 address this enough or should there be a separate page?

@jelletreep
Copy link
Member Author

I don't remember what I had in mind when creating this issue 😅
We have now some tips about measures and best practices to keep a workspace secure.

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?

@dometto
Copy link
Member

dometto commented May 13, 2024

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!

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

2 participants