1. This presentation, including any supporting materials, is owned by Gartner, Inc. and/or its affiliates and is for the sole use of the intended Gartner audience or other authorized recipients. This presentation may contain information that is confidential, proprietary or otherwise legally protected, and it may not be further copied, distributed or publicly displayed without the express written permission of Gartner, Inc. or its affiliates. © 2011 Gartner, Inc. and/or its affiliates. All rights reserved. Ian Glazer Research VP, Agenda Manager Ian.glazer@gartner.com @iglazer Looking at federation through enterprise eyes

2. Recent Past

3. Federation = SSO

4. Hub and Spoke

5. Network of peers

6. Except Both hub and spoke, as well as, network of peers faced challenges scaling. -Some of these issues were technical. -Some of these issues were value-related. Communities of interest formed to address both challenges.

7. Today's World

8. Enterprise federation today Majority of enterprises do not participate in federations per se. However, enterprises do use federation technologies to connect to externally-provided services. Federation found its enterprise stride via SaaS adoption.

9. Status Quo

10. Welcome SaaS and Its Friends

11. Big shiny object!

12. Federation = Way to attach SaaS to the enterprise = SSO

13. Joining a Federation (The Short Version)

14. Sign business agreement

15. Except The business isn’t involved. Lawyers are involved. -Appropriate use of attributes and other information is a legal agreement. Business expectations are assumed to be met but inherent value of the service.

16. Determine RP’s needs

17. Except This isn’t a dialogue. “Provide the following attributes.” But what about entitlements? But what about authorization policies?

18. Start building SAML metadata

19. Map local attributes to RPs entitlements and attributes

20. Except These mappings are poorly documented Lots of tribal knowledge, less institutional knowledge Brittle mappings aren’t contextual friendly

21. Perform telekinesis

22. Perform telekinesis?

23. Action at a distance

24. Telekinesis Want to effect the authorizations in a remote system Provisioning local objects to effect remote authorization state But this is a hoax -Provision remote objects too

25. Spray old data everywhere Lots of attributes being pushed But now with less visibility! -RPs don’t know the quality of the data -RPs don’t know the data’s “Sell By” date -Information sources don’t always know where the data went

26. Today's Federated Provisioning Approaches

27. How to Connect People to Federated/Cloud Apps?

28. ?

29. Federation = Way to attach SaaS to the enterprise = SSO

30. Variety of techniques exist Broad spectrum of federated provisioning techniques -Manual one-off -“Traditional” -Creative Service providers lack consistency

31. Service Provider User Management Tools User management console: -Allows administrator to manually create and manage user accounts and privileges Bulk load operations: -Most support.csv file uploads Integration tools: -Proprietary user management APIs -Directory Synchronization -Support for IAM standards such as LDAP, SAML, SPML, etc.

32. User management console -Allows administrator to manually create and manage user accounts and privileges Bulk load operations -Most support.csv file uploads Integration tools -Proprietary user management APIs -Directory Synchronization -Support for IAM standards such as LDAP, SAML, SPML, etc. Majority Service Provider User Management Tools The select few

33. You Call This a Provisioning Tool?

34. Yes!

35. Local Connector A target application is just a target.

36. Cloud-Based Connector Everything is better in the cloud?

37. To the Cloud With Your Provisioning Server

38. Directory Synchronization Hosted On-Premises SaaS App Identity Repository Sync ServerEnterprise Identity Store (LDAP or AD) User Attributes Change Detection

39. Just-In-Time Provisioning via SAML

40. Welcome back!

41. Except All of these approaches only solve a portion of the problem: -Administrative authorization -SSO What happens with attributes and entitlements that get pushed to the federation partner/service? The enterprise fixation with federated authentication is blinding it from the larger issues – federated authorization 40

42. Administrative & runtime authorization

43. Two Kinds of Authorization Policies

44. Administrative Policies Sets up attributes and entitlements needed to enable access Ahead of their use

45. Provisioning Identity and access governance (IAG) -Access policy management -Role management In people’s heads -Workflow as manually enforced policies Where Do Administrative Policies Live?

