1 / 4

Enhancing Identity Management in Cloud Services: Challenges and Strategies

The difference in cloud services lies in their purpose and scope, like Concur's focus on authentication versus Box's collaboration features. Current identity management systems often fail to provide adequate independent leverage, prioritizing consumer needs while leaving enterprise controls lagging behind. To improve user management, institutions must adopt vendor-provided APIs and ensure automated de-provisioning of accounts. The goal is a campus-hosted system that empowers users with self-provisioning capabilities while maintaining security. Institutions should take charge of credential management, pushing vendors towards better solutions.

wirt
Télécharger la présentation

Enhancing Identity Management in Cloud Services: Challenges and Strategies

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. How is the cloud different? • Depends on service scope/intent • Concur (auth only) versus Box (collaboration/storage) • Existing Identity Management compromises persist • Limited independent leverage • Consumer-centric • Enterprise administrative controls can lag behind

  2. Identity In the Cloud? • Goal: • Campus-hosted system of record for entitled/active services • End-user self-provisioning for all services • Requires: • Vendor-provided user-management APIs • Disabling cloud-based identity management tools • Password change, account name change, etc. • Institution/cloud reconciliation • Automated de-provisioning of cloud accounts • Results in: • Institution is not dependent on cloud providers to know which services affiliates are provisioned for • Attestation capability

  3. How Can You Help? • Spread the message: • Federated authentication • Institutions should manage credentials – not cloud providers • Continue to push vendors in this direction • Account Name does not equal Email Address • All our users have multiple institutional email addresses • We need role-based security • User-centric controls are insufficient for a managed service

  4. Biggest Challenges • Identity Management compromises in favor of end-user features • Vendor maturity • Revoking campus credentials may not revoke access • Identity clean up for consumer-centric services • Affinities • No elegant solution for groups • Define the horizon

More Related