• Products & Solutions

• 01 Enterprise Content Management

• 02 Identity Management

• SAM Identity Management Suite

• Solutions

• Automated User Provisioning

• Electronic Request Workflow for User Accounts and Access Rights

• Self-Service Password Reset

• Leveraging automated Provisioning for Application Security

• Implementing Identity Management Solutions

• Role Based Administration

• GAP Analysis Role Modeler

• Saving Log Data for Forensic Analsysis

• 03 Data Center Infrastructure

• 04 4Agility

Situation:
The reasons why management may decide to introduce an Identity Management System for all the IT systems in the company are usually of central strategic importance: The costs of access rights management need to be slashed, and growing demands for security need to be met. In order to attain these goals, processes have to be automated to the greatest possible extent, thus achieving a significantly higher degree of efficiency and transparency. However, experience has shown that projects like this can take a lot of time and money, and they don't always bring the expected results; sometimes they even fail.

Complications:
One of the most difficult problems to overcome is reconciling all the different people, departments and structural units that need to work together. Conflicts of interest are unavoidable, and are complicated even further by the fact that no one in any one department or business unit knows enough about all the others to be able to manage and control the project properly. It very soon becomes clear that Identity Management is not just a matter of implementing relatively complicated software: workflows, procedures and areas of responsibility need to be redefined, and the enormous quantities of data that have built up over the years – all the definitions of rights and security requirements for all the different systems - need to be streamlined and consolidated.

Solution:
To make sure that projects of this type not only stay within the budget but also meet their strategic aims, they must be implemented step by step. Experience has shown that it is not practicable to take every work package at once and attempt to process everything in parallel. Dependencies must be identified and taken into consideration. For example, it's a good idea to start with the access rights procedures that are most important for the organization, and add the other procedures one at a time afterwards. Existing data must be consolidated first; only then can processes be automated or central rule engines implemented.
Years of experience with projects like this have enabled Professional Services personnel from Beta Systems Software AG to develop a procedural model. It's a four-stage model that runs under the headings Consolidate, Automate, Streamline, Manage: tasks and work packages build up on one another in the most rational possible way, thus achieving ROI in the shortest possible time. At the same time, this model is flexible enough to meet the widest variety of requirements from the widest variety of enterprises and organizations.