Softwr

Cybersecurity · head to head

Cosign vs VMware Carbon Black

Cosign logo

Cosign

Cybersecurity

Signs and verifies container images and artifacts, with or without managing keys

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 Cosign has a free tier, so it costs nothing to try first.
  • Each has a real cost: Cosign keyless signing inherits every weakness of the identity provider behind it. Sigstore’s own threat model states that if an identity provider is compromised, Sigstore will issue certificates to those identities, so a compromised account produces perfectly valid signatures.; 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: Cosign covers Keyless signing, 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 Cosign and VMware Carbon Black actually diverge.

Attributes where Cosign and VMware Carbon Black differ
AttributeCosignVMware Carbon Black
Starting priceFreeOn request
Pricing modelOpen source, no licence feesubscription
Free tierYesNo
PlatformsmacOS, Linux, Windows, DockerDesktop, 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 Cosign

  • Keyless signing
  • Key and KMS signing
  • Registry-native storage
  • In-toto attestations
  • Offline verification
  • Trusted root and signing config

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.

Cosign

  • Signing container images in a build pipeline without managing long-lived private keysnot VMware Carbon Black
  • Attaching a signed bill of materials to a release so consumers can verify its provenancenot VMware Carbon Black
  • Meeting a customer or regulatory requirement for signed artifactsnot VMware Carbon Black
  • Verifying third-party images before they enter an internal registrynot VMware Carbon Black

VMware Carbon Black

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

Where each one falls short

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

Cosign

  • Keyless signing inherits every weakness of the identity provider behind it. Sigstore’s own threat model states that if an identity provider is compromised, Sigstore will issue certificates to those identities, so a compromised account produces perfectly valid signatures.
  • A signature proves who signed, never whether they should have. The documentation is explicit that Sigstore cannot determine authorisation, so every consumer must write and maintain their own identity and issuer policy or verification means nothing.
  • Nothing is enforced without an admission controller. Signing changes what you can prove, not what runs, and the official policy controller has a small maintainer base for a component sitting in a cluster admission path.
  • Upgrades break pipelines. Version 3 changed defaults, version 4 is announced as removing legacy functionality and roughly half the command line flags, and two official client libraries still lacked support for the new log format as of mid 2026.
  • Signatures do not expire. An artifact signed before a maintainer account was compromised and one signed after are indistinguishable unless somebody is actively monitoring the transparency log, and almost nobody is.

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

Cosign

Free
  • CosignFree
    • Apache-2.0
    • Public Sigstore infrastructure free to use
    • No usage limits published

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 Cosign if

  • You need keyless signing.
  • You want to start without paying.
  • You work on macOS, Linux, Windows, Docker.
  • You also want key and kms signing.
Cosign 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 Cosign or VMware Carbon Black better?
Neither clearly leads. Cosign 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, Cosign or VMware Carbon Black?
Cosign has a free tier; the other does not. Paid plans start at Free for Cosign and On request for VMware Carbon Black.
Does Cosign or VMware Carbon Black run on more platforms?
Cosign runs on macOS, Linux, Windows, Docker. VMware Carbon Black runs on Desktop, Api.
Can I use Cosign for free?
Yes. Cosign has a free tier, so you can try it without paying. VMware Carbon Black starts at On request.
What is Cosign best used for?
Cosign is most often used for signing container images in a build pipeline without managing long-lived private keys, attaching a signed bill of materials to a release so consumers can verify its provenance, meeting a customer or regulatory requirement for signed artifacts, verifying third-party images before they enter an internal registry. Of those, signing container images in a build pipeline without managing long-lived private keys and attaching a signed bill of materials to a release so consumers can verify its provenance are not what VMware Carbon Black is typically brought in for.
What can Cosign do that VMware Carbon Black cannot?
Cosign covers Keyless signing, Key and KMS signing, Registry-native storage, In-toto attestations. VMware Carbon Black covers Endpoint Standard, Enterprise EDR, Audit and Remediation, Single sensor.

Answered from the vendors’ own pages

Cosign: Does Cosign tell me if an image is vulnerable?

No. It has no vulnerability knowledge whatsoever. It can carry an SBOM as a signed attestation but never reads it. Pair it with a scanner.

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.

Cosign: Is signing alone enough?

No. Verification is a command somebody runs. Without an admission controller enforcing it, an unsigned image still runs.

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.

Cosign: What does a bare cosign verify actually prove?

Very little. Without a pinned certificate identity and OIDC issuer, it accepts a valid signature from any identity at all.

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.

Cosign: What is the risk of keyless signing?

Your OIDC provider becomes the root of trust. Compromise of that account yields genuine, verifiable signatures, so account security is the control that matters.

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.

Cosign: Should we expect breaking changes?

Yes. Version 4 is announced to remove roughly half the flags, and a post-quantum migration is named as a further breaking change after that.

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 Cosign

More on VMware Carbon Black

Keep looking

Other head to heads