Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Category comparison. Deployment.

Self-hosted vs SaaS data security tools: where findings live

Who runs the tool, where scan results are stored and what leaves your network, answered as a vendor questionnaire.

By Dipal Panchal, co-founder and CEO · Updated November 8, 2026

Overview

The tool reads your data; findings map it

A self-hosted data security tool runs on infrastructure you control, on-premises or in your own cloud account. Its scanner, its database and its findings sit with your team. A SaaS (software as a service) tool runs in the vendor’s cloud. In NIST’s definition of SaaS, the customer doesn’t manage or control the underlying infrastructure, apart from limited application settings.

For a DSPM tool the choice matters twice: it reads your most sensitive data, and its findings are a map of where that data is. Decide where that map should live, then test the claim.

Explore deployment
Compare

The two models side by side

Cells describe the typical tool in each model; the NIST Cybersecurity Framework (CSF) row is our reading. Many tools mix the two, so ask where each part runs.

The two models side by side
AspectSelf-hostedSaaS
Acts onSources reachable from your network, including internal databases and file sharesSources the service can reach: cloud services, or your network through a route you open
Main strengthFindings and credentials stay inside your infrastructureNo servers for your team to run, patch or back up
What it cannot doRemove the operating work: hosting, backups, upgrades and capacity stay with youKeep findings out of the vendor’s cloud, or run with no route to the vendor
Best fitPolicy or regulators expect sensitive data and findings to stay on infrastructure you controlMostly cloud sources and a team that doesn’t want more infrastructure
A typical scenarioA bank scans databases on a network with no route to the internetA software company scans its SaaS apps and cloud storage
Where it runsOn servers or cloud accounts you controlIn the vendor’s cloud, shared with other customers or set apart
Who operates itYour team: hosting, backups, upgrades and capacityThe vendor, under a contract and service levels
UpdatesInstalled when your team decidesApplied by the vendor, usually without action from you
Supplier risk (NIST CSF 2.0 GV.SC)Covers the software and how its releases are built and deliveredCovers the service, where it runs, who operates it and its subprocessors
Use cases

A vendor questionnaire for each model

Ten questions a security reviewer sends before approving a data security tool. The answers describe each model in general; get the vendor’s own in writing.

A vendor questionnaire for each model
Questionnaire itemSelf-hostedSaaS
1. Where is data processed?In your infrastructureIn the vendor’s cloud, in the regions it names
2. Where are findings stored?In a database you hostIn the vendor’s cloud, under its retention rules
3. Who can read findings?Your staff, by your access rulesYour staff, plus any vendor staff the contract allows
4. What leaves our network?Only the outbound connections the tool makesDepends on design: samples, metadata or only results
5. Where are source credentials held?Inside your infrastructureBy the service, or in your account, by design
6. How is it updated?You install releases on your scheduleThe vendor applies updates
7. Can it run with no internet route?Where the tool allows itNo; it needs the vendor’s service
8. Who are the subprocessors?None run your scans; ask about licensing and supportListed in the data processing agreement
9. How is data deleted at exit?You delete it from your own databaseThe contract sets a deletion period and proof
10. How does the vendor access support cases?Only if you grant accessPer the vendor’s support process; ask who and how it is logged
Who it’s for

When each model fits

Self-hosted fits when

Your policy or your regulators expect sensitive data and findings to remain on infrastructure you control, or sources sit on networks with no route out.

SaaS fits when

Your sources are mostly cloud services, your team doesn’t want to run more infrastructure, and the vendor’s processing terms pass your review.

You might use both when

A SaaS tool covers your cloud services, and a self-hosted tool covers databases and file shares that can’t be reached from outside.

Requirements

What to test in a proof of concept

Put the questionnaire to the vendor in writing, then check the answers on a running system.

  • Record outbound connections from the tool’s host for a day and match them to the vendor’s list.
  • Ask where credentials, samples and findings are stored, and find each one.
  • Cut the internet route and check what still works.
  • Ask for the exit procedure and the deletion proof.
  • Ask who at the vendor can see a support case, and how that is logged.
Capabilities

How IRIS fits

IRIS is customer-hosted by default. Sylox-hosted environments are used only for demos and agreed pilots.

In your own infrastructure

IRIS can be deployed in your own infrastructure, on-premises or in any cloud, so your data stays within your environment.

Results in your database

IRIS runs on infrastructure you control. Findings, coverage records and evidence are stored in the IRIS database there.

What connects outbound

The license service, once at activation and when an admin chooses to validate. A time source, which can be your own. SaaS services only during scans of those sources.

Verified releases, no run-time updates

Releases arrive as verified bundles. IRIS pulls no updates at run time, so the release you approved is the one that runs.

Capabilities vary by edition.

Official sources

  1. SP 800-145, The NIST Definition of Cloud Computing, NIST. Opened November 8, 2026.
  2. CSWP 29: Cybersecurity Framework 2.0, NIST. Opened November 8, 2026.
FAQ

Self-hosted and SaaS questions

Protect your brand. Start with your data.

Send the ten questions to your shortlist this week, then book a demo to plan hosting with a specialist.