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

Encyrption at rest use-case problem description is too narrow #32

Open
k-wall opened this issue Jan 25, 2024 · 0 comments
Open

Encyrption at rest use-case problem description is too narrow #32

k-wall opened this issue Jan 25, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@k-wall
Copy link
Contributor

k-wall commented Jan 25, 2024

The problem description is too narrow. It focuses on the cloud use-case and omits to mention that the same problem may exist within an organisation.

Tom said:

This is a specific example of a problem that can exist even without cloud in the picture. It's simply about the trust boundaries within an organisation. If compliance requirements dictate that the people (internal or external) who run the Kafka cluster (and therefore have broker access) should not be trusted to see the business data being stored there (e.g. by some other business function in the org) then essentially the same problem exists.

If we're aiming this at decision makers then let's not give them the excuse of misunderstanding and thinking "we run Kafka on-prem, so this doesn't apply to us". I.e. describe the general problem and use cloud only as ac concrete example of it.

Originally posted by @tombentley in #25 (comment)

@k-wall k-wall changed the title use-case problem description is too narrow Encyrption at rest use-case problem description is too narrow Jan 25, 2024
@gracegrimwood gracegrimwood added the documentation Improvements or additions to documentation label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants