Closed LucaGuerra closed 3 months ago
Comparing 6a0922b6879c309f75bc82e644f2e9918310f7cc
with latest tag falco-incubating-rules-4.0.0
Patch changes:
System procs network activity
changed its output fieldsUnexpected UDP Traffic
changed its output fieldsContact EC2 Instance Metadata Service From Container
changed its output fieldsContact cloud metadata service from container
changed its output fieldsNetwork Connection outside Local Subnet
changed its output fieldsLGTM label has been added.
/hold
@LucaGuerra mind also updating the description?
Comparing c2e6007b0de8268dda3cb4f3da33f858ca774568
with latest tag falco-incubating-rules-4.0.0
Patch changes:
System procs network activity
changed its output fieldsUnexpected UDP Traffic
changed its output fieldsContact EC2 Instance Metadata Service From Container
changed its output fieldsContact cloud metadata service from container
changed its output fieldsNetwork Connection outside Local Subnet
changed its output fieldsLGTM label has been added.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, loresuso, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Comparing 42bf4c83e67e7565174e6fd76d33ac82b16c4018
with latest tag falco-incubating-rules-4.0.0
Patch changes:
System procs network activity
changed its output fieldsUnexpected UDP Traffic
changed its output fieldsContact EC2 Instance Metadata Service From Container
changed its output fieldsContact cloud metadata service from container
changed its output fieldsNetwork Connection outside Local Subnet
changed its output fields
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area rules
Proposed rule maturity level
/area maturity-incubating
What this PR does / why we need it:
In https://github.com/falcosecurity/rules/pull/208 we changed the type of the
cmd
argument to a flag type because of changes in https://github.com/falcosecurity/libs/pull/1545 , however the libs PR was only modifying the exit event, while this rule refers to the enter event which is still an INT64, thus we still need to use the value5
for this event. I noticed this during a conversation with @incertum .Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: