- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
A Target Set in Idira SIA is a configuration grouping that defines and matches the properties of infrastructure targets—primarily Windows machines for RDP access, but applicable to other resources—to which secure, privileged access can be granted.
From official Idira documentation (e.g., "Add and manage strong accounts for Windows targets" and "Use of target sets and connections in SIA"):
In SIA, target set is the collective name for the following group of target properties:
- Domain — the target's domain (e.g., cyberark.com or cyberarklab.local).
- Target — the target's identifier. For on-premises targets: usually the FQDN (e.g., mail.cyberark.com); for cloud targets: instance ID, private IP, or public IP.
- Suffix — the target's DNS suffix if configured differently from the domain (e.g., suffix.com).
A Target Set can include one, any two, or all three of these properties, providing flexible scoping: broad (e.g., entire domain via Domain only) or granular (e.g., specific server via Target FQDN).
Key Usage: In Conjunction with Strong Account Onboarding and Management
The term Target Set is primarily used in conjunction with a Strong Account during onboarding, configuration, and ongoing management. Strong accounts are the privileged credentials (vaulted in Privilege Cloud/SIA or PAM Self-Hosted, or stored directly in SIA) that enable access—either by retrieving secrets for sessions or by provisioning ephemeral (temporary) users for zero-standing-privileges (ZSP) flows.
Target Sets are associated with (and scoped to) a specific Strong Account. This ensures SIA applies the correct strong account only to matching targets, enforcing policies and least privilege.
This is done via the "Manage target set items" action in the SIA UI:
Steps (from docs):
This "Manage target set items" flow is the standard way to onboard or adjust Target Sets for a strong account—whether creating a new strong account (where you can add Target Sets during setup) or editing an existing one.
Connector pools define connectivity and routing (which connectors broker sessions to which targets). They do not officially use the term "Target Set" in current SIA documentation. Instead, they define target identifiers and/or networks to scope coverage.
Connector Pools:
Key Rules:
* Important note on multiple wildcard domains: If you add multiple wildcard domain entries in target identifiers or networks (e.g., *.domain1.com and *.domain2.com) within the same connector pool (or across pools that overlap incorrectly), you may encounter intermittent failures with the error DPA_CREATE_TUNNEL_BACKEND_CONNECTOR_UNREACHABLE. This happens because SIA may select a connector pool that matches the wildcard pattern but whose connectors do not actually have network reachability to the resolved target (e.g., it picks the wrong domain's pool/connectors). Connections will sometimes succeed (when it picks the correct matching pool) and sometimes fail unpredictably. To avoid this, use separate connector pools for distinct domains/subnets, or avoid broad overlapping wildcards in the same pool—prefer specific networks/CIDRs or explicit FQDNs/IPs where possible.
| Aspect | Target Sets (Strong Accounts) | Target Identifiers / Networks (Connector Pools) |
|---|---|---|
| Defined in | Strong accounts section ("Manage target set items") | Connector pools section (Add target identifier / Networks) |
| Properties | Domain, Target (FQDN/ID/IP), Suffix | FQDN/Hostname/IP, Network (CIDR), Cloud IDs (Instance ID, VPC/Subnet, etc.) |
| Purpose | Credential scoping + ZSP/ephemeral provisioning | Connectivity scoping + connector routing/load balancing |
| Matching Level | Credential/policy enforcement | Network/reachability + parallel connection attempts |
| Wildcard Support | Limited (mainly Suffix, e.g., *.suffix.com) | Yes (e.g., in networks or cloud scopes) |
| Certificate Validation | Per target set (Enabled/Disabled) | Global or per-connection type (e.g., TLS for vaulted) |
| When to Use | When controlling which creds apply to targets | When defining which connectors reach which environments |