Application

The Application object (called a Source in Identity Security Cloud) represents a connected system that SailPoint governs. It holds the connector type, connection settings, account and group schemas, and the correlation configuration for that one system. Aggregation and provisioning both act through the Application object.

• Connector configuration: type, host/URL, credentials and options.
• Schemas: the account schema (and group/entitlement schema) describing the attributes read from the target.
• Correlation config: how the target’s accounts map to identities.
• Provisioning settings: whether and how changes are written back.

An application can be an authoritative source (usually HR), which supplies identities and their attributes, or a target, which supplies accounts to govern. Some are both. Designating authoritative sources correctly is critical, they drive identity creation and the attributes everything else depends on.

When you aggregate an application, its accounts are read into the warehouse as Links and correlated to identities. From that point the application’s access appears on the relevant cubes and can be governed like any other.

Bringing an application under governance means creating the Application object, configuring its connector, mapping its schema, defining correlation, aggregating, and verifying. An application not onboarded is invisible to every control, so coverage, how many of your systems are actually governed, is a key programme metric.

• Mis-mapped schema breaking correlation or provisioning.
• Wrong authoritative designation, letting a target overwrite identity data.
• Low coverage, sensitive systems left un-onboarded and ungoverned.