Debugfs Launched in Privileged Container

Description

Detect file system debugger debugfs launched inside a privileged container which might lead to container escape. This rule has a more narrow scope.

Query · falco

spawned_process and container and container.privileged=true and proc.name=debugfs

Rule dependencies

Depends on

  • composes · Falco macro container
    A shared condition, not a detection — not indexed on this site.
  • composes · Falco macro spawned_process
    A shared condition, not a detection — not indexed on this site.

Analyst notes

Debugfs launched started in a privileged container | evt_type=%evt.type user=%user.name user_uid=%user.uid user_loginuid=%user.loginuid process=%proc.name proc_exepath=%proc.exepath parent=%proc.pname command=%proc.cmdline terminal=%proc.tty exe_flags=%evt.arg.flags

Raw source Debugfs Launched in Privileged Container · Falco YAML
Esc
Published by falcosecurity/rules ↗, licensed under Apache 2.0 ↗. Reproduced here unmodified. 
rule: Debugfs Launched in Privileged Container
desc: 'Detect file system debugger debugfs launched inside a privileged container
  which might lead to container escape. This rule has a more narrow scope.

  '
condition: 'spawned_process and container and container.privileged=true and proc.name=debugfs

  '
output: Debugfs launched started in a privileged container | evt_type=%evt.type user=%user.name
  user_uid=%user.uid user_loginuid=%user.loginuid process=%proc.name proc_exepath=%proc.exepath
  parent=%proc.pname command=%proc.cmdline terminal=%proc.tty exe_flags=%evt.arg.flags
priority: WARNING
tags:
- maturity_stable
- container
- cis
- process
- mitre_privilege_escalation
- T1611

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.