-
Notifications
You must be signed in to change notification settings - Fork 165
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
No fd.net set for UDP event? #2159
Comments
With a closer look at the logs, I now suspect that fd.net work for IPv4, but not for IPv6. |
Perhaps it is related to https://github.com/draios/sysdig/pull/1091and falcosecurity/falco#343 ? The unit test in the latter only test for IPv4, perhaps it could be extended to test IPv6 too? The patch in sysdig only mention IPv4, but I guess the case is equally valid for IPv6. |
I suspect something like this might be a step in the right direction. Unfortunately I do not know how to make the IPv6 .scap file, so I am unable to complete the test.
|
I am using the rule set from falco-incubating_rules.yaml, and try to filter out some of the irrelevant UDP traffic from the 'Unexpected UDP traffic' rule. When I try to filter on fd.net to avoid reports for traffic to and from localhost, this do not work.
This is using the RPM packages for falco version 0.39.1-1.
For reference, the rule I am trying to modify look like this:
I am overriding the expected_udp_traffic. This do not work as expected. I've tried to reduce it to a simple test case, to demonstrate the problem, using this simpler rule to trigger on ping packages not heading for localhost:
When I test with 'ping localhost' with this rule loaded, I get events like this in /var/log/falco.log:
I expected these events to be ignored, as the fd.net content should match the localhost IPv4 and IPv6 content.
Environment
Falco version:
Wed Nov 13 11:09:04 2024: Using deprecated config key 'rules_file' (singular form). Please use new 'rules_files' config key (plural form).
Wed Nov 13 11:09:04 2024: Falco version: 0.39.1 (x86_64)
Wed Nov 13 11:09:04 2024: Falco initialized with configuration files:
Wed Nov 13 11:09:04 2024: /etc/falco/falco.yaml | schema validation: failed for [webserver]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'k8s_audit_endpoint'.
Wed Nov 13 11:09:04 2024: System info: Linux version 6.10.7-100.fc39.x86_64 (mockbuild@bcd4ebc81e1d4849aca2632ad651b39e) (gcc (GCC) 13.3.1 20240522 (Red Hat 13.3.1-1), GNU ld version 2.40-14.fc39) update: delete notices about chisels #1 SMP PREEMPT_DYNAMIC Fri Aug 30 00:07:39 UTC 2024
{"default_driver_version":"7.3.0+driver","driver_api_version":"8.0.0","driver_schema_version":"2.0.0","engine_version":"43","engine_version_semver":"0.43.0","falco_version":"0.39.1","libs_version":"0.18.1","plugin_api_version":"3.7.0"}
System info:
{
"machine": "x86_64",
"nodename": "mytesthost",
"release": "6.10.7-100.fc39.x86_64",
"sysname": "Linux",
"version": "update: delete notices about chisels #1 SMP PREEMPT_DYNAMIC Fri Aug 30 00:07:39 UTC 2024"
}
Cloud provider or hardware configuration:
libvirt VM x86_64/amd64
OS:
Fedora release 39
Kernel:
Linux mytesthost 6.10.7-100.fc39.x86_64 update: delete notices about chisels #1 SMP PREEMPT_DYNAMIC Fri Aug 30 00:07:39 UTC 2024 x86_64 GNU/Linux
Installation method:
RPM
The text was updated successfully, but these errors were encountered: