diff --git a/content/en/blog/falco-0-40.0/images/eventsPerSecond.svg b/content/en/blog/falco-0-40.0/images/eventsPerSecond.svg
new file mode 100644
index 000000000..73b6f9122
--- /dev/null
+++ b/content/en/blog/falco-0-40.0/images/eventsPerSecond.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/content/en/blog/falco-0-40.0/images/googleBenchmark.svg b/content/en/blog/falco-0-40.0/images/googleBenchmark.svg
new file mode 100644
index 000000000..248608fa6
--- /dev/null
+++ b/content/en/blog/falco-0-40.0/images/googleBenchmark.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/content/en/blog/falco-0-40.0/index.md b/content/en/blog/falco-0-40.0/index.md
new file mode 100644
index 000000000..533b1454a
--- /dev/null
+++ b/content/en/blog/falco-0-40.0/index.md
@@ -0,0 +1,159 @@
+---
+title: Introducing Falco 0.40.0
+date: 2025-01-28
+author: Aldo Lacuku, Federico Di Pierro
+slug: falco-0-40-0
+tags: ["Falco","Release"]
+---
+
+Dear Falco Community, today we are happy to announce the release of Falco 0.40.0!
+
+This version brings several new features, performance improvements, and bug fixes that streamline Falco’s detection capabilities.
+During this release cycle, we merged more than 52 PRs on Falco and more than 150 PRs for libs and drivers, version 0.20.0 and version 8.0.0 respectively. Thank you to our maintainers and contributors, as this would not happen without your support and dedication!
+
+To learn all about these changes, read on!
+
+## What’s new? TL;DR
+
+*Key features:*
+
+* [Streamlined Falco docker images](#streamlined-falco-docker-images);
+* Falco static build has been reintroduced for `x86_64` binary using `musl`;
+* New [process filters](#introducing-new-processs-filters) allow to filter events based on process metadata;
+* Added support for `sendmmsg` and `recvmmsg` syscalls parameters;
+* [Plugins suggested output fields](#plugins-suggested-output-fields) are now available in the Falco engine;
+
+{{% pageinfo color="warning" %}}
+This release also comes with [breaking changes](#breaking-changes-and-deprecations) that you should be aware of before upgrading.
+{{% /pageinfo %}}
+
+## Major features and improvements
+
+The 0.40.0 release contains a number of features and UX improvements. Here is a list of some of the key new capabilities.
+
+### Streamlined Falco docker images
+
+In the Falco 0.40.0 release, the Falco team has streamlined the Docker images to improve usability and performance. The new images are designed to be more efficient and easier to use, providing a better experience for users deploying Falco in containerized environments.
+
+Key improvements include:
+
+* Reduced Image Size: The new images are smaller, which reduces the time required to pull and deploy them.
+* Optimized Layers: The layers in the Docker images have been optimized to improve build times and caching efficiency.
+* Enhanced Security: The images have been hardened to enhance security, reducing potential vulnerabilities.
+
+These changes make it easier to deploy and manage Falco in various environments.
+
+### Introducing new process filters
+
+A new set of process filters are made available in this release: `proc.pgid, proc.pgid.name, proc.pgid.exe, proc.pgid.exepath, proc.is_pgid_leader`.
+These filters enable users to filter events based on process metadata, such as the process name, executable path, and arguments. The new filters
+introduce the `pgid` field, which is directly obtained from the kernel. This ID corresponds to the `host pid namespace`, aiding in the creation
+of more reliable rules.
+
+### Plugins suggested output fields
+
+The Falco engine now supports plugins that can suggest output fields. This feature allows plugins to provide additional context and information about an event, enhancing its visibility and understanding.
+The suggested output fields are displayed in the Falco output, giving users valuable insights into the event and its context. By leveraging this feature, Falco makes it easier for users to take advantage of the metadata provided by plugins and improve their security monitoring and incident response capabilities. New output fields are added only if the option is enabled and the plugin supports this new feature.
+
+Keep an eye on the existing plugins to be updated to support the new feature.
+
+## Breaking changes and deprecations ⚠️
+This version comes with breaking changes, mostly in the configuration interface.
+
+### Removed command line options and equivalent configuration options
+
+We removed the already deprecated options `--cri`, `--disable-cri-async`, and is now possible to achieve the same result through the [Falco configuration](https://falco.org/docs/rules/controlling-rules/#via-falco-configuration-or-parameters).
+A new configuration options has been introduced to enable and configure the supported container engines in Falco:
+```yaml
+container_engines:
+ docker:
+ enabled: true
+ cri:
+ enabled: true
+ sockets: ["/run/containerd/containerd.sock", "/run/crio/crio.sock", "/run/k3s/containerd/containerd.sock"]
+ disable_async: false
+ podman:
+ enabled: true
+ lxc:
+ enabled: true
+ libvirt_lxc:
+ enabled: true
+ bpm:
+ enabled: true
+```
+Please keep in mind that the new configuration options are tagged as `incubating` and may change in the future.
+
+You can also use the `-o` command line option:
+* `--cri `: use `-o container_engines.cri.enabled=true, -o container_engines.cri.sockets[]=
+
+The following one shows the average of multiple runs of [Google Benchmark](https://github.com/google/benchmark) framework embedded in libsinsp:
+
+
+
+
+Additionally, artifacts now use [jemalloc](https://jemalloc.net/) as the allocator library. This should help mitigate some `memory fragmentation-related` issues.
+
+Furthermore, Falco debug symbol files are now attached to GitHub releases. Falco is built in `RelWithDebInfo` mode, enabling users to download debug symbols and attach them to their debugging sessions.
+
+
+## Try it out
+
+Interested in trying out the new features? Use the resources below to get started.
+
+* [Container Images](/docs/getting-started/running/#docker)
+ * `falco` ([DockerHub](https://hub.docker.com/r/falcosecurity/falco), [AWS ECR Gallery](https://gallery.ecr.aws/falcosecurity/falco))
+ * `falco-driver-loader` ([DockerHub](https://hub.docker.com/r/falcosecurity/falco-driver-loader), [AWS ECR Gallery](https://gallery.ecr.aws/falcosecurity/falco-driver-loader))
+* [CentOS/Amazon Linux](/docs/getting-started/installation/#centos-rhel)
+* [Debian/Ubuntu](/docs/getting-started/installation/#debian)
+* [openSUSE](/docs/getting-started/installation/#suse)
+* [Linux binary package](/docs/getting-started/installation/#linux-binary)
+
+## What’s next?
+
+Falco is more mature with each release. Following its [graduation](/blog/falco-graduation/) we have published the [roadmap](/docs/roadmap/#road-to-falco-1-0-0) for version 1.0.0 which is guiding us in the next steps. For the next release, you can expect more stability, a new container plugin, refinements to our deployment methods with a k8s operator, and as always new detections and fixes.
+
+## Stay connected
+
+Join us on social media and in our weekly community calls! It’s always great to have new members in the community, and we’re looking forward to hearing your feedback and ideas.
+
+You can find all the most up-to-date information at [https://falco.org/community/](https://falco.org/community/).
+
+
+Additionally, artifacts now use [jemalloc](https://jemalloc.net/) as the allocator library. This should help mitigate some `memory fragmentation-related` issues.
+
+Furthermore, Falco debug symbol files are now attached to GitHub releases. Falco is built in `RelWithDebInfo` mode, enabling users to download debug symbols and attach them to their debugging sessions.
+
+
+## Try it out
+
+Interested in trying out the new features? Use the resources below to get started.
+
+* [Container Images](/docs/getting-started/running/#docker)
+ * `falco` ([DockerHub](https://hub.docker.com/r/falcosecurity/falco), [AWS ECR Gallery](https://gallery.ecr.aws/falcosecurity/falco))
+ * `falco-driver-loader` ([DockerHub](https://hub.docker.com/r/falcosecurity/falco-driver-loader), [AWS ECR Gallery](https://gallery.ecr.aws/falcosecurity/falco-driver-loader))
+* [CentOS/Amazon Linux](/docs/getting-started/installation/#centos-rhel)
+* [Debian/Ubuntu](/docs/getting-started/installation/#debian)
+* [openSUSE](/docs/getting-started/installation/#suse)
+* [Linux binary package](/docs/getting-started/installation/#linux-binary)
+
+## What’s next?
+
+Falco is more mature with each release. Following its [graduation](/blog/falco-graduation/) we have published the [roadmap](/docs/roadmap/#road-to-falco-1-0-0) for version 1.0.0 which is guiding us in the next steps. For the next release, you can expect more stability, a new container plugin, refinements to our deployment methods with a k8s operator, and as always new detections and fixes.
+
+## Stay connected
+
+Join us on social media and in our weekly community calls! It’s always great to have new members in the community, and we’re looking forward to hearing your feedback and ideas.
+
+You can find all the most up-to-date information at [https://falco.org/community/](https://falco.org/community/).