SIA Target Sets : How they work

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Secure Infrastructure Access
5 min read
L0 Member
No ratings

Question

What Is a Target Set?

 

Answer

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):

  1. In SIA, navigate to Strong accounts.
  2. The list of strong accounts displays in a table (showing name, domain, etc.).
  3. For the relevant strong account, click the More options button (ellipsis ⋮) on its row.
  4. Select Manage target set items (this opens the "Strong account target set" page for that account).
  5. On this page, you can:
    • Search for existing target sets (by domain, suffix, or target).
    • Add a new target set: Click Add a target set → In the popup, select Type (Domain, Target, or Suffix) from the dropdown → Enter the value → Toggle Certificate Validation (Enabled/Disabled) → Save (or Save and add another).
    • Edit/delete existing items: Select one or more → Use actions like Delete, Enable validation, or Disable validation.
  6. Changes apply immediately to scope the strong account.

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: Target Identifiers and Networks (Sometimes Loosely Called "Target Sets")

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:

  • Target Identifiers (added via "Add target identifier" in pool setup):
    • Types: FQDN, Hostname, IP address, Network (CIDR/subnet), Cloud-specific (Instance ID, Private/Public IP, AWS Account/VPC/Subnet, Azure Subscription/Vnet/Subnet, Google Cloud Project/VPC/Subnet).
    • Recommendation: Define multiple identifiers for flexible access (e.g., connect by FQDN, IP, or cloud ID).
  • Networks (assigned to the pool): Broader scoping (e.g., entire subnet/VPC). When using a network, target identifiers are optional but can refine coverage.

Key Rules:

  • All connectors in a pool must have access to the same targets (same networks/identifiers) for consistent load balancing/high availability.
  • SIA attempts parallel connections from matching pools/connectors; first success wins.
  • Multiple pools can match the same target for redundancy.

 

* 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.

Key Differences Summary

AspectTarget Sets (Strong Accounts)Target Identifiers / Networks (Connector Pools)
Defined inStrong accounts section ("Manage target set items")Connector pools section (Add target identifier / Networks)
PropertiesDomain, Target (FQDN/ID/IP), SuffixFQDN/Hostname/IP, Network (CIDR), Cloud IDs (Instance ID, VPC/Subnet, etc.)
PurposeCredential scoping + ZSP/ephemeral provisioningConnectivity scoping + connector routing/load balancing
Matching LevelCredential/policy enforcementNetwork/reachability + parallel connection attempts
Wildcard SupportLimited (mainly Suffix, e.g., *.suffix.com)Yes (e.g., in networks or cloud scopes)
Certificate ValidationPer target set (Enabled/Disabled)Global or per-connection type (e.g., TLS for vaulted)
When to UseWhen controlling which creds apply to targetsWhen defining which connectors reach which environments
 
 

Matching and Full Flow

  • Connectivity first: SIA resolves the target and matches against connector pool target identifiers/networks → Routes through qualifying connectors/pools.
  • Credential/policy next: Matches target against strong account Target Sets → Applies strong account (vaulted creds or ZSP generation).
  • If no connector pool matches → Connection fails (no reachability).
  • If no Target Set matches → No allowed strong account → Access denied.

Best Practices

  • Use Target Sets narrowly on strong accounts for least-privilege credential scoping.
  • Use target identifiers/networks broadly on connector pools for reliable routing (tag pools regionally, e.g., corp.example.com\AWS-us-east-1).
  • For on-prem: Often network/CIDR + FQDN/IP identifiers.
  • For cloud/ZSP: Include Instance ID + IPs for robust matching.
  • Test: Use session diagnostics for mismatches.
Rate this article:
  • 1298 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:46 AM
Updated by: