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

Is opendistro GDPR compliant? #4

Closed
pavolloffay opened this issue Mar 11, 2019 · 4 comments
Closed

Is opendistro GDPR compliant? #4

pavolloffay opened this issue Mar 11, 2019 · 4 comments

Comments

@pavolloffay
Copy link

Hi,

is Opendistro fully GDPR compliant like SearchGuard https://search-guard.com/gdpr-compliance-elasticsearch?

@elfisher
Copy link
Contributor

Hi @pavolloffay Open Distro for Elasticsearch Security provides a variety of security tools like encryption in transit, role based access control at the index, document, and field-level. It also provides an audit logging feature to track access to your cluster and log security and compliance related events.

It is up to the user to configure their cluster correctly for GDPR, but the security plugin provides tools to help meet compliance.

@pavolloffay
Copy link
Author

thanks @elfisher. To be honest I do not know what exactly is required for GDPR compliance. As GDPR probably requires more "checkboxes" it would be helpful to provide more documentation how each requirements can be met with opendistro. At the moment I found only this https://opendistro.github.io/for-elasticsearch/features/security.html

@fatalglitch
Copy link

It's important to note that even SearchGuard does not make you GDPR compliant, but it helps with some of the requirements. There's a lot more than just RBAC, Auditing, and Encryption that are required to be compliant. At a high level, many of the core functions of RBAC, Auditing, and Encryption appear to be in Open Distro for Elasticsearch that help with being compliant for GDPR.

@elfisher
Copy link
Contributor

@pavolloffay Thanks for opening this issue. As there isn't a direct issue or feature request for the project, I'm going to go ahead and close the issue. Thanks.

willyborankin added a commit to willyborankin/security that referenced this issue Apr 15, 2024
Moved test:
 - SecurityConfigApiActionTest into ConfigRestApiIntegrationTest

Test with the Legacy prefix removed since new tests use randomization for paths

Signed-off-by: Andrey Pleskach <ples@aiven.io>
willyborankin added a commit to willyborankin/security that referenced this issue Apr 29, 2024
Moved test:
 - SecurityConfigApiActionTest into ConfigRestApiIntegrationTest

Test with the Legacy prefix removed since new tests use randomization for paths

Signed-off-by: Andrey Pleskach <ples@aiven.io>
willyborankin added a commit to willyborankin/security that referenced this issue May 1, 2024
Moved test:
 - SecurityConfigApiActionTest into ConfigRestApiIntegrationTest

Test with the Legacy prefix removed since new tests use randomization for paths

Signed-off-by: Andrey Pleskach <ples@aiven.io>
willyborankin added a commit to willyborankin/security that referenced this issue May 6, 2024
Moved test:
 - SecurityConfigApiActionTest into ConfigRestApiIntegrationTest

Test with the Legacy prefix removed since new tests use randomization for paths

Signed-off-by: Andrey Pleskach <ples@aiven.io>
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

3 participants