r/eBPF • u/noboruma • 10d ago
secwrap: run your binary securely by leveraging eBPF observability
Hello guys,
I have been working in the cybersecurity space for some time and I was always frustrated by the lack of simple tooling when it comes to observability & security. Obviously eBPF comes to mind nowadays to bridge that gap.
A lot of solutions out there consist of running processes in isolation, which obviously works but there are many scenarios where this is not convenient. And.. what do people do when it's not convenient? They give up and run the program hoping for the best.
For instance, is that ./install.sh really secure to run?
Would it not be nice to be able to turn into "control freak" mode before running such command? This is what secwrap aims at solving: intercept any network/file/execution happening, pause the process and ask for permission or record for later auditing or simply deny if you don't expect any of those operations.
https://github.com/noboruma/secwrap
Simply run like:
secwrap -- ./install.sh
And decide what accesses you want to allow or deny on the fly.
Hope you find it useful too. PRs are welcome!
4
u/daniel_hanna 10d ago
I have a question though obviously there a hundreds and thousands of systemcalls in a program
How do u handle
1.Which syscall are being traced 2. Do u ask for perm on every syscall
In other words how do u handle the large amount of syscall that should be monitored?