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

adding an event of launching network tool in container #104

Merged
merged 5 commits into from
Apr 4, 2024

Conversation

h4l0gen
Copy link
Contributor

@h4l0gen h4l0gen commented Mar 14, 2024

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 is an event try to trigger rule specified here
Which issue(s) this PR fixes:

Fixes #97

Special notes for your reviewer:

@h4l0gen
Copy link
Contributor Author

h4l0gen commented Mar 14, 2024

@leogr as you mentioned here #98 (comment), i tried to make an event for launching network tool(nmap) inside container. please give your feedback regarding this, or any changes?

@h4l0gen h4l0gen changed the title adding an event of launching network tool wip: adding an event of launching network tool Mar 16, 2024
@h4l0gen h4l0gen changed the title wip: adding an event of launching network tool wip: adding an event of launching network tool in container Mar 28, 2024
@h4l0gen
Copy link
Contributor Author

h4l0gen commented Apr 3, 2024

@FedeDP as expected this triggered rule
image
I have used this Dockerfile

`FROM alpine:latest

RUN apk update && apk add --no-cache nmap

ENTRYPOINT ["nmap"]
`

To trigger this rule, I used the command docker run -it nmap-docker. I am not including the argument (port) to reduce noise, as it is causing excessive UDP traffic.

@h4l0gen h4l0gen changed the title wip: adding an event of launching network tool in container adding an event of launching network tool in container Apr 4, 2024
@poiana poiana added the lgtm label Apr 4, 2024
@poiana
Copy link

poiana commented Apr 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: h4l0gen, leogr

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

@poiana
Copy link

poiana commented Apr 4, 2024

LGTM label has been added.

Git tree hash: 53a97ce9762e39f4cabcc09a5f2333ecd0de310e

@poiana poiana added the approved label Apr 4, 2024
@poiana poiana merged commit 46d371f into falcosecurity:main Apr 4, 2024
4 checks passed
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.

Detecting Network tools inside containers
3 participants