1. Grid Security Overview The Globus Project™ http://www.globus.org/ Copyright (c) 2002 University of Chicago and The University of Southern California. All Rights Reserved. This presentation is licensed for use under the terms of the Globus Toolkit Public License. See http://www.globus.org/toolkit/download/license.html for the full text of this license.

2. Grid School 2004Security Overview2 Security Terminology l Authentication: Establishing identity l Authorization: Establishing rights l Message protection –Message integrity –Message confidentiality l Non-repudiation l Digital signature l Accounting l Delegation

3. Grid School 2004Security Overview3 Trust Mismatch Mechanism Mismatch Multi-Institution Issues Certification Authority Certification Authority Domain A Server X Server Y Policy Authority Policy Authority Task Domain B Sub-Domain A1 Sub-Domain B1 No Cross- Domain Trust

4. Grid School 2004Security Overview4 Why Grid Security is Hard l Resources being used may be valuable & the problems being solved sensitive –Both users and resources need to be careful l Dynamic formation and management of virtual organizations (VOs) –Large, dynamic, unpredictable… l VO Resources and users are often located in distinct administrative domains –Can’t assume cross-organizational trust agreements –Different mechanisms & credentials >X.509 vs Kerberos, SSL vs GSSAPI, X.509 vs. X.509 (different domains), >X.509 attribute certs vs SAML assertions

5. Grid School 2004Security Overview5 Why Grid Security is Hard… l Interactions are not just client/server, but service-to-service on behalf of the user –Requires delegation of rights by user to service –Services may be dynamically instantiated l Standardization of interfaces to allow for discovery, negotiation and use l Implementation must be broadly available & applicable –Standard, well-tested, well-understood protocols; integrated with wide variety of tools l Policy from sites, VO, users need to be combined –Varying formats l Want to hide as much as possible from applications!

6. Grid School 2004Security Overview6 The Grid Trust solution l Instead of setting up trust relationships at the organizational level (lots of overhead, possible legalities - expensive!) set up trust at the user/resource level l Virtual Organizations (VOs) for multi-user collaborations –Federate through mutually trusted services –Local policy authorities rule l Users able to set up dynamic trust domains –Personal collection of resources working together based on trust of user

7. Grid School 2004Security Overview7 Grid Solution: Use Virtual Organization as Bridge Certification Domain A GSI Certification Authority Sub-Domain B1 Authority Federation Service Virtual Organization Domain No Cross- Domain Trust

8. Grid School 2004Security Overview8 Effective Policy Governing Access Within A Collaboration

9. Grid School 2004Security Overview9 Use Delegation to Establish Dynamic Distributed System Compute Center VO Rights Compute Center Service

10. Grid School 2004Security Overview10 Goal is to do this with arbitrary mechanisms Compute Center VO Rights Compute Center Service Kerberos/ WS-Security X.509/SSL SAML Attribute X.509 AC SAML Attribute X.509 AC

11. Grid School 2004Security Overview11 Grid Security Infrastructure (GSI) l Use GSI as a standard mechanism for bridging disparate security mechanisms –Doesn’t solve trust problem, but now things talk same protocol and understand each other’s identity credentials –Basic support for delegation, policy distribution l Translate from other mechanisms to/from GSI as needed l Convert from GSI identity to local identity for authorization

12. Grid School 2004Security Overview12 GSI l GSI implements X.509 Proxy Certificates as extensions to these standards to support dynamic naming of services, delegation of rights and single sign-on l After authentication, GSI identity is mapped by administer configuration to a local identity for authorization. –Local identity controls access to local files, job startup rights, etc.

13. Grid School 2004Security Overview13 Grid Security Infrastructure (GSI) l Based on standard PKI technologies –SSL protocol for authentication, message protection –CAs allow one-way, light-weight trust relationships (not just site-to-site) l X.509 Certificates for asserting identity –for users, services, hosts, etc. l Proxy Certificates –GSI extension to X.509 certificates for delegation, single sign-on

14. Grid School 2004Security Overview14 Grid Security Infrastructure (GSI) l GSI is: PKI (CAs and Certificates) SSL/ TLS Proxies and Delegation PKI for credentials SSL for Authentication And message protection Proxies and delegation (GSI Extensions) for secure single Sign-on

15. Grid School 2004Security Overview15 Grid Identity, Local Policy Local Policy Map to local name Grid Identity In current model, all Grid entities assigned a PKI identity. User is mapped to local identities to determine local policy..

16. Grid School 2004Security Overview16 Local Identity, Grid Identity, Local Policy Local Policy Map to local name Grid Identity Kerberos Site KCA SSLK5 KRB5 Resources

17. Grid School 2004Security Overview17 GSI Implementation Compute Center VO Rights VO Users Services (running on user’s behalf) Rights’’ Rights’ Access Local Policy on VO identity or attribute authority CAS or VOMS issuing SAML or X.509 ACs SSL/WS-Security with Proxy Certificates Authz Callout KCA MyProxy

18. Grid School 2004Security Overview18 Public Key Infrastructure (PKI) l PKI allows you to know that a given key belongs to a given user l PKI builds off of asymmetric encryption: –Each entity has two keys: public and private –Data encrypted with one key can only be decrypted with other. –The public key is public –The private key is known only to the entity l The public key is given to the world encapsulated in a X.509 certificate Owner

19. Grid School 2004Security Overview19 John Doe 755 E. Woodlawn Urbana IL 61801 BD 08-06-65 Male 6’0” 200lbs GRN Eyes State of Illinois Seal Certificates l Similar to passport or driver’s license: Identity signed by a trusted party Name Issuer Public Key Signature

20. Grid School 2004Security Overview20 Certificates l By checking the signature, one can determine that a public key belongs to a given user. Name Issuer Public Key Signature Hash =? Decrypt Public Key from Issuer

21. Grid School 2004Security Overview21 Certificate Authorities (CAs) l A small set of trusted entities known as Certificate Authorities (CAs) are established to sign certificates l A Certificate Authority is an entity that exists only to sign user certificates l The CA signs it’s own certificate which is distributed in a trusted manner Name: CA Issuer: CA CA’s Public Key CA’s Signature

22. Grid School 2004Security Overview22 Certificate Authorities (CAs) l The public key from the CA certificate can then be used to verify other certificates Name Issuer: CA Public Key Signature Hash =? Decrypt Name: CA Issuer: CA CA’s Public Key CA’s Signature CA

23. Grid School 2004Security Overview23 Certificate Request Private Key encrypted on local disk Cert Request Public Key ID Cert User generates public/private key pair. User send public key to CA along with proof of identity. CA confirms identity, signs certificate and sends back to user.

24. Grid School 2004Security Overview24 X.509 Proxy Certificates l GSI Extension to X.509 Identity Certificates –RFC l Enables single sign-on l Allow user to dynamically assign identity and rights to service –Can name services created on the fly and give them rights (i.e. set policy) l What is effectively happening is the user is creating their own trust domain of services –Services trust each other with user acting as the trust root

25. Grid School 2004Security Overview25 Proxy Certificates Service CN=Jane Doe/9874 Rights: Can access file F1, Service S1, … CN=Jane Doe X.509 Proxy Delegation S1 F1 Use delegated rights to access resources. X.509 Id certificate X.509 Proxy certificate Create

26. Grid School 2004Security Overview26 Obtaining a Certificate l The program grid-cert-request is used to create a public/private key pair and unsigned certificate in ~/.globus/: –usercert_request.pem: Unsigned certificate file –userkey.pem: Encrypted private key file >Must be readable only by the owner l Mail usercert_request.pem to ca@globus.org l Receive a Globus-signed certificate Place in ~/.globus/usercert.pem l Other organizations use different approaches –NCSA, NPACI, NASA, etc. have their own CA

27. Grid School 2004Security Overview27 Certificate Information l To get cert information run grid-cert-info % grid-cert-info -subject /C=US/O=Globus/O=ANL/OU=MCS/CN=Ian Foster l Options for printing cert information -all-startdate -subject-enddate -issuer-help

28. Grid School 2004Security Overview28 “Logging on” to the Grid l To run programs, authenticate to Globus: % grid-proxy-init Enter PEM pass phrase: ****** l Creates a temporary, local, short-lived proxy credential for use by our computations l Options for grid-proxy-init: -hours -bits -help

29. Grid School 2004Security Overview29 grid-proxy-init Details l grid-proxy-init creates the local proxy file. l User enters pass phrase, which is used to decrypt private key. l Private key is used to sign a proxy certificate with its own, new public/private key pair. –User’s private key not exposed after proxy has been signed l Proxy placed in /tmp, read-only by user l NOTE: No network traffic! l grid-proxy-info displays proxy details

30. Grid School 2004Security Overview30 Grid Sign-On With grid-proxy-init User certificate file Private Key (Encrypted) Pass Phrase User Proxy certificate file

31. Grid School 2004Security Overview31 Destroying Your Proxy (logout) l To destroy your local proxy that was created by grid-proxy-init: % grid-proxy-destroy l This does NOT destroy any proxies that were delegated from this proxy. –You cannot revoke a remote proxy –Usually create proxies with short lifetimes

32. Grid School 2004Security Overview32 Proxy Information l To get proxy information run grid-proxy-info % grid-proxy-info -subject /C=US/O=Globus/O=ANL/OU=MCS/CN=Ian Foster l Options for printing proxy information -subject-issuer -type-timeleft -strength-help l Options for scripting proxy queries -exists -hours -exists -bits –Returns 0 status for true, 1 for false:

33. Grid School 2004Security Overview33 Delegation l Delegation = remote creation of a (second level) proxy credential –New key pair generated remotely on server –Proxy cert and public key sent to client –Clients signs proxy cert and returns it –Server (usually) puts proxy in /tmp l Allows remote process to authenticate on behalf of the user –Remote process “impersonates” the user

34. Grid School 2004Security Overview34 Limited Proxy l During delegation, the client can elect to delegate only a “limited proxy”, rather than a “full” proxy –GRAM (job submission) client does this l Each service decides whether it will allow authentication with a limited proxy –Job manager service requires a full proxy –GridFTP server allows either full or limited proxy to be used

35. Grid School 2004Security Overview35 Secure Services l On most unix machines, inetd listens for incoming service connections and passes connections to daemons for processing. l On Grid servers, the gatekeeper securely performs the same function for many services –It handles mutual authentication using files in /etc/grid-security –It maps to local users via the gridmap file

36. Grid School 2004Security Overview36 Sample Gridmap File # Distinguished name Local # username "/C=US/O=Globus/O=NPACI/OU=SDSC/CN=Rich Gallup” rpg "/C=US/O=Globus/O=NPACI/OU=SDSC/CN=Richard Frost” frost "/C=US/O=Globus/O=USC/OU=ISI/CN=Carl Kesselman” u14543 "/C=US/O=Globus/O=ANL/OU=MCS/CN=Ian Foster” itf l Gridmap file maintained by Globus administrator l Entry maps Grid-id into local user name(s)

37. Grid School 2004Security Overview37 Authorization l GSI handles authentication, but authorization is a separate issue l Authorization issues: –Management of authorization on a multi-organization grid is still an interesting problem. –The grid-mapfile doesn’t scale well, and works only at the resource level, not the collective level. –Large communities that share resources exacerbates authorization issues, which has led us to CAS…

38. Grid School 2004Security Overview38 Security Summary l Programs for credential management –grid-cert-info, grid-proxy-init, grid-proxy- destroy, grid-proxy-info l GSS-API: The Globus Toolkit Grid Security Infrastructure (GSI) uses this API, which allows programs to easily add security l globus_gss_assist: This is a simple wrapper around GSS-API, making it easier to use