Users could only request access that matched their job function
Certifications could contain extra information to help certifiers make
access decisions
Service accounts could be treated differently than user accounts
…and more!
Searching
• Ad hoc queries
• Access request process
Reporting
• Account Attributes
• Identity Attributes
…and more!
Copyright © SailPoint Technologies, Inc. 2017. All rights reserved. 16
• Extending identities
• Extending roles
• Extending applications
Extended
Attribute • Extending accounts
Use Cases • Extending certifications
• Extending entitlement catalog items
• Extending multiple objects
Request John
The Solution:
Primary_Campus: West
Campuses: North, South, West
Identity Rich
Attributes: Primary_Campus: North
Primary_Campus Campuses: North, East
Correlating The Problem: • Hospital associates can have multiple employee IDs,
corresponding to multiple jobs
Multiple • Access corresponds to job
Personas • Need to correlate access for multiple IDs to one person
The Solution:
• Add extended attribute to identities
• Populate with encrypted hashed PII data from
HR system
Identity Attribute:
• Correlate multiple HR feed records per person
Correlation_ID
HR Records
Identity Cube Victor, Doctor, fff13289
Victor
Victor, Professor, fff13289
Correlation_ID: fff13289
Victor, Researcher, fff13289
Copyright © SailPoint Technologies, Inc. 2017. All rights reserved. 20
Case Study Extending Identities
Specify The Problem: • Specify unique owners for Service Identity
Owners for Cubes
Service Cube
Reviews • Do not provide additional abilities (i.e.
The Solution: manager) for service cube owner
Reviews Karen.Johnson
Manager:
The Rich.Simms
Solution:
SrvCube_Owner: <empty>
Identity Attribute:
SrvCube_Owner Advanced Certification
(data type: identity)
Run Time
If no SrvCube_Owner, exclude from certification
Copyright © SailPoint Technologies, Inc. 2017. All rights reserved. 22
Case Study Extending Roles
Run Time
If Approval_Free, bypass approval step
The Solution:
Identity: ?
Security_Level
Role:
Req_Sec_Level ?
Security Roles
Identity Cubes Access Options
John ?
Spy Super User
Security_Level: 7
Req_Sec_Level:
The Solution: 10
Susan
Identity: Spy Audit ?
Security_Level: 12
Security_Level Req_Sec_Level: 10
Role: Ian
Spy Data Entry
Req_Sec_Level Security_Level: 2 ?
Req_Sec_Level: 5
Run Time
Is Req_Sec_Level less than user’s Security_Level?
Security Roles
Identity Cubes Access Options
John Spy Data?Entry
Spy Super User
Security_Level: 7
Req_Sec_Level:
The Solution: 10
Susan Spy Super User
Identity: Spy Audit Spy Data?Entry
Security_Level: 12
Security_Level Req_Sec_Level: 10 Spy Audit
Role: Ian
Spy Data Entry
Req_Sec_Level Security_Level: 2 <No Spy ?Options>
Req_Sec_Level: 5
Run Time
Is Req_Sec_Level less than user’s Security_Level?
Privileged • Set risk score for each account attribute and calculate
application risk scores
Service
• When certifying, identify privileged and service accounts
Run Time
If not Privileged or Service, exclude
Account Attribute:
Privileged
Account Attribute:
Privileged
Run Time
For AD group, set existing custom certification field to Windows_Servers