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

Identify collector's required capabilities #1112

Open
3 tasks
Stringy opened this issue Apr 14, 2023 · 0 comments
Open
3 tasks

Identify collector's required capabilities #1112

Stringy opened this issue Apr 14, 2023 · 0 comments
Assignees

Comments

@Stringy
Copy link
Collaborator

Stringy commented Apr 14, 2023

Following removal of kernel modules, collector will be running with all capabilities (as a privileged container.) To harden the collector process, we should drop all capabilities that we don't require.

  • Identify required capabilities for running the various collector components
    • Kernel driver (eBPF/CORE bpf)
    • conn scraper
    • self-check process
  • Implement a collection-method agnostic way of dropping capabilities once startup has concluded.
  • Identity if any mounts are no longer needed
@JoukoVirtanen JoukoVirtanen self-assigned this Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants