



"Sun Drives New Security Offering." By Dennis Fisher. While such systems easily can hook into Web-based applications, integration with client/server applications likely will require more time-consuming and costly custom integration work." See also the sidebar "Identity Management Tips: Eight Suggestions On How to Implement Identity Management Smoothly." Rowe Price uses IBM Tivoli Access Manager, and CUNA Mutual uses Oblix's NetPoint. A number of vendors, including IBM, Netegrity and Oblix, sell Web access management products that provide authorization. Should the user later want to access other applications, the token can be shuttled around as necessary behind the scenes, so the user doesn't have to log on to each new application. Often some form of software-based security token that denotes the user's credentials is then passed to the application. There the user is properly authenticated, with at least a username and password. Centralized access management can be implemented in a number of ways, but generally, when a user attempts to log on to a Web application, the logon request is routed to the access management engine. With the directory in order, integrating applications can begin. Largely homogeneous organizations might implement an all-encompassing enterprise directory, but it's unlikely you'll ever get down to just one. One option is a metadirectory, which brings a consolidated view of data in various directories in the corporation. For example, the human resources application would be the authoritative source for fiduciary employee records, while Active Directory holds e-mail addresses. Multiple authoritative sources might be associated with the same individual, depending on the data in question. The idea is to have a single 'authoritative source' for each piece of data. Most identity management strategies start with some form of directory services integration, says Kevin Kampman, senior consultant with Burton Group. The goal is to 'understand who you're working with and what they need,' says Joe Duffy, global leader of PricewaterhouseCooper's (PWC) Security and Privacy Practice. Experts agree that the problem is the same whether those individuals are employees, customers or business partners. Ideally, it provides a single view of every individual across IT systems throughout the organization. Identity management involves dealing with individuals in an online world. "You can build it, you can buy it, but you can't escape the need for identity management. "Gaining Perspective On Digital Identities." By Paul Desmond.
