wip: adding new event of copying content of sensitive files

[h4l0gen]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it: This PR is adding an event which will try to copy content of sensitive files to another destination. Which issue(s) this PR fixes:

Fixes #96

Special notes for your reviewer:

[poiana]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: h4l0gen Once this PR has been reviewed and has the lgtm label, please assign fededp for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[poiana]

Welcome @h4l0gen! It looks like this is your first PR to falcosecurity/event-generator 🎉

[h4l0gen]

Hey maintainers, this is my first PR for the event-generator. I've created an event for the first time, so please review the PR and provide me with your valuable feedback. Thank you!

[h4l0gen]

/kind feature /area events

[h4l0gen]

/area events

[h4l0gen]

@leogr , oh i wasn't aware of this

Each action must match a specific existing rule and have the same name
(I apologize because I know this convention is not documented).

then this event doesn't belong to any specific rule. I just created it as per security concern.

[h4l0gen]

@leogr i came across this rule Launch Remote file copy tools in container in https://falco.org/docs/reference/rules/default-rules/ this rule has also procedure of copying content of file. If you like i can convert this PR to Launch Remote file copy tools in container rule.

[h4l0gen]

@leogr can we close this, as not related to rule.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale