| HOME | EVENTS | RESOURCES | NEWSLETTERS | IDENTORATI | ABOUT |
|
|
|
A Journal of |
|
Departments Home
|
User provisioning: right access to the right peopleProvisioning's efficacy is not limited to employees; it can be used to manage access to business systems for contractors, partners and customers Last issue we touched on a new definition for identity. Today I'd like to present the definitive view of the first, both historically as well as in the context of adding identity and access management (IAM) to your organization. User provisioning has been called the "killer app" for identity management. It started us down the road to IdM over a dozen years ago. In fact, we almost take it for granted today. But what does it involve, what does it imply, and why does it matter? Ian Glazer and Kevin Kampman of the Burton Group (now part of Gartner) issued a paper just before Christmas called "Roles and User Provisioning", which unfortunately is behind a paywall. But if you're a Burton (or, presumably a Gartner) client you should have access to it. I don't want to get into roles just now (we'll eventually get back to that subject, though, as we continue to review the fundamentals). But Glazer and Kampman present provisioning in a succinct, yet complete, definition that goes like this: "Ensuring that the right people get access to the right business resources at the right time, provisioning is the enterprise plumbing that promotes productivity and reduces enterprise risk. Provisioning primarily occurs at three critical points in an employee's relationship with the enterprise: when the employee joins, changes jobs within, and leaves the enterprise. In the first of these, known as onboarding, provisioning sets up employees with access to business systems that have capabilities appropriate to each employee's job function. It is imperative that an employee starts on Day One with all of the business resources needed to be productive. Delays in receiving access means lost productivity. When an employee transfers from one role to another within the enterprise, provisioning removes access to business systems that is no longer needed -- thus reducing the risk that the employee will be able to use that access inappropriately -- while doling out new access the employee needs to be productive. Finally, when an employee leaves the enterprise, provisioning removes all access, thus reducing the risk that the employee can access business systems after separating from the enterprise. Provisioning's efficacy is not limited to just employees; it can be used to provide and manage access to business systems for contractors, partners and even customers. A well-run provisioning process takes the manual effort and guesswork out of granting the right access to the right people." And, really, that's it in a nutshell: granting the right access to the right people. Make sure your processes have all three parts: on-boarding, transforming (or moving) and de-provisioning. From a security standpoint, the latter two are more important than the first. Join me when I talk about provisioning in a Webinar next Tuesday. Subscribe to this and other newsletters. The 'game' of identityA look back at an early identity-based application Back in the day when personal computers where starting to become commonplace, the various machines (Commodore VIC-20, Atari, TRS-80, Apple I and others) each had its own operating system. Software could only run on one machine, which meant there were few choices and high prices. But what they all had was built-in BASIC, the programming language. Most had a BASIC interpreter, but the IBM PC came with a BASIC compiler (showing, I guess, that it was intended for bigger and better things). It struck me the other day that it was back then, on my old VIC-20, that I first encountered an identity-based application. It was a game, written in BASIC that had to be typed in to the computer called "Animal." The game (and you can see the code here) purported to be a "guessing" game where the computer guessed the name of an animal you were thinking of. It did this by asking a series of yes/no questions and following a decision tree to an endpoint. Then it would ask, for example: "Are you thinking of an elephant?" If you answered "No" it would ask what animal you were thinking of (say, a camel) and what question would differentiate it from an elephant ("It lives in the dessert"). It thus built up a series of attributes which -- taken together -- identified a particular animal. That's not so very different from how we identify people. It's been a while, so it might be a good time to try -- once again -- to define "identity". What follows is my thinking, but as always, I'd like to hear what you have to say. An "identity" is a description of a thing. That is, a list of descriptors, or "attributes," one or more of which (when grouped together) constitute a unique identifier for that entity within a given domain. The descriptors may be subjective (name, favorite music, religion and so on) or objective (sex, race, ability to dance, fingerprint and so on). Objective identifiers can be tested for, subjective ones cannot. A disinterested third party, for example, could pick out "everyone with black hair" from a lineup, but could not pick out "everyone who preferred cats to dogs." Subjective identifiers (which includes account numbers, usernames, passwords and so on) can be vouched for by third-party identity providers, the basis for so-called user-centric identity schemes. Objective identifiers might be used by those identity providers as a way to validate an entity's identity. That doesn't seem particularly deep, overly simple or lacking in any major way. But, if I'm headed down the wrong path, please enlighten me! ©2009 by Network World, Inc. 118 Turnpike Road, Southborough, Massachusetts 01772. Reprinted from Network World. |
PRESS
RELEASES Monday, Feb 8 Another Way to Support Access Compliance
How much security do we need?
IAM can be used in many ways, claims expert
Lieberman Software and Heritage Global Solutions Partner to Deliver Privileged Identity Management Solutions
Gemalto buys mobile authentication firm Valimo
Some still don’t get it!
If you have the same problem for a long time, maybe it is a fact not a problem…
Identification through “Social Pattern Recognition”
AuthenTec Inc. dismisses rival's merger bid; alleges patent infringement
All NHIN identity management is local
SPML Is On Life Support ….
A Project Manager’s Take on Initiating an Identity Management Program
Federated identity graphic (SAML, OpenID, WS-*, more…)
Expanding on the Oracle-Sun IdM Strategy
Internet Banking-Related Security Suit – A Case of Man Bites Dog
The risk of costs
Sun IDM is dead
How to Keep Mobile Cloud Data Safe
Jericho Systems Selected to Provide Attribute-Based Access Control (ABAC) Solution for U.S. Army
Considerations for an Identity Management Initiative in 2010
CertiPath Launches Trusted PACS Service
idOnDemand, ChosenSecurity partner
Oracle and Sun– the Acquisition is Done. What’s Next for IAM?
Access Management: How To Authenticate Users
Microsoft, Novell collaborate on LDAP access to SharePoint
|
© Copyright 2003 - 2009, The Virtual Quill