46. Authorizes user to perform an action based on context Context = attributes, entitlements, and external factors Runtime Policies

47. Applications Web access management Externalized authorization management Federated services Where Do Runtime Policies Live?

48. Administrative Policy

49. ... in Action

50. Runtime Policy

51. ... in Action

52. Two Policies; One Goal

53. Attributes and Entitlements Dependencies

54. Each type of policy is maintained by separate teams with separate change management processes Neither kind of policy is aware of the other The teams maintained these policies are usually disconnected as well A Part and Yet Apart

55. To completely answer who can do what, both administrative and runtime environments must be examined Lack of awareness and linkage of both environments prevents complete answers Disconnected policies inhibit traceability We do not know if we are faithfully fulfilling business controls The Problem

56. Things don’t get better in a federated scenario

57. Brain surgery with Buckaroo Banzai 56 No, no! Don’t tug on that. You never know what it is attached to.

58. Manipulating attributes has unknown and unknowable consequences

59. Things don’t get better in a federated scenario Policy coherence is harder to achieve -Administrative policies are typically tribal in nature -Runtime policies are tribal in nature… and maintained by a different tribe! -Examining both sets of policies together is nearly impossible Federated SSO is not hard to establish -What happens after sign-on is crucial… and it is often well out of sight of the IdP 58

60. Looking into the near future

61. New developments in federated provisioning

62. Cloud HR Is the Lifecycle Feed

63. Cloud Directory Is the New Lifecycle Feed

64. Token Flipper Is the New Lifecycle Feed

65. Token Flipper Is the New Connector

66. Multi-Protocol JIT

67. But all of these solutions 66

68. will eventually fail.

69. Federation = Way to attach SaaS to the enterprise = SSO

70. Enterprise fixation with federated authentication is blinding it from the larger issue.

71. Federated Authorization

72. Shared Problems

73. Problems with our administrative tools Traditional on-premise administrative IAM tools are push-oriented. -These tools are “copy” not “reference” in nature. Policies should be provisioned, not attributed -Attributes should be referenced not copied. Authorization policies are increasingly split between administrative and run-time environments.

74. Problems with our runtime tools Runtime authorization environments often have opaque policies. -Hard to execute compliance-related activities. Attribute and entitlement meaning is inferred and codified in varying ways. What is acceptable use doesn’t always make it into the authorization policies. 73

75. Problems with federated services There are inconsistent ways of discovering entitlements -And on-premise tools (especially IAG) don’t know to deal with that Authorization policies is: -Sometimes managed by the enterprise -Sometimes by the RP -Sometimes both -And not rationalized against administrative policies 74

76. The problems beneath the problems Our models are insufficient -IAM tools do not model relationships well. -IAM tools do not model context well. Authorization is a problem of relationship and context. -Federated authorization is more so We push attributes instead of pull them. We lack mechanisms to share, distributed, and link authorization policy. 75

77. Calls to Action and Readings

78. What you should do: Know and Map Know your entitlements -An entitlement catalog transforms tribal knowledge into institutional knowledge Know your authorization policies -Document authorization policies -Try to close the gap between administrative and runtime authorization policies Map attribute dependencies -First step to addressing authorization policy coherence is knowing where shared attribute dependencies exist. 77

79. What can you do: Demand more Enterprises often lag higher education and federal governments in federation sophistication Vendors primarily selling to private enterprise will thus lag as well. Bulk load interface ≠ acceptable federation solution 78

80. What we must do: Hasten evolution The industry needs to move from pushing attributes to pushing authorization policies. Relationships and context must become first- class citizens in the IAM world and its tools. The enterprise notion of federation as glorified SSO must evolve. 79

81. Federation ≠ Way to attach SaaS to the enterprise ≠ SSO

82. Federation = Authorization across boundaries

83. Recommended Gartner Reading Achieving Greater Control Over Authorization Ian Glazer Combating Policy Sprawl: Identity and Access Governance and Externalized Authorization Management Systems Ian Glazer Upcoming - The Brave New World of Federation Robin Wilton Upcoming - Combating Policy Sprawl: Identity and Access Governance and Externalized Authorization Management Systems Mark Diodati 82