Softwr

Cybersecurity · head to head

Falco vs VMware Carbon Black

Falco logo

Falco

Cybersecurity

CNCF-graduated runtime threat detection for Linux and Kubernetes using eBPF

From
Free
Rated
-
Full reviewWebsite
V

VMware Carbon Black

Cybersecurity

Cloud-delivered endpoint protection and EDR, now owned by Broadcom and positioned alongside Symantec.

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only Falco has a free tier, so it costs nothing to try first.
  • Each has a real cost: Falco falco detects and alerts but does not block; stopping an attack requires wiring up Falco Talon or your own response tooling, so out of the box a confirmed detection still means a human intervening after the fact.; VMware Carbon Black broadcom's enterprise model concentrates direct sales and support on its largest accounts and moves everyone else to resellers, so a mid-size customer can lose named support contacts and face a substantially repriced renewal with limited notice.
  • They diverge on capability: Falco covers eBPF kernel instrumentation, VMware Carbon Black covers Endpoint Standard.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Falco and VMware Carbon Black actually diverge.

Attributes where Falco and VMware Carbon Black differ
AttributeFalcoVMware Carbon Black
Starting priceFreeOn request
Pricing modelOpen source, no licence feesubscription
Free tierYesNo
PlatformsLinux, Kubernetes, Self-hostedDesktop, Api
FoundedUnknown2002

Identical on both: user rating (Not yet rated), category (Cybersecurity).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Falco

  • eBPF kernel instrumentation
  • System call rules engine
  • Container and Kubernetes context
  • Default rule set
  • Falcosidekick
  • Falco Talon
  • Plugins framework
  • DaemonSet deployment

Only in VMware Carbon Black

  • Endpoint Standard
  • Enterprise EDR
  • Audit and Remediation
  • Single sensor
  • Live Response
  • Workload protection
  • Container security
  • Watchlists and feeds

What people use each for

The jobs each tool is most often brought in to do.

Falco

  • A platform team that needs to know when a shell is opened inside a production container, which image scanning cannot detect because it happens at runtimenot VMware Carbon Black
  • A regulated business required to evidence host and container intrusion detection on Kubernetes nodes for an auditnot VMware Carbon Black
  • A security team wanting a vendor-neutral detection layer whose rules they can read and modify rather than a black-box agentnot VMware Carbon Black
  • A cluster where a compromised dependency might write to sensitive paths or open unexpected outbound connections, and only kernel-level visibility will catch itnot VMware Carbon Black

VMware Carbon Black

  • A SOC that wants unfiltered endpoint telemetry to hunt over rather than only vendor-generated alertsnot Falco
  • A vSphere estate that wants workload protection deployed through the hypervisor instead of installing an agent in every guestnot Falco
  • Replacing signature antivirus after an incident where the incumbent product had no record of what the attacker didnot Falco
  • An organisation already inside a Broadcom or Symantec enterprise agreement that can consolidate endpoint onto an existing contractnot Falco

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Falco

  • Falco detects and alerts but does not block; stopping an attack requires wiring up Falco Talon or your own response tooling, so out of the box a confirmed detection still means a human intervening after the fact.
  • The default rule set is noisy in real clusters and generates a large volume of benign matches from normal operational activity; without weeks of tuning, alert fatigue sets in and the team stops reading the feed, which is the usual failure mode.
  • There is no storage, console, search or case management in the project, so a working detection capability means also running Falcosidekick, an event store, a dashboard and alert routing, all of which you build, host and maintain.
  • The modern eBPF driver requires kernel 5.8 or later; older hosts fall back to the legacy probe or the kernel module, which brings driver-building against kernel headers and the operational fragility that comes with it on every kernel upgrade.
  • Per-node syscall instrumentation carries measurable CPU overhead on busy hosts, and the cost scales with syscall volume rather than with cluster size, so the noisiest and most performance-sensitive workloads are exactly the ones that feel it most.

VMware Carbon Black

  • Broadcom's enterprise model concentrates direct sales and support on its largest accounts and moves everyone else to resellers, so a mid-size customer can lose named support contacts and face a substantially repriced renewal with limited notice.
  • Continuous EDR recording is retained for a defined window and longer retention is a paid tier, so the investigation you most need is often the one whose telemetry has already aged out, and that is discovered during the incident rather than before it.
  • The product assumes an operator: watchlists, policy tuning and alert triage are ongoing work, and organisations without a dedicated analyst or an MDR contract typically leave policies in monitor mode and pay for telemetry that is never reviewed.
  • The sensor operates in the same kernel and file-filter territory as other endpoint agents, so running it alongside an incumbent antivirus, DLP or backup agent commonly produces performance complaints and requires maintained exclusion lists on both sides.
  • Linux sensor support is tied to specific distribution and kernel versions, so a routine operating system upgrade can leave hosts without a supported sensor until a matching build ships, and anything outside the supported list gets no coverage at all.

