-
Notifications
You must be signed in to change notification settings - Fork 72
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
Test: Verify if secrets are encrypted #1971
base: main
Are you sure you want to change the base?
Conversation
Please create WIP or DRAFT PRs as DRAFT's when creating, this will prevent any accidental merges as "Draft" status will grey out the "merge" button until they're actually ready for review and merging. |
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.
lgtm
@HashNuke I think this one is ready for test |
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.
spec test(s) missing
Description
By default in kubernetes system, encrypting of data inside object like secret is not enabled, so data in etcd are available for potential attacker.
Encrypting of secret is possible in newer versions of kubernetes. When this configuration is done, all newly created secrets has encrypted data in etcd key-value store.
We can use kubescape test to cover this area.
Issues:
Refs: #1970
How has this been tested:
Types of changes:
Checklist:
Documentation
Code Review
Issue