Replies: 5 comments 2 replies
-
Hey @rawc0der, |
Beta Was this translation helpful? Give feedback.
-
Yes, exactly - as a user you can use an optional CLI flag to transform a pure report to -> pseudonymised report. This involves integrating with some form of Cryptographic service for owning the Key for Mapping File Encryption/Decryption (this is the whole crux). Problem Scope To add extra protection a Private Key from any external Key Management Service can be used to Obfuscate/Pseudonymise entire report keys metadata Possible CLI flags:
Definitely recommend checking out SOPS for possible initial solution path. Desired outcome (least technical effort):
What do you think? |
Beta Was this translation helpful? Give feedback.
-
This sounds good to me but I just had some questions in my mind.
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the clarification @rawc0der! |
Beta Was this translation helpful? Give feedback.
-
Great Discussions!, Can I contribute to this too... like some sort of non-code contribution. Just a beginner, would love to be a part of it. |
Beta Was this translation helpful? Give feedback.
-
Hi @rakshitgondwal - lets discuss the details here.
Problem:
Reports contain sensitive information like Pod names, Namespaces, Resource names etc that are somerimes classified as strictly confidential to a specific group or even more restrictive individual person (C3, C4 data classification).
For example the User has a Namespace with his name and a Pod name with a newly developed unreleased Product -- this is considered Confidential info, not supposed to be visible to anyone else.
The idea behind solving this is to use
Let me know what you think about this whole idea, thanks!
Beta Was this translation helpful? Give feedback.
All reactions