feat(docs): Removing Coveo Logo

[ggstalderCoveo]

What type of PR is this?

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

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind event

Any specific area of the project related to this PR?

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

/area blog

/area documentation

/area community

What this PR does / why we need it: Removing the Coveo logo as Coveo no longer use Falco

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

[poiana]

Welcome @ggstalderCoveo! It looks like this is your first PR to falcosecurity/falco-website 🎉

[Issif]

Hi,

Thank you for this update. Out of curiosity, do you have any complaint about the project which explains you stopped using it? All feedback are really valuable for us.

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggstalderCoveo, Issif

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:

• OWNERS [Issif]

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

[poiana]

LGTM label has been added.

Git tree hash: f6d5eff0a88952de8e8087719c760ee7f9903250

[JPLachance]

Hi,

Thank you for this update. Out of curiosity, do you have any complaint about the project which explains you stopped using it? All feedback are really valuable for us.

Hello Thomas,

It’s been a while since we worked together on Falco, and I fondly remember our fun explorations, especially when we first dived into Falco dashboards in Kibana!

At Coveo, we decided to move away from Falco in 2020 and switched to a provider that leverages behavioral analytics, where the rules aren’t static. The primary reason for this was the time investment required to fine-tune the rules and reduce false positives, which became quite time-consuming for my team. We also encountered some performance-related challenges, as detailed in this GitHub issue.

That being said, we haven’t ruled out the possibility of revisiting Falco in the future. For businesses seeking a robust, cost-effective security solution, I’ll definitely continue recommending Falco.

Thanks again for the work you and the team are doing, and I look forward to seeing Falco evolve!

Best regards,
Jean-Philippe

[Issif]

Hi,

Thanks a lot for these precious details.

FYI, a lot changed since 2020 to help with the perfs issues you faced:

• we introduced a modern eBPF probe
• selection of the syscalls to capture, only those relevant with the current rules are collected, not all like before
• possibility to fine tune the different buffers
• out of the box prometheus metrics with a Grafana dashboard to track the drops with their reasons
• a k8s metadata collector + a plugin to get the k8s metadata in a resilient and performant way (no more n/a for k8s.* fields)
• a lot of improvements in the codebase + deps

Regards,