Changing the default set of events #2611
Replies: 3 comments 1 reply
-
personally I would try to keep the default to just the minimum valuable events, also keeping #1310 in mind and also assuming this doesn't affect signatures. just my opinion: containers - I would keep just start (not sure what existing is) WDYT? |
Beta Was this translation helpful? Give feedback.
-
main merged (#2636, #2645) with these events as default:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
We got feedback from some users saying that today's default set is too noisy, and a suggestion for a new default set that we can use. I would like to get any other feedback about this new default set of events:
containers
container_create
container_remove
files
creat
chmod
fchmod
fchmodat
chown
fchown
lchown
fchownat
memfd_create
security_inode_unlink
security_sb_mount
network
security_socket_bind
security_socket_connect
security_socket_accept
code injection
process_vm_writev
process_vm_readv
ptrace
execution
sched_process_exec
process privileges
setuid
setgid
setpgid
setsid
setreuid
setregid
setresuid
setresgid
setfsuid
setfsgid
setns
kernel module
init_module
finit_module
In the future, we will add more user-friendly events to this set as described here: #1310
In addition to that, after we will complete the new "everything is an event" experience (#2355) we will also add some (or all?) of tracee rules to this default list
Beta Was this translation helpful? Give feedback.
All reactions