-
Notifications
You must be signed in to change notification settings - Fork 21
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
Data access monitoring #171
Labels
Comments
One way to identify the sensitivity of data could be with labels on datasets. Few more questions, that insights can provide answers to:
|
Usage history (access logs) data collection will be discussed in detail in #265 |
lifosmin
referenced
this issue
in lifosmin/guardian
Aug 31, 2023
* feat(guardian): introduce access list and get api * chore: update plural name for access * chore: add access field in appeal * chore: add role field in access * feat: add access revoke api * feat: add bulk revoke access api * chore: deprecate RevokeAppeal and RevokeAppeals rpcs * chore: change revoke accesses API method to PUT * feat: add list user accesses API and add more params * chore: remove created_at param from ListUserAccessesRequest * chore: add created_by field * add: add order_by param in list access * change: rename Access to Grant * chore: fix format issues Co-authored-by: Ravi Suhag <suhag.ravi@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Guardian can manage access across multiple providers. But it is still hard for data governance managers to monitor the different aspects of data access.
Goal:
With data access monitoring in Guardian, we aim to provide answers to the following questions.
Scope:
Access monitoring can be tracked across different sections
The text was updated successfully, but these errors were encountered: