Refactor and simplify legacy `syscall_event_drops` - Githubissues

falcosecurity / falco

Cloud Native Runtime Security

https://falco.org

Apache License 2.0

7.25k stars 895 forks source link

Refactor and simplify legacy `syscall_event_drops` #3050

Open incertum opened 7 months ago

incertum commented 7 months ago

Refactor and simplify legacy syscall_event_drops.

Previous discussion: https://github.com/falcosecurity/falco/issues/2910

Needs to address CVE-2019-8339 even better. @leogr to provide more details.

incertum commented 7 months ago

/milestone 0.38.0

/assign @leogr

incertum commented 7 months ago

Initial ideas:

Add an explicit enabled key to allow for easier opt out
By default enabled for all logging levels not just priority level debug
Only report global drop stats and instead point to metrics for detailed and continuous monitoring
Discuss alert volume implications -> opportunity to re-design and adopt a new approach

poiana commented 4 months ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

Andreagit97 commented 4 months ago

/remove-lifecycle stale

LucaGuerra commented 3 months ago

Is this addressed by the latest changes in Falco or shall we move it to the next milestone?

/milestone 0.39.0

incertum commented 3 months ago

We haven't gotten to it, so 0.39.0 is perfect. Thanks!

poiana commented 2 weeks ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

incertum commented 2 weeks ago

/remove-lifecycle stale

next milestone