1 / 9

Identity & Access Management (IAM)

Identity & Access Management (IAM). Update for the Committee on Technology and Architecture. Current Environment Problematic. Inconvenient and complex for users Significant application overhead Enterprise inefficiencies Increased risk exposures. Components: Identity Access Data.

Download Presentation

Identity & Access Management (IAM)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Identity & Access Management (IAM) Update for the Committee on Technology and Architecture

  2. Current Environment Problematic • Inconvenient and complex for users • Significant application overhead • Enterprise inefficiencies • Increased risk exposures Components: IdentityAccessData

  3. Near-term IAM Plan Enhance MyAccess • Establish production-level service • Introduction of application list feature • Bring new applications on board IAM Strategy & Roadmap • Establish committee (members, vision, scope) • Inventory and map current IAM ecosystem • Establish plan for unified logon (Phase 1) • Define business requirements • SSO and directory system(s) • Data scrubbing and population requirements

  4. FY11-12 IAM Proposed Plan MyAccess – grow service • Enable most UCSF users • Increase number of supported applications • Establish usage policy Execute unified logon plan (Phase 1) • Implement technical infrastructure • Migrate applications to new infrastructure • Establish governance policies and procedures Establish data management plan (Phase 2) • Define data owners, requirements, and policies • Evaluate existing systems • Define architecture and implementation plan

  5. The new MyAccessWebsite: • Lists all applications that have been enabled for Single Sign-On so far. • Provides users with the ease of a single ID and password for multiple applications. • Enables users to access multiple applications with just one login. • Enables users to reset their own passwords (self-service features).

  6. Single Sign-On Login

  7. Application List

  8. MyAccess Snapshot Branding for Identity Management service

  9. Thank You Tom Manessis Thomas.Manessis@ucsf.edu Reba Brindley Reba.Brindley@ucsf.edu

More Related