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

Recategorization of CVE for Network Exposure #9

Open
shreyas-s-rao opened this issue Jul 10, 2023 · 0 comments
Open

Recategorization of CVE for Network Exposure #9

shreyas-s-rao opened this issue Jul 10, 2023 · 0 comments
Labels
area/compliance Compliance related area/security Security related kind/task General task lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@shreyas-s-rao
Copy link
Contributor

What would you like to be added:
Recategorization of CVE for Network Exposure.

Why is this needed:
Currently CVE network_exposure is set to private since the etcd-wrapper container does not interact with any endpoints outside of the cluster, and does not expose any external services as well. It is only contacted by etcd-backup-restore, kube-apiserver and prometheus. There is ongoing discussion to move etcd initialization from backup-restore container to etcd container, since initialization is is a DB-specific operation, and finds a better place within etcd container. Once this is done, the CVE label network_exposure needs to be re-looked at, since DB validation also checks the backup bucket for revision sanity check against the DB revision. Since this involves the etcd container contacting the object storage on a public hyperscaler, the value for label network_exposure will have to be changed to protected.

@shreyas-s-rao shreyas-s-rao added area/compliance Compliance related area/security Security related kind/task General task labels Jul 10, 2023
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Mar 18, 2024
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/compliance Compliance related area/security Security related kind/task General task lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

2 participants