Identity Strategy Flashcards
What Identity Attributes should be captured?
Any attributes that would help an access reviewer to make solid ‘Keep/Remove’ decisions
Any attribute that would help you to SORT, FILTER, or GROUP populations of identities for reviews, reports, or rules
If using the Access Request module – include attributes needed to restrict forms
Why should any extra identity attributes be left out?
Unneeded fields will simply pollute your database, make collections take longer, and increase opportunities for data integrity problems
Why is the supervisor field (Supervisor unique ID) considered a common identity field?
Having the name makes reports and screens more useful – but must have the supervisor’s unique ID to be able to route reviews
What are some examples of multiple Identity sources within clients environments?
One or more HR sources for full-time employees
One or more systems of record for contractors, part-timers, independent agents, volunteers and other non-employees that access the network and/or applications
One or more technical systems such as Active Directory or eDir that have important attributes not found in the other systems
How is it decided what will be the primary unifying value
the best maintained and trusted information
