-
Notifications
You must be signed in to change notification settings - Fork 65
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
Feature 837 subframework for encrypting data at rest. #3105
Feature 837 subframework for encrypting data at rest. #3105
Conversation
- AES-GCM-SIV encryption using - None encryption
- added Base64 string class - improved documentation - upgraded BouncyCastle - changed interfaces using Base64 string class
- Introduce BinaryString interface - Implemented three BinaryString types: Base64String, HexString and PlainString - Added AES GCM SIV 192 as potential algorithm - Improved tests - Small improvements
- implemented rotation tests - improved tests - fixed detected problems - improved the documentation closes #837
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 🌟 Good work 👍
I've found some optional Issues
...e/src/test/java/com/mercedesbenz/sechub/commons/core/security/persistence/AesGcmSivTest.java
Show resolved
Hide resolved
...e/src/test/java/com/mercedesbenz/sechub/commons/core/security/persistence/AesGcmSivTest.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good to me 👍
I just have some minor optional requests for changes, please have a look at the comments.
Implements a sub-framework for encrypting data at-rest.
It is designed to encrypt text data which needs to be stored into a persistent storage (data base, object storage, file etc.).
The algorithms used fulfill the following requirements:
Allows to rotate:
HINT: The actual database encryption as described in #837 and #838 is not implemented.