Pricing, plan by plan

Falco

Free
  • Falco (open source)Free
    • Apache 2.0 licence, CNCF graduated project
    • eBPF and kernel module drivers
    • Full rules engine and default rule set

VMware Carbon Black

On request
  • CB Endpoint StandardFree
    • NGAV
    • Behavioral EDR
    • Device control
  • CB Endpoint AdvancedFree
    • All Standard features
    • Threat hunting
    • Audit and remediation
  • CB Endpoint EnterpriseFree
    • All Advanced features
    • Advanced threat hunting
    • Live response

Which should you pick?

Choose Falco if

  • You need ebpf kernel instrumentation.
  • You want to start without paying.
  • You work on Linux, Kubernetes, Self-hosted.
  • You also want system call rules engine.
Falco review

Choose VMware Carbon Black if

  • You need endpoint standard.
  • You work on Desktop, Api.
  • You also want enterprise edr.
VMware Carbon Black review

Questions people ask

Is Falco or VMware Carbon Black better?
Neither clearly leads. Falco starts at Free and VMware Carbon Black at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Falco or VMware Carbon Black?
Falco has a free tier; the other does not. Paid plans start at Free for Falco and On request for VMware Carbon Black.
Does Falco or VMware Carbon Black run on more platforms?
Falco runs on Linux, Kubernetes, Self-hosted. VMware Carbon Black runs on Desktop, Api.
Can I use Falco for free?
Yes. Falco has a free tier, so you can try it without paying. VMware Carbon Black starts at On request.
What is Falco best used for?
Falco is most often used for a platform team that needs to know when a shell is opened inside a production container, which image scanning cannot detect because it happens at runtime, a regulated business required to evidence host and container intrusion detection on kubernetes nodes for an audit, a security team wanting a vendor-neutral detection layer whose rules they can read and modify rather than a black-box agent, a cluster where a compromised dependency might write to sensitive paths or open unexpected outbound connections, and only kernel-level visibility will catch it. Of those, a platform team that needs to know when a shell is opened inside a production container, which image scanning cannot detect because it happens at runtime and a regulated business required to evidence host and container intrusion detection on kubernetes nodes for an audit are not what VMware Carbon Black is typically brought in for.
What can Falco do that VMware Carbon Black cannot?
Falco covers eBPF kernel instrumentation, System call rules engine, Container and Kubernetes context, Default rule set. VMware Carbon Black covers Endpoint Standard, Enterprise EDR, Audit and Remediation, Single sensor.

Answered from the vendors’ own pages

Falco: Does Falco block attacks?

No. It detects and emits events. Response requires Falco Talon or your own automation on top.

VMware Carbon Black: Who owns Carbon Black now?

Broadcom. It acquired VMware in November 2023, and Carbon Black now sits in Broadcom's enterprise security business alongside Symantec. VMware branding is being phased out.

Falco: Is Falco owned by Sysdig?

Sysdig created and open sourced it, but it graduated within the CNCF in February 2024, so governance sits with the foundation rather than the vendor.

VMware Carbon Black: Why do the docs use names I do not recognise?

The product has been renamed repeatedly. CB Defense is now Endpoint Standard, CB ThreatHunter is Enterprise EDR and CB LiveOps is Audit and Remediation. Older community answers and runbooks still use the previous names.

Falco: What does it cost?

The project is Apache 2.0 with no licence fee. The cost is the storage, routing, tuning and staff time needed to make its output useful.

VMware Carbon Black: Does it replace my existing antivirus?

Yes on supported Windows, macOS and Linux versions, and running it alongside another antivirus is not recommended because the two agents contend for the same hooks. Check your compliance requirements, as some auditors still ask for a named antivirus product.

Falco: What kernel version do I need?

Kernel 5.8 or later for the default modern eBPF driver. Older hosts need the legacy eBPF probe or the kernel module.

VMware Carbon Black: Do I need a full-time analyst to run it?

To get value from Enterprise EDR, effectively yes. The prevention tier can run with part-time attention, but the hunting and recording capability is only worth its cost if somebody is querying it, which is why many customers buy it through an MDR provider.

VMware Carbon Black: How is it licensed?

Per endpoint, per year, with the capability tier determining the rate and workload and container protection priced separately. Extended EDR data retention is an additional line item.

Share

Related pages

More on Falco

More on VMware Carbon Black

Keep looking

Other head to heads