1. CIFER Community Identity Framework for Education and Research (CIFERproject.org) An agile, best-of-breed, community-governed, comprehensive IAM solution for higher education

2. IAM in university environments Which people? What systems & business processes? What policies? What purposes? Whose authority? It’s complicated! April 20122

3. Context IAM is 5% of all higher education IT expenditures. (sources: Gartner/Forrester, 2010-2011) IAM investment currently earns substantially below-average ROI and under-serves the four key higher-ed missions These problems are pervasive: all campuses suffer Financial Situation OSS IAM would substantially reduce operating costs and improve ROI. Key portions of the open-licensed IAM solution are mostly complete, but needs final-push investment in order to fully meet diverse HE needs Open-licensed vendors are ready and willing to serve The timing of this opportunity is important A Strategic Opportunity—especially in difficult times 3

4. CIFER Objectives Builds upon existing open source IAM projects Creates a comprehensive, modular IAM stack Implements open, standards-based architecture Reduces ops costs (TCO) through improved integration, automation, QA Focuses on needs, challenges distinctive to HE Avoids vendor lock-in 4ciferproject.org

5. CIFER Principles 5 Research and teaching-oriented campuses; 4-year and 2-year; public and private “Consortia Organizations” (COs), including research collaboratives and learned societies, as well as Internet2, Jasig, Kuali, other OSS projects, etc. Serve all of higher education Full scope of teaching, learning, research, and service missions Universal and HE-specific policies and risks, cloud services, and threats HE-specific distributed management On large and small campuses and multi-campus systems alike Support distinctive, education-specific needs As a matter of principle: open governance by-and-for HE, as well as open licensing As a matter of pragmatics: keep costs down, mitigate risks, etc. Openness

6. CIFER Strategy 6 Reduce the costs, reduce the risks, and improve the quality of IAM available to any US campus Improve creation, diffusion of IAM best-practices using proven collaborative models, practices Create a healthy, sustainable community, with a healthy vendor-support market, to serve us well Pool community resources to deliver open-licensed IAM technologies Reduce operating costs and risks by filling urgent functional gaps (e.g., person-registry) Enhance campus agility, productivity by sharply improving process-automation for monitoring, reporting, compliance, and audit (e.g., unified management console) Enhance ROI through coordinated governance, collaborative innovation going forward Implement a proven sustainability model, to ensure ROI indefinitely Build out a comprehensive, agile, open-licensed IAM stack Collaborative teaching, learning, research, and service Social and mobile applications (in teaching, learning, research, and service) The “cloud”—and especially the higher education cloud (e.g., for-profit enterprise SaaS offerings—but also Net+, DuraSpace, etc.) Target higher education’s particular IAM priorities, pain-points

7. CIFER Scope DRAFT: NOT FOR CIRCULATION7 IAM Console (monitor, audit, reporting, etc.) Identity Registries Provisioning/Integration Other IAM Components “No Reinvention Zone” (Middleware like ServiceMix, Jboss, etc. Directories like LDAP, AD, etc.) Access ManagementAuthentication Systems of Record (e.g. HR, SIS, etc.) Target Systems (e.g. LMS, Cloud Apps) Quality Assurance = In Scope, 5 Workstreams plus overall QA = Out of Scope, needs no new investment

8. Launching CIFER Pre-Launch (Underway) – Demonstrate value to community, investors – Solidify commitments Investment (Leadership, Support, & Participation) Deployment commitments Launch (upon completion of pre-launch targets) – Media releases by projects, investors, and participants – Professional education (conference presentations, etc.) – Additional investment by new participants – Vendor participation and effort 8ciferproject.org

9. CIFER Roadmap Timeline & Highlights 9 Collaboration and support continues Coordinated and focused work begins CAS and Shibboleth both well established authentication platforms, encourage conformity Today - Existing products deliver immediate value Identity registry with identity matching (largest, most ubiquitous gap; KIM, OpenReg, Penn St code possible options; encourage convergence) Encourage integration and standardization of key access management projects (e.g., KIM & Grouper) Provisioning/Integration connectors to major commercial apps (ERP, LMS, email, etc.); community contribution begins Instrumentation and integration across components begins; beta version of IAM management console Year 1 - Full features & QA; integration & instrumentation begins Full suite of provisioning/integration connectors to systems of record and enterprise apps—many contributed by community Full process automation and IAM management console, for provisioning, integration, compliance, access management, reporting, etc. Year 2 - Comprehensive, best-of-breed solution

10. CIFER ROI 10 Swap out high-cost vendor components Reduce high-maintenance “glue” code Reduce ops, helpdesk effort Fair-cost vendor availability gives management more and better choices Today - Provide immediate functional and economic wins Complete stack ends license fees, replaces high-maintenance self-build components Process automation, console further reduce ops costs Community sustaining model sharply reduces campus share of maintenance costs Year 1 - Accelerates ROI Full stack, with full process-automation for monitoring, reporting, compliance, and audit Comprehensively cloud-serving, and ready for cloud-based delivery as well Year 2 - Transforms the possibilities

11. CIFER Investment Options Monetary Investment: – Participant Campuses $1/student/year (2 years); Others $50k – Supporter Campuses $2/student/year (2 years); Others $100k – Leader Campuses $5/student/year (2 years); Others $250k – Work Stream-specific investment option as well FTE Resources (in-kind contribution) Code (IP) 11ciferproject.org

12. Why Commit to Invest in CIFER? Higher-ROI, Lower-TCO, lower-risk IAM: sooner, better, and sustainably Prepares us better for HE-specific challenges like collaboration, social/mobile, and the cloud Community governance improves our institutional control over our own destiny Modular solution means no non-core investment Diverse investment options let us tailor our investment precisely to our institutional priorities Vendors available for immediate support, ROI Validates and advances our institutional stature 12ciferproject.org

13. Communications Plan 13 Leaders Announced Terms of Participation Statements of support Announcements on general HE (Chronicle, Inside Higher Ed) and tech-specific (EDUCAUSE CIOs list) media Public Launch Other Leaders, Participants, and Supporters sign on Commercial affiliates sign on InCommon signs on Team members speak at various professional meetings, etc. Participants solicit participation from peers Follow-up Publicity Separate from (but linked to) technical web presence Pledge-point for campus contributions Information aggregator, to create, sustain ongoing project momentum Project Public Website

14. What’s Needed? 14 Your campus Through your preferred CO Early pledges are particularly important, to motivate others Invest! What are your campus IAM needs? How does your campus find the funds? Others will need examples, as well as inspiration Educate: Help us make the case to the HE community Urge peers to invest Mobilize COs of which you’re a member Keep the project in people’s minds Motivate

15. Questions? 15 For More Information contact : info@ciferproject.org