Softwr

Cybersecurity · head to head

Qualys VMDR vs Sigstore

Qualys VMDR logo

Qualys VMDR

Cybersecurity

Cloud-delivered vulnerability management licensed per asset, using scanner appliances and a lightweight agent.

From
$3/month
Rated
-
Full reviewWebsite
Sigstore logo

Sigstore

Cybersecurity

Free public signing and transparency infrastructure for open source artifacts

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Sigstore has a free tier, so it costs nothing to try first.
  • Each has a real cost: Qualys VMDR licensing is per asset and each capability is its own subscription, so patch management, endpoint detection, web application scanning, container security and policy compliance are separate line items, and the platform demonstrated in a proof of concept is rarely the platform in the quote.; Sigstore the security model depends on somebody watching the log. The documentation states that compromise of an identity provider or of Fulcio itself is detectable only if third parties monitor the transparency log, the monitoring tool is a community-tier rather than core project, and almost no consumer runs one.
  • They diverge on capability: Qualys VMDR covers Cloud Agent, Sigstore covers Fulcio.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Qualys VMDR and Sigstore actually diverge.

Attributes where Qualys VMDR and Sigstore differ
AttributeQualys VMDRSigstore
Starting price$3/monthFree
Pricing modelsubscriptionOpen source, public instance free to use
Free tierNoYes
PlatformsWeb, Cloud, ApiWeb, Linux, macOS, Windows, Self-hosted
Founded1999Unknown

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 Qualys VMDR

  • Cloud Agent
  • Scanner appliances
  • Authenticated scanning
  • TruRisk scoring
  • Asset inventory
  • Patch Management
  • Cloud connectors
  • Container sensor

Only in Sigstore

  • Fulcio
  • Rekor
  • Keyless signing
  • Multi-language clients
  • Timestamp authority
  • Neutral governance

What people use each for

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

Qualys VMDR

  • A hybrid workforce where scheduled network scans miss most laptops and continuous agent-based assessment is the only way to get real coveragenot Sigstore
  • PCI DSS external scanning where an approved scanning vendor report is a contractual requirementnot Sigstore
  • An estate spanning datacentre, multiple public clouds and endpoints that needs one vulnerability view rather than three toolsnot Sigstore
  • Organisations replacing a manual patch-verification process with agent-reported evidence that a fix actually landednot Sigstore

Sigstore

  • Open source projects signing releases without running a certificate authoritynot Qualys VMDR
  • Organisations meeting a signed-artifact requirement without buying a signing productnot Qualys VMDR
  • Publishing provenance that a consumer can verify independently of younot Qualys VMDR
  • Self-hosting the same components where a public log is unacceptablenot Qualys VMDR

Where each one falls short

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

Qualys VMDR

  • Licensing is per asset and each capability is its own subscription, so patch management, endpoint detection, web application scanning, container security and policy compliance are separate line items, and the platform demonstrated in a proof of concept is rarely the platform in the quote.
  • Ephemeral cloud instances consume asset entitlement until they age out of inventory, so an autoscaling group that creates and destroys hosts hourly can burn licence capacity on machines that existed for minutes, and controlling that means tuning purge policies rather than tuning the cloud.
  • Authenticated scanning produces materially better results than unauthenticated, but it requires storing and rotating privileged credentials for every target platform, which is a security project in its own right, and teams that skip it receive reports full of unconfirmed potential findings that nobody trusts.
  • The console is a set of modules with separate interfaces, search syntaxes and report engines, so an analyst moving between vulnerability management, policy compliance and web application scanning learns each one, and cross-module reporting usually ends in a spreadsheet or a script against the API.
  • The tool surfaces findings far faster than any organisation can remediate them, and it does not solve the ownership problem: without an agreed prioritisation policy and a named owner in IT operations, a first scan producing tens of thousands of findings becomes a dashboard that everyone learns to ignore.

Sigstore

  • The security model depends on somebody watching the log. The documentation states that compromise of an identity provider or of Fulcio itself is detectable only if third parties monitor the transparency log, the monitoring tool is a community-tier rather than core project, and almost no consumer runs one.
  • It is a 99.5 percent objective with no service level agreement, which permits several hours of downtime a month and offers no remedy. A pipeline that signs on every build has taken a hard dependency on a free service with no contract behind it.
  • Log scale is a live engineering problem rather than a theoretical one. The active shard holds billions of entries, the log has already been sharded twice, and sharding version 1 requires stopping traffic, which is why a replacement was built.
  • Ten-minute certificates make trust depend on log availability. Verifying an older signature relies on the log entry proving it was made inside that window, so a lost or unreachable entry can render a valid artifact unverifiable.
  • Migration debt is substantial and ongoing. Version 2 of the log is generally available but not the public default, the signing client has an announced breaking release ahead, some official clients lag the new log format, and a post-quantum migration is named as the next break after that.

Pricing, plan by plan

Qualys VMDR

$3/month
  • VMDR$3/month
    • Per asset
    • Vulnerability scanning
    • Detection
  • VMDR+$5/month
    • All VMDR features
    • Advanced analytics
    • Cloud integration
  • VMDR Complete$7/month
    • All VMDR+ features
    • Threat intel
    • Response automation

Sigstore

Free
  • Public good instanceFree
    • Free to everyone with no contract
    • 99.5 percent availability objective, not an agreement
    • 100KB cap per attestation upload
  • Self-hostedFree
    • Apache-2.0
    • Run your own Fulcio and Rekor
    • Rekor v2 available for self-hosters

Which should you pick?

Choose Qualys VMDR if

  • You need cloud agent.
  • You work on Web, Cloud, Api.
  • You also want scanner appliances.
Qualys VMDR review

Choose Sigstore if

  • You need fulcio.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows, Self-hosted.
  • You also want rekor.
Sigstore review

Questions people ask

Is Qualys VMDR or Sigstore better?
Neither clearly leads. Qualys VMDR starts at $3/month and Sigstore at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Qualys VMDR or Sigstore?
Sigstore has a free tier; the other does not. Paid plans start at $3/month for Qualys VMDR and Free for Sigstore.
Does Qualys VMDR or Sigstore run on more platforms?
Qualys VMDR runs on Web, Cloud, Api. Sigstore runs on Web, Linux, macOS, Windows, Self-hosted.
Can I use Sigstore for free?
Yes. Sigstore has a free tier, so you can try it without paying. Qualys VMDR starts at $3/month.
What is Qualys VMDR best used for?
Qualys VMDR is most often used for a hybrid workforce where scheduled network scans miss most laptops and continuous agent-based assessment is the only way to get real coverage, pci dss external scanning where an approved scanning vendor report is a contractual requirement, an estate spanning datacentre, multiple public clouds and endpoints that needs one vulnerability view rather than three tools, organisations replacing a manual patch-verification process with agent-reported evidence that a fix actually landed. Of those, a hybrid workforce where scheduled network scans miss most laptops and continuous agent-based assessment is the only way to get real coverage and pci dss external scanning where an approved scanning vendor report is a contractual requirement are not what Sigstore is typically brought in for.
What can Qualys VMDR do that Sigstore cannot?
Qualys VMDR covers Cloud Agent, Scanner appliances, Authenticated scanning, TruRisk scoring. Sigstore covers Fulcio, Rekor, Keyless signing, Multi-language clients.

Answered from the vendors’ own pages

Qualys VMDR: Agent or scanner: which do I need?

Usually both. The agent covers endpoints and servers you control and gives continuous data; scanners cover devices you cannot install an agent on, such as network gear, printers and appliances, and provide the external perimeter view.

Sigstore: Is the public instance really free?

Yes, with no contract and no paid tier. That is also the weakness: a 99.5 percent objective with no agreement, no remedy and support through Slack.

Qualys VMDR: Does it patch as well as detect?

Yes, through the Patch Management module, which is a separate subscription using the same agent. Core VMDR detects and prioritises but does not deploy fixes.

Sigstore: Has the public log moved to Rekor v2?

No. Version 2 reached general availability in October 2025 and self-hosters can use it, but the public instance still defaults to version 1 and the project has said it will for the foreseeable future.

Qualys VMDR: How are assets counted for licensing?

By the number of assets in inventory, which includes cloud instances and containers depending on the modules in use. Short-lived cloud assets count until they are purged, so purge settings directly affect what you consume.

Sigstore: Does Sigstore make my dependencies safe?

No, and this is a category error worth avoiding. It tells you who published something. It has no knowledge of what the artifact contains or whether it is vulnerable.

Qualys VMDR: Can I keep the data in a specific region?

Yes. Qualys operates several regional platform instances and you choose which one your subscription lives on. Moving between them later is not trivial, so decide before onboarding.

Sigstore: What are the rate limits?

Not published. Only the 100KB cap per attestation upload is documented, so do not design a high-volume pipeline around assumed throughput.

Qualys VMDR: Does it scan web applications?

Web Application Scanning is a separate module licensed per application, not part of core VMDR, and it is a dynamic scanner with the usual limits around authenticated flows in single-page applications.

Sigstore: Should we self-host it?

If a public record of every signature is unacceptable, or if a free service with no agreement cannot sit in your build path, then yes. Otherwise the public instance is what most projects use.

Share

Related pages

More on Qualys VMDR

More on Sigstore

Keep looking

Other head to heads