Skip to content

Commit

Permalink
+ Add a user_known_write_monitored_dir_conditions macro to allow cust…
Browse files Browse the repository at this point in the history
…om conditions in the "Write below monitored dir" rule (#566)

falco-CLA-1.0-contributing-entity: Coveo Solutions Inc.
falco-CLA-1.0-signed-off-by: Jean-Philippe Lachance <jplachance@coveo.com>
  • Loading branch information
JPLachance authored and mstemm committed Mar 28, 2019
1 parent bdda640 commit 2fd90bf
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions rules/falco_rules.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -763,6 +763,15 @@
or user_ssh_directory)
and not mkinitramfs_writing_boot
# Add conditions to this macro (probably in a separate file,
# overwriting this macro) to allow for specific combinations of
# programs writing below monitored directories.
#
# Its default value is an expression that always is false, which
# becomes true when the "not ..." in the rule is applied.
- macro: user_known_write_monitored_dir_conditions
condition: (never_true)

- rule: Write below monitored dir
desc: an attempt to write to any file below a set of binary directories
condition: >
Expand All @@ -774,6 +783,7 @@
and not python_running_ms_oms
and not google_accounts_daemon_writing_ssh
and not cloud_init_writing_ssh
and not user_known_write_monitored_dir_conditions
output: >
File below a monitored directory opened for writing (user=%user.name
command=%proc.cmdline file=%fd.name parent=%proc.pname pcmdline=%proc.pcmdline gparent=%proc.aname[2])
Expand Down

0 comments on commit 2fd90bf

Please sign in to comment.