Identity is defined as the quality or condition of being the same; absolute or essential sameness; oneness. Identity is what makes something or someone the same today as it, she, or he was yesterday. Importantly, identity can refer to a thing (e.g., a computer) as well as a person. Things and people can have different identities when working with different systems, or can have more than one identity when working with a single system, perhaps when working in different roles.
A typical large enterprise is operated by people who join as staff (permanent or temporary), contractors, and business partners. These people are assigned roles and act in them. These roles are always “temporary” in the sense that they have no fixed duration. Eventually people either change roles or leave, creating a need for identity information to be actively managed and maintained throughout its lifecycle, frequently across multiple systems.
Identity Management (IdM)
IdM manages an identity’s lifecycle through a combination of processes, organizational structure, and enabling technologies. Identification is the process of assigning an identifier to every individual or system to enable decisions
about the levels of access that should be given. Identifiers must contain the following:
- Uniqueness- Each identifier (e.g. user ID or University M Number) is unique; that is, each
identifier is associated with a single person or other entity
- One Identifier per Individual- An individual may have no more than one University identification number
- Non-Reassignment- Once an identifier is assigned to a particular person it is always associated with that person. It is never subsequently reassigned to identify another person or entity.
Access Management (AM)
AM primarily focuses on Authentication and Authorization. The authentication process determines whether someone or something is, in fact, who or what it is
declared to be. Authentication validates the identity of the person. Authentication methods involve presenting both a public identifier (such as a user name or identification number) and private authentication information, such as a Personal Identification Number (PIN) or password. All systems and applications must use encrypted authentication mechanisms and abide by the following:
- Authentication credentials will not be coded into programs or queries unless they are
encrypted, and only when no other reasonable option exits.
- Unique initial passwords must be provided through a secure and confidential manner and initial
passwords must be changed upon first logon
- Passwords must not be stored in clear text or in any easily reversible form.
- Vendor-supplied default and/or blank passwords shall be immediately identified and reset upon installation of the affected application, device, or operating system.
Authorization is the process used to grant permissions to authenticated users. Authorization grants the
user, through technology or process, the right to use the information assets and determines what type
of access is allowed (read-only, create, delete, and/or modify). The system or application should
determine if the user has permission to perform the requested operation.
Users are not permitted to access sensitive data unless the Data Owner has given written permission
through established business processes. Data Owners are individually responsible for establishing data
access procedures that must include, at a minimum, the following:
- Access request forms must be used to request, change, or delete existing access privileges to systems that contain sensitive information.
- To maintain the requirements of minimum necessary and least privilege, when a user transfers, all accounts should first be disabled, privileges removed, then accounts re-enabled and privileges added that are required in the user’s new role.
- For new accounts and changes to existing accounts, portions of the form must be completed and authorized by the:
o Person who is requesting access to the system
o User’s supervisor and/or department head (or designated representative)
o Data Owner
- For account deletions, report separations in a timely manner when workforce members are reassigned, promoted, or separated. For Termination with cause, deactivation must occur immediately.
- Periodic review of user privileges to ensure access is commensurate with user’s current responsibilities, as well as modification, removal or inactivation of accounts when access is no longer required.
Segregation of Duties (SoD)
Access privileges granted to each individual user will adhere to the principles of separation of duties.
Technical or administrative users, such as programmers, system administrators, database administrators, security administrators of systems and applications must have an additional, separate end-user account to access the system as an end-user to conduct their personal business.
Identity & Access Management concepts and processes can be broadly
broken down into the following three categories:
• People and Relationships – The myriad of individuals who need to interact with the
University’s online resources and the related life-cycles of these interactions.
• Creation and Maintenance of Identities – The management of the assignment of
identity records and issuance of identity credentials (IDs, passwords, and other tokens)
to individuals.
• Access to Data and Applications – The management of access rights to online
resources—ensuring they are appropriately and efficiently granted when needed,
auditable, and updated or removed when circumstances change.
Foundational Goals - Four overarching goals provide the foundation for a comprehensive
strategy toward the implementation of Identity & Access Management at Penn State:
• Increase collaboration and innovation
• Improve customer service
• Increase efficiency, productivity, and cost containment
• Improve security of digital assets and mitigate risks
IAM strategy
1. Create a Comprehensive Policy for Identity & Access Management – A
comprehensive policy, covering all aspects of Identity & Access Management, does not exist today and needs to be developed. This policy framework is crucial for the project’s success.
2. Develop a Plan for Formal Risk Assessment – A systematic risk management
process is needed to evaluate the technology and information systems that are critical to the mission.
3. Create a Central Person Registry – A single centralized person registry is needed to combine identity data records from disparate systems, ensuring the integrity and
availability of person records.
4. Add Level of Assurance Component to Accounts and Access Decisions – A more
granular approach to account creation and access decisions is needed. A Level of
Assurance component will provide this flexibility and is also being required by federal
agencies.
5. Promote Single Sign-on, Federated Identities, and Better Control of University
Digital Credentials – Better control of Penn State digital credentials is needed—
especially in regards to the use of these credentials with outside agencies, hosted
vendor solutions, and other institutions of higher education. Single sign-on and
federated identities will provide this control.
6. Streamline Vetting, Proofing, and Issuance of Digital Credentials – Significant gains in efficiency could be realized by overhauling the current processes for creating
accounts and issuing credentials.
7. Automate the Provisioning (and De-provisioning) of Access Rights – Customer
service and security could both be significantly increased by automating the provision of access based on affiliation, roles, and attributes.
8. Promote Awareness and Education of the Importance of Identity & Access
Management – Initial awareness and on-going education is needed to promote
understanding of the importance of Identity & Access Management and achieve buy-in from stakeholders.
more about I&AM
more about IAM assessment
more about IAM infrastruture
more about federated identity
more from Wikipedia http://en.wikipedia.org/wiki/Identity_access_management
more from Youtubehttp://www.youtube.com/watch?v=scoDacOFRPo