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

rule(macro user_known_set_setuid_or_setgid_bit_conditions): create macro #1213

Merged
merged 1 commit into from
May 26, 2020
Merged

rule(macro user_known_set_setuid_or_setgid_bit_conditions): create macro #1213

merged 1 commit into from
May 26, 2020

Conversation

marier-nico
Copy link
Contributor

What type of PR is this?

/kind feature
/kind rule-update

Any specific area of the project related to this PR?

/area rules

What this PR does / why we need it:

This macro will be useful because it will make it possible to filter out
events with a higher degree of granularity than is currently possible
for the Set Setuid or Setgid bit rule.

For example, if some application is expected to set the setuid or the
setgid bit under a specific condition, like if it's started with a
specific command, then the user_known_chmod_applications list is not
enough because we don't want to filter out all events by this
application, only specific ones. This macro allows that.

A concrete example of this is when using docker-in-docker : the dockerd process is triggering the Set Setuid or Setgid bit rule and every time it does, proc.cmdline is the same. This is expected in our case, but we don't want to just ignore all events from dockerd within this rule, just this specific one with this specific proc.cmdline value.

Which issue(s) this PR fixes:

None

Does this PR introduce a user-facing change?:

rule(macro user_known_set_setuid_or_setgid_bit_conditions): create macro

This macro will be useful because it will make it possible to filter out
events with a higher degree of granularity than is currently possible
for the `Set Setuid or Setgid bit` rule.

For example, if some application is expected to set the setuid or the
setgid bit under a specific condition, like if it's started with a
specific command, then the `user_known_chmod_applications` list is not
enough because we don't want to filter out _all_ events by this
application, only specific ones. This macro allows that.

Signed-off-by: Nicolas Marier <nmarier@coveo.com>
@Kaizhe
Copy link
Contributor

Kaizhe commented May 19, 2020

Thanks!
/lgtm

@poiana
Copy link

poiana commented May 19, 2020

LGTM label has been added.

Git tree hash: 856dc2ad6d950e14a0ec355cc43ea87d29badaed

1 similar comment
@poiana
Copy link

poiana commented May 19, 2020

LGTM label has been added.

Git tree hash: 856dc2ad6d950e14a0ec355cc43ea87d29badaed

@fntlnz
Copy link
Contributor

fntlnz commented May 25, 2020

reopening to let the CI do its thing

@fntlnz fntlnz closed this May 25, 2020
@fntlnz fntlnz reopened this May 25, 2020
Copy link
Member

@leodido leodido left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@poiana poiana merged commit 81e29c5 into falcosecurity:master May 26, 2020
@poiana
Copy link

poiana commented May 26, 2020

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Kaizhe, leodido

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Successfully merging this pull request may close these issues.

None yet

6 participants