Zuzanna Konopek [4:19 PM] Hi, has anyone had problems with file monitoring? 1. In version 5.4.0, there was a File Access Rules tab on group nodes, but in 5.4.8 it is missing. Is there a value to enable it now in helm deployment (I coudnt find it in https://github.com/neuvector/neuvector-helm/tree/master/charts/core)? 2. Also, on a container group in monitoring mode (with and without Zero-drift), NeuVector isn't detecting certain changes: a. modification of file

/etc/hosts

and

/etc/resolv.conf

is detected and reported - ok b. creation, permission changes, or content modification of

/bin/kot

(and all of the default monitoring locations) are not reported – but should be. c. custom rules for

/home/ubuntu/kot

are also not reported. I set appropriate runtimePath - for helm values.yaml file, I added label "pod-security.kubernetes.io/enforce=privileged" to namespace, in enforcer section I added pod annotation container.apparmor.security.beta.kubernetes.io/neuvector-enforcer-pod: unconfined - for helm values.yaml file my nodes utilize appparmor but in their logs there is no DENY entry also unknown process execution is working fine Im running this on openstack, kubernetes 1.34.3 and Ubuntu 22.04.5 LTS and all of the Does anyone have an idea what more could be done?