1 IAM Program Launch - Hitachi ID Systemshitachi-id.com/password-manager/largedocs/presentation-iam... · • Notes • Windows • Unix/Linux. ... (OU) Create/manage ... Operations:
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1 IAM Program Launch
Managing the User LifecycleAcross On-Premises andCloud-Hosted Applications
Kickstart an IAM program with discovery of business and IT requirements
2 Agenda
• Who? Introductions.• Why? Business drivers.• What? Business processes.• Where? Integrated systems.• When? Priorities and timelines.• How? Best practices guidelines.
• System of record (HR)?• SAP• Oracle EBS• PeopleSoft• Vertical• Custom
• VPN• Smart card• Token
• Building/badge• PC/installed image• Desk phone/VoIP• Mobile phone• Full disk encryption
7 Priorities and timelines
7.1 Incremental deployment
• Business processes change.• Infrastructure changes too (application and OS upgrades, etc.).• IAM systems link process to infrastructure• If deployment takes a long time, the delivered system will meet obsolete requirements (pointless).• Conclusion: deliver fast .• There are many possible deliverables.• Conclusion: deliver early and often .
– This is not a new business function – just a better way to do it.– Changing processes and integrations plus complex deliverables mean that implementation will
never end.
• Deliver early and often:
– Increase visibility, credibility.– Deliverables should be backed by metrics.
• Executive sponsorship:
– Motivate stake-holders.– Resolve conflicts.– Engage all stake-holders early.
• Effective project management:
– Phased approach: design/implement/test/rollout - repeat.– Think software development lifecycle (SDLC).– Communicate success, next steps to all stake-holders.