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 layer #1200

Open
wajda opened this issue Apr 18, 2023 · 2 comments
Open

Security layer #1200

wajda opened this issue Apr 18, 2023 · 2 comments
Labels

Comments

@wajda
Copy link
Contributor

wajda commented Apr 18, 2023

This is an umbrella issue for discussing and brainstorming security aspects of the system, basically those A's - Authentication, Authorisation, Access control, Auditing etc.

@wajda wajda added the feature label Apr 18, 2023
@cerveada cerveada added this to Spline Apr 18, 2023
@github-project-automation github-project-automation bot moved this to New in Spline Apr 18, 2023
@wajda wajda added Epic and removed feature labels Apr 18, 2023
@wajda
Copy link
Contributor Author

wajda commented Apr 18, 2023

As a minimum, we need to implement an authorisation mechanism (OAuth, Kerberos) for both APIs, and access control on computational level lineage (expressions) and operation details, that might leak some sensitive meta-information about security jobs logic etc.

@wajda
Copy link
Contributor Author

wajda commented Apr 18, 2023

@ArpanABSA

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

No branches or pull requests

1 participant