Penn Information Systems & Computing
September 2019 Update

Consumer IAM (CIAM) Project
The Consumer IAM (CIAM) project is developing a new, cloud-based IAM service for populations who neither need nor want all the access privileges and security requirements associated with a PennKey (e.g., non-traditional learners, research collaborators, business partners, and other external affiliates). The CIAM service will provide an alternative credential for these populations and can be integrated with applications to provide a single sign-on experience. Recent progress includes:
  • The team is excited to announce that the CIAM service has a new Pennified name and logo, which will be used on the login screen:
  • The team has been working with Penn’s Online Learning Initiative (OLI) to integrate PennPath into OLI’s new online platform. PennPath will support OLI’s vision to provide an end-to-end, Penn-branded experience for non-credit online learners. Many thanks to our campus partners – especially Rebecca Stein, Rebecca Cweibel, and Anna Miller from OLI; Molly Bonnard from the Library; and Nicole Auge from SP2 – for their invaluable collaboration throughout the project.
  • PennPath is being prepared for enterprise deployment as an ISC Access Management service offering.
  • If you have any questions about PennPath, please contact us at penn-iam@upenn.edu.
Internal IAM Project 
The Internal IAM project includes a re-engineering of Penn's core IAM infrastructure, replacing 15-year-old, custom-built identity management systems and processes with a standards-based, modern solution to strengthen Penn's overall security posture and ability to comply with emerging global regulatory requirements. The new IAM solution will be implemented in phases. Recent progress includes:
  • This month, the team has begun conducting requirements assessment sessions with the owners of Penn Community components and source systems. The goals are to replace Penn Community with minimal disruption to existing services and to put in place the foundation for future improvements. The team will document opportunities discovered during requirements collection. Opportunities will be explored and evaluated for future releases and will go to a governance body for consideration and priority setting. The meetings with system representatives will inform the requirements in the product request for proposal (RFP) to vendors.
  • Updates will be shared with IT Roundtable as the project progresses.
  • If your group is seeking to deploy new applications in FY20 while Penn’s new IAM infrastructure is being developed and deployed, see the IAM Transition Guidance for New Applications document. If you have any questions, please contact us at penn-iam@upenn.edu.
  • To see the FY20 goals/scope, please visit the project page on the website
Two-Step Verification 
With increased controls like Two-Step Verification, there was a 90% reduction in PennKey compromises in FY19 over our average rate for the prior two years. See the Two-Step impact graphic below for more information (click for larger view):
As the final stage in onboarding campus communities, on Tuesday, October 8, 2019, incoming undergraduate students will be required to enroll in Two-Step Verification. CHAS Technology, the Office of the Provost, and all four undergraduate Schools have approved the following schedule:
  • Monday, September 9: Intercept screen with 30-day countdown begins for incoming undergraduates
  • Tuesday, October 8: Two-Step enforced for incoming undergraduates
Questions & Feedback
ISC values your feedback. If you have questions, comments, or suggestions, please contact penn-iam@upenn.edu.
For the latest developments on the IAM program, please visit the website.
We look forward to sharing more progress with you soon!
The Penn IAM Team
Subscribe to our email list.