Cookie settings

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

Skip to content
Skip to content

Category comparison. Data discovery.

Agentless vs agent-based discovery: what each needs from you

What each approach asks of your hosts, your network and your team, shown on one database discovered both ways.

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

Overview

Host software, or an account on the source

Agent-based discovery installs a program, the agent, on each server, endpoint or virtual machine. The agent reads data where it sits and reports to a central service. Agentless discovery installs nothing on the source: a scanner elsewhere connects through the source’s own interfaces, using an account you create for it.

Choose per source. Use agents where a machine leaves the network or offers no remote interface, and a connection where the source offers one. NIST described the same trade-off for patch management tools in SP 800-40 Revision 3, a guide since withdrawn.

Compare

The two approaches side by side

Cells describe the typical tool in each approach. Check your own tool against them.

The two approaches side by side
AspectAgent-basedAgentless
Acts onServers, endpoints and virtual machines that run the agentDatabases, file shares, cloud storage and SaaS apps that offer an interface
Main strengthReaches local disks and machines that are rarely on the networkNothing to install or patch on each source
What it cannot doCover appliances and platforms the agent doesn’t support, or hosts where you can’t install softwareReach a source behind a firewall or address translation, or a machine that is off the network
Best fitLaptops, and servers with no remote interfaceEstates made mostly of databases, file shares and cloud services
A typical scenarioFind files on a field laptop that rarely connectsFind card numbers in a production database through a read-only account
Where it runsOn every host in scopeOn a scanner host that connects to each source
What you grantRights to install software, often with administrator privileges on each hostAn account on each source with the read rights the scan needs, and a network path to it
Load on the sourceProcessor and memory on each host while the agent worksQueries and reads against the source during a scan, plus network traffic
UpkeepAgent updates, compatibility checks and resources on every machineAccounts, credentials and network rules for the scanner
What a security review asksWhat the agent can do on each host, and how it is updatedWhere the scanner runs, what each account can read and how credentials are stored
Use cases

One database discovered both ways

Suppose a PostgreSQL server holds a billing database in a locked-down network segment. You need to know which tables hold card numbers.

One database discovered both ways
StepAgent-basedAgentless
What is installedAn agent on the database host, approved and installed by a server administratorNothing on the host
What is grantedInstall rights on the host, then the agent’s access to local files and the databaseA read-only database account created for the scanner
Network pathThe agent calls out to a central service, so the segment needs an outbound ruleThe scanner reaches the database port, so the segment needs an inbound rule from one host
Load while it runsProcessor and memory on the database host, shared with the databaseQueries against the database. IRIS is designed to limit load on production sources.
Upkeep next quarterAgent update, tested against the host’s patch cycleCredential rotation and the firewall rule
When it breaksA host patch stops the agent; its data goes quiet until someone noticesThe account expires; the connection reports failed and the source shows as unread
Who it’s for

When each approach fits

Agent-based fits when

The data sits on laptops or servers that are often off the network, or on systems with no interface you can read remotely.

Agentless fits when

The data sits in databases, file shares, cloud storage and SaaS apps that already offer a way to read them with an account.

You need both when

Your estate mixes endpoints with databases and cloud services. Choose per source, and record which approach covers which data.

Requirements

What to test in a proof of concept

Pick one production database and one file share, and put the same questions to each approach.

  • List what must be installed, which rights that needs and which firewall rule opens.
  • Run a scan in a quiet window and watch processor use and connection counts on the source.
  • Revoke the scan account and check that the tool reports the source as failed, with a reason.
  • Ask where source credentials are stored and who can read them.
  • Ask for the output on a source the tool cannot reach, and check it is listed.
Capabilities

How IRIS fits

Read-only access, deployable in your environment, agentless where the source supports it.

Read-only access

IRIS uses read-only access to your sources, agentless where the source supports it, with accounts you create.

Each connection tested

Each source connection is tested and reports connected, partial or failed.

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.

Capabilities vary by edition.

FAQ

Agent and connection questions

Protect your brand. Start with your data.

Run the access test on one production database this week, then book a demo or take the tour.