Introduction to the PKI Issues at UW Madison Presented to ITC on Friday, 3/18/2005 Tom Jordan Systems Engineer, DoIT Middleware Group
What is PKI? PKI is Public Key Infrastructure PKI makes communications and data more secure PKI facilitates: aa0377ffee22 9fc23b7623ac 748aa0377ffe e229fc23b762 3ac7 Data Encryption Secure Messaging Stronger Authentication Encrypted Communications
Closely related to PKI Token Authentication Smart Cards Multifactor Authentication Digital Signatures Electronic Workflow SSL Secure Data Transmission Single signon / reduced signon
Why PKI? What’s wrong with what we’ve got? –Username and password authentication –Lots of cleartext messaging –Little secure workflow –Lots of data vulnerable in transit and at rest Existing systems adequate for some things, not for others Many tactical problems that would benefit from a strategic effort
What does it mean to have an infrastructure? Address tactical problems piecemeal vs. defining a strategic direction Commonality enables interoperability
How are other folks using PKI? University of Texas HSC, Houston –10,000 users doing document signing and electronic workflow –5 years in production Dartmouth –8,000 users using PKI for VPN authentication –2 years in production University of Texas, Galveston –13,000 users of secure –3 years pilot, 6 months production University of Alabama, Birmingham –30,000 users of enterprise authentication system –3 years in production University of Virginia –30,000 users of secure –2 years in production Minnesota – token authentication for administrative users Penn State – not PKI per se, but heavy into data encryption
How do folks here want to use PKI? State Lab of Hygiene –Business & Research –Local data encryption Office of the Registrar –Stronger authentication for course enrollment –Digitally signed transcript requests Computer Science –Identification and Authorization for Grid Computing Graduate School –FastLane Grant submission DoIT –More secure access to server / datacenter environs –Secure support in WiscMail –Security for Web Services / SOA / Distributed Computing –Multifactor Institutional Authentication
Why now? Regulatory pressures –Secure communications –Data encryption Peer Institution Exploits Trends towards interoperability –Integrated applications –SOA / Distributed Computing Window of adoption – where do we need to be in 3-5 years? Budgetary pressure to find common solutions
What will it take? Strategic Planning Policy Work Process Work Technical Planning & Implementation Adoption & adaptation
Questions? -----BEGIN PUBLIC KEY----- MIGfMA0GCSqGSIb3DQEBAQUAA4GNAD CBiQKBgQC5eD8plw5d8s8qA6BgfVsu N2G+TSdlmDLNugx510ehFOeLID+3dW 0Y9WDzSwMyRcTez2DzTLg5YusaGJEa vleImO1qi1UZONOTPNp5xFcejXCwfz W8AzYmXZy53kx1Ff3xTOJyoIFdZtec 9oaTN711pYTTIuhDv2Xn2uM0eYOjIQ IDAQAB -----END PUBLIC KEY-----