feat(storage): enable at-rest encryption on storage container #963
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
git commit -S -m "YOUR_COMMIT_MESSAGE"
See cryostatio/cryostat#690
Description of the change:
Enables the
cryostat-storage
flag to turn on SeaweedFS at-rest data encryption.Motivation for the change:
Improves data security and integrity by ensuring that at-rest files are encrypted. This is not a full solution because Seaweed stores the encryption/decryption key in the file metadata (so that the file can be decrypted later), and in our usage the metadata is stored on the same persistent volume as the encrypted file. So, any attack vectors where the attacker has direct access to the PV bypassing authn/authz checks or the S3 API will still allow the attacker to compromise the data.
How to manually test:
REST_ENCRYPTION_ENABLE=1
cryostat-storage
container logs within the Pod and look for:-filer.encryptVolumeData
should be passed as an argument to theexec weed
invocation.