Correlation rule
Quick answer
How correlation rules match aggregated accounts to the right identity in SailPoint IdentityIQ.
Key takeaways
- Correlation decides which identity an account belongs to
- Rules return the identity attribute and value to match on
- Use config for simple matches, rules for logic and fallbacks
- Uncorrelated accounts need a fallback or manual fix
The correlation problem
When accounts are aggregated, IdentityIQ must decide which identity each account belongs to. Correlation rules (or correlation config) provide the matching logic.
How it works
The rule receives the account attributes and returns a map identifying the matching identity attribute and value, for example matching an AD employeeID to the identity employeeNumber.
Config vs rule
Simple attribute matches are done with correlation configuration; a rule is used when matching needs logic, fallbacks or normalisation.
Uncorrelated accounts
Accounts that match no identity become uncorrelated and often need a fallback rule or manual correlation to resolve.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
What does correlation determine?
- A. The password policy
- B. Which identity an account belongs to
- C. The approval scheme
- D. The connector type
Show answer
B. Which identity an account belongs to
Correlation matches each aggregated account to the correct identity.