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

[TRACKING] Re-audit container engines for empty container info values (Initial focus on CRI for Kubernetes) #2708

Open
incertum opened this issue Jul 31, 2023 · 13 comments
Assignees
Milestone

Comments

@incertum
Copy link
Contributor

Describe the bug

While no system and mechanism is perfect, re-audit container engines for empty container info values (Initial focus on CRI for Kubernetes).

The motivation is to get to the bottom of why the container enrichment sometimes fails and subsequently find out if we can improve something still.

@incertum
Copy link
Contributor Author

In addition, I opened a proposal for a formal container engine testing framework falcosecurity/libs#1298.

@poiana
Copy link
Contributor

poiana commented Nov 30, 2023

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
Copy link
Contributor Author

/remove-lifecycle stale

@incertum
Copy link
Contributor Author

Based on improvements made in:

We will be able to better track cases where the container info is missing (leveraging new metrics and output fields). More testing will be performed in January 2024.

@incertum
Copy link
Contributor Author

incertum commented Jan 3, 2024

/assign

@incertum
Copy link
Contributor Author

incertum commented Feb 28, 2024

We just merged falcosecurity/libs#1595 -> Starting with Falco 0.38.0, we will have faster storage of container information into the container cache when running Falco w/ --disable-cri-async. This improvement should significantly impact production environments.

Syscall events are now expected to have significantly fewer missing container fields. However, if a syscall event triggers a rule too close to the container start, before the API call against the container runtime socket has finished (at least 500ms), the Falco alert may still contain missing container image fields.

@incertum
Copy link
Contributor Author

Longer term, we have identified more improvement opportunities; however they will take more time. See falcosecurity/libs#1708 for tracking (milestone TBD).

@incertum
Copy link
Contributor Author

Another note: We have also improved our documentation https://falco.org/docs/reference/rules/supported-fields/#field-class-container and state that under certain circumstances there may be a delay: "In instances of userspace container engine lookup delays, this field may not be available yet".

@poiana
Copy link
Contributor

poiana commented May 28, 2024

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
Copy link
Member

/remove-lifecycle stale

@poiana
Copy link
Contributor

poiana commented Aug 27, 2024

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
Copy link
Member

/remove-lifecycle stale

@poiana
Copy link
Contributor

poiana commented Nov 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants