How many Targets are configured on a typical Agent?
The number of Targets configured per Agent depends on multiple factors, described in this article, which also includes Target-Agent allocation recommendations.
In Spirion Sensitive Data Platform (SDP), the number of Targets configured per Agent depends on the deployment architecture and Agent type:
1. Endpoint Agents (1 Target per Agent)
- Configuration: Installed directly on local workstations, laptops, or servers (Windows, macOS, Linux).
- Target Count: Typically 1 Target — The host machine itself (local hard drives, local user directories, system storage).
- Purpose: Performs local background scanning directly on the host using system resources. The priority of the scan can be customized to minimize impact on end users. See "Can a Spirion Agent be set to run as "low priority"?"
2. Centralized / Discovery Agents (Multiple Targets per Agent or Agent Pool)
- Configuration: Installed on dedicated discovery servers or deployed as worker Agent pools.
- Target Count: Multiple Targets (often tens to hundreds of Targets assigned sequentially or across an Agent pool).
- Target Types:
- Network File Shares: SMB/NFS shares across departments or file servers.
- Databases: Relational/SQL databases and data warehouses.
- Cloud / SaaS Repositories: Microsoft 365 (SharePoint, OneDrive, Exchange mailboxes), Google Workspace, Amazon S3 buckets, Box, Dropbox.
- Purpose: Centralized Agents connect remotely across the network or via APIs to perform discovery on Agentless Targets.
Key Operational Factors for Target Allocation
- Resource & Performance Limits: Assigning too many large Targets (for example, massive file shares or multi-terabyte databases) to a single Agent can create scan bottlenecks. Organizations typically distribute large Targets across an Agent Pool to enable parallel scanning.
- Network Proximity & Latency: Centralized Agents are usually positioned close to their assigned Targets (for example, an Agent deployed in AWS to scan S3 buckets vs. an on-premise Agent scanning local SAN storage).
- Authentication & Permissions: Cloud and network Targets often require specific service account credentials, which dictates which Agent or Agent pool handles those scan jobs.