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

Encrypt kcap #52

Open
rabbitstack opened this issue Mar 1, 2021 · 0 comments
Open

Encrypt kcap #52

rabbitstack opened this issue Mar 1, 2021 · 0 comments
Labels
needs: config Indicates the issue requires changes in the config file/flags needs: docs Indicates that the issue needs documentation updates scope: kcap Anything related to captures

Comments

@rabbitstack
Copy link
Owner

rabbitstack commented Mar 1, 2021

Description

In stringent security environments, it might be desirable to encrypt all the capture data including processes, handles, and, of course, kernel events. For this purpose, the kcap configuration section should get a couple of new attributes including the encryption algorithm (e.g. aes) and the actual encryption key. We should provide the ability to load the key from alternative sources, e.g. environment variables or vault stores. The encryption algorithm will get stored in the capture flags bitset that is part of the kcap header, so we can effectively compare the algorithm that was used to encrypt the kcap with the one that is specified in the configuration and bail out when they differ.

References

https://golang.org/pkg/crypto/cipher/
https://golang.org/pkg/crypto/rsa/
https://github.com/hashicorp/vault/tree/master/api

@rabbitstack rabbitstack added needs: docs Indicates that the issue needs documentation updates needs: config Indicates the issue requires changes in the config file/flags scope: kcap Anything related to captures labels Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: config Indicates the issue requires changes in the config file/flags needs: docs Indicates that the issue needs documentation updates scope: kcap Anything related to captures
Projects
None yet
Development

No branches or pull requests

1 participant