Identity and Access Management Overview Rafal Lukawiecki Strategic

Identity and Access Management: Overview Rafal Lukawiecki Strategic Consultant, Project Botticelli Ltd rafal@projectbotticelli. co. uk www. projectbotticelli. co. uk Copyright 2006 © Microsoft Corp & Project Botticelli Ltd. E&OE. For informational purposes only. No warranties of any kind are made and you have to verify all information before relying on it. You can re-use this presentation as long as you read, agree, and follow the guidelines described in the “Comments” field in File/Properties. This presentation is based on work of many authors from Microsoft, Oxford Computer Group and other companies. Please see the “Introductions” presentation for acknowledgments.

2 Objectives Build a good conceptual background to enable later technical discussions of the subject Overview the problems and opportunities in the field of identity and access management Introduce terminology Highlight a possible future direction

3 Session Agenda Identity Problem of Today Identity Laws and Metasystem Components and Terminology Roadmap

4 Identity Problem of Today

5 Universal Identity? Internet was build so that communications are anonymous In-house networks use multiple, often mutuallyincompatible, proprietary identity systems Users are incapable of handling multiple identities Criminals love to exploit this mess

6 Explosion of IDs Business Partners Automation (B 2 B) # of Digital IDs Company (B 2 E) Customers (B 2 C) Mobility ns tio Internet a ic pl Ap Client Server Mainframe Time Pre 1980’s 1990’s 2000’s

7 The Disconnected Reality • Authentication • Authorization • Identity Data HR System • Authentication • Authorization • Identity Data NOS • Authentication • Authorization • Identity Data Enterprise Directory • Authentication • Authorization • Identity Data Lotus Notes Apps Infra Application COTS Application In-House Application “Identity Chaos” Lots of users and systems required to do business Multiple repositories of identity information; Multiple user IDs, multiple passwords Decentralized management, ad hoc data sharing

8 Multiple Contexts Customer satisfaction & customer intimacy Cost competitiveness Reach, personalization Your SUPPLIERS Your CUSTOMERS Collaboration Outsourcing Faster business cycles; process automation Value chain Your COMPANY and your EMPLOYEES M&A Mobile/global workforce Flexible/temp workforce Your REMOTE and VIRTUAL EMPLOYEES Your PARTNERS

9 Trends Impacting Identity Rising Tide of Regulation and Compliance SOX, HIPAA, GLB, Basel II, 21 CFR Part 11, … $15. 5 billion spend in 2005 on compliance (analyst estimate) Deeper Line of Business Automation and Integration One half of all enterprises have SOA under development Web services spending growing 45% CAGR Increasing Threat Landscape Identity theft costs banks and credit card issuers $1. 2 billion in 1 yr $250 billion lost in 2004 from exposure of confidential info Maintenance Costs Dominate IT Budget On average employees need access to 16 apps and systems Companies spend $20 -30 per user per year for PW resets Data Sources: Gartner, AMR Research, IDC, e. Marketer, U. S. Department. of Justice

10 Pain Points IT Admin Too many user stores and account admin requests Unsafe sync scripts Developer Redundant code in each app Rework code too often End User Too many passwords Long waits for access to apps, resources Security/ Compliance Too many orphaned accounts Limited auditing ability Business Owner Too expensive to reach new partners, channels Need for control

11 Possible Savings Directory Synchronization “Improved updating of user data: $185 per user/year” “Improved list management: $800 per list” - Giga Information Group Password Management “Password reset costs range from $51 (best case) to $147 (worst case) for labor alone. ” – Gartner User Provisioning “Improved IT efficiency: $70, 000 per year per 1, 000 managed users” “Reduced help desk costs: $75 per user per year” - Giga Information Group

12 Can We Just Ignore It All? Today, average corporate user spends 16 minutes a day logging on A typical home user maintains 12 -18 identities Number of phishing and pharming sites grew over 1600% over the past year Corporate IT Ops manage an average of 73 applications and 46 suppliers, often with individual directories Regulators are becoming stricter about compliance and auditing Orphaned accounts and identities lead to security problems Source: Microsoft’s internal research and Anti-phishing Working Group Feb 2005

13 One or Two Solutions? Better Option: Build a global, universal, federated identity metasystem Will take years… Quicker Option: Build an in-house, federated identity metasystem based on standards Federate it to others, system-by-system But: both solutions could share the same conceptual basis

14 Identity Laws and Metasystem

15 Lessons from Passport designed to solve two problems Identity provider for MSN 250 M+ users, 1 billion logons per day Significant success Identity provider for the Internet Unsuccessful: Not trusted “outside context” Not generic enough Meant giving up control over identity management Cannot re-write apps to use a central system Learning: solution must be different than Passport

16 Idea of an Identity Metasystem Not an Identity System Agreement on metadata and protocols, allowing multiple identity providers and brokers Based on open standards Supported by multiple technologies and platforms Adhering to Laws of Identity With full respect of privacy needs

17 Roles Within Identity Metasystem Identity Providers Organisations, governments, even end-users They provide Identity Claims about a Subject Name, vehicles allowed to drive, age, etc. Relying Parties Online services or sites, doors, etc. Subjects Individuals and other bodies that need its identity established

18 Metasystem Players Identity Providers Issue identities Relying Parties Require identities Subjects Individuals and other entities about whom claims are made

19 Identity Metasystem Today Basically, the set of WS-* Security Guidelines as we have it Plus Software that implements the services Microsoft and many others working on it Companies that would use it Still to come, but early adopters exist End-users that would trust it Will take time

20 Identity Laws www. identityblog. com 1. User Control and Consent 2. Minimal Disclosure for a Constrained Use 3. Justifiable Parties 4. Directed Identity 5. Pluralism of Operators and Technologies 6. Human Integration 7. Consistent Experience Across Contexts

21 Enterprise Applicability That proposed metasystem would work well inside a corporation Of course, we need a solution before it becomes a reality Following the principles seems a good idea while planning immediate solutions Organic growth likely to lead to an identity metasystem in long term

22 Enterprise Trends Kerberos is very useful but increasingly it does not span disconnected identity forests and technologies easily We are moving away from static Groups and traditional ACLs… Increasingly limited and difficult to manage on large scales …towards a dynamic combination of: Role-Based Access Management, and, Rich Claims Authorization PKI is still too restrictive, but it is clearly a component of a possible solution

23 Components and Terminology

nagement 24 What is Identity Management? We b. S Sec ervice s urit y Dig i Ma Righ tal na ts ge me nt Ma Role nag em le Sign e Sing nt On Fed era tio n Provisioning Autho rizatio n Strong Authentication Sec ure Rem Acc ess es Directori Auditing & Reportin g PKI

25 Identity and Access Management Directory Services Repositories for storing and managing accounts, identity information, and security credentials A system of procedures, policies and technologiesprocess of authenticating credentials and The to manage the lifecycle Access controlling access to networked resources Management entitlements of electronic and based on trust and identity credentials Identity Lifecycle Management The processes used to create and delete accounts, manage account and entitlement changes, and track policy compliance

26 Remember the Chaos? • Authentication • Authorization • Identity Data HR System • Authentication • Authorization • Identity Data NOS • Authentication • Authorization • Identity Data Enterprise Directory • Authentication • Authorization • Identity Data Lotus Notes Apps Infra Application COTS Application In-House Application

27 Identity Integration Enterprise Directory Identity Integration Server • Authentication • Authorization • Identity Data • Authentication • Authorization • Identity Data HR System Student Admin Lotus Notes Apps Infra Application COTS Application In-House Application

28 IAM Benefits today (Tactical) Save money and improve operational efficiency Improved time to deliver applications and service Benefits to take you forward (Strategic) New ways of working Improved time to market Enhance Security Regulatory Compliance and Audit Closer Supplier, Customer, Partner and Employee relationships

29 Some Basic Definitions Authentication (Auth. N) Verification of a subject’s identity by means of relying on a provided claim Identification is sometimes seen as a preliminary step of authentication Collection of untrusted (as yet) information about a subject, such as an identity claim Authorization (Auth. Z) Deciding what actions, rights or privileges can the subject be allowed Trend towards separation of those two Or even of all three, if biometrics are used

30 Components of IAM Administration User Management Password Management Workflow Authorization Identity Management Account Provisioning Account Deprovisioning Synchronisation Administration Authentication Authorization Access Management Authentication Delegation Reliable Identity Data

31 IAM Architecture

32 Roadmap

33 Microsoft’s Identity Management Directory (Store) Services Access Management Identity Lifecycle Management Active Directory & ADAM Active Directory Federation Services Identity Integration Server Extended Directory Services Authorization Manager Biz. Talk PKI / CA Enterprise Single Sign On Audit Collection Services for Unix / Services for Netware ISA Server SQL Server Reporting

34 Components of a Microsoft-based IAM Infrastructure Directory Active Directory Application Directory AD/AM (LDAP) Lifecycle Management MIIS Workflow Biz. Talk, Partner Solutions (Ultimus BPM, SAP) Role-Based Access Control Authorization Manager or Partner Solutions (ex: OCG, RSA) and traditional approaches Directory & Password Synchronization MIIS & Partner solutions SSO (Intranet) Kerberos/NTLM, Vintela/Centrify Enterprise SSO (Intranet) Sharepoint ESSO, Biz. Talk ESSO, HIS ESSO Strong Authentication Smart. Cards, CA/PKI, Partner (eg. RSA – Secur. ID, MCLMS, Wize. Key) Web SSO ADFS, Partner (eg. RSA – Clear. Trust) Integration of UNIX/Novell SFU, SFN, Partner (eg. Vintella/Centrify) Federation ADFS

35 Summary

36 Summary We have reached an “Identity Crisis” both on the intranet and the Internet Identity Metasystem suggests a unifying way forward Meanwhile, Identity and Access Management systems need to be built so enterprises can benefit immediately Microsoft is rapidly becoming a strong provider of IAM technologies and IM vision www. microsoft. com/idm & www. microsoft. com/itsshowtime & www. microsoft. com/technet

37 Special Thanks This seminar was prepared with the help of: Oxford Computer Group Ltd Expertise in Identity and Access Management (Microsoft Partner) IT Service Delivery and Training www. oxfordcomputergroup. com Microsoft, with special thanks to: Daniel Meyer – thanks for many slides Steven Adler, Ronny Bjones, Olga Londer – planning and reviewing Philippe Lemmens, Detlef Eckert – Sponsorship Bas Paumen & NGN - feedback