-
Notifications
You must be signed in to change notification settings - Fork 228
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
blog post falco-talon 0.3.0 #1448
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM, just a few minor reccomendation (see below)!
tags: ["Talon", "Release"] | ||
--- | ||
|
||
Today we announce the release of **Falco Talon 0.3.0** 🦅! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Today we announce the release of **Falco Talon 0.3.0** 🦅! | |
Today, we announce the release of **Falco Talon 0.3.0** 🦅! |
The key feature this release brings is the new actionner `kubernetes:sysdig`. For whom are not familiar with [sysdig](https://github.com/draios/sysdig), it's a CLI tool which allows to capture and record the syscalls, like `tcpdump` does for the network packets. Old brother of Falco, they share the same libs and filters. | ||
|
||
With this new integration, when a suspicious event occurs in a pod, Talon will trigger a capture then export the created artifact to AWS S3 or Minio. You can configure the `duration` and the `amount of bytes` captured for each syscall. More settings are available, check out the [docs](https://docs.falco-talon.org/docs/actionners/list/#kubernetessysdig). | ||
|
||
See this example rule: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The key feature this release brings is the new actionner `kubernetes:sysdig`. For whom are not familiar with [sysdig](https://github.com/draios/sysdig), it's a CLI tool which allows to capture and record the syscalls, like `tcpdump` does for the network packets. Old brother of Falco, they share the same libs and filters. | |
With this new integration, when a suspicious event occurs in a pod, Talon will trigger a capture then export the created artifact to AWS S3 or Minio. You can configure the `duration` and the `amount of bytes` captured for each syscall. More settings are available, check out the [docs](https://docs.falco-talon.org/docs/actionners/list/#kubernetessysdig). | |
See this example rule: | |
The key feature this release brings is the new actionner `kubernetes:sysdig`. For those who are not familiar with [sysdig](https://github.com/draios/sysdig), it's a CLI tool that allows to capture and record the syscalls, like `tcpdump` does for the network packets. Old brother of Falco, they share the same libs and filters. | |
With this new integration, when a suspicious event occurs in a pod, Talon triggers a capture and then exports the created artifact to AWS S3 or Minio. You can configure the `duration` and the `amount of bytes` captured for each syscall. Check out the [docs](https://docs.falco-talon.org/docs/actionners/list/#kubernetessysdig) to discover more settings. | |
See this example rule: |
|
||
## Let's meet 🤝 | ||
|
||
We meet every Wednesday in our [community calls](https://github.com/falcosecurity/community), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We meet every Wednesday in our [community calls](https://github.com/falcosecurity/community), | |
We meet every two weeks on Wednesday in our [community calls](https://github.com/falcosecurity/community), |
|
||
Thanks to all the amazing contributors! | ||
|
||
Enjoy 😎, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the comma a left-over? 🤔
Signed-off-by: Thomas Labarussias <[email protected]>
8d3bc4b
to
ebbeb68
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Issif, 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 |
LGTM label has been added. Git tree hash: dc82aad595cc4180e765c17b57124d127baf928b
|
What type of PR is this?
/kind content
Any specific area of the project related to this PR?
/area blog
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: