EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Argus: command line usage and banning Christoph Witzig, SWITCH

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Outline Introduction Command line interface Global Banning Summary

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Introduction Institutions involved: –CNAF, HIP, NIKHEF, SWITCH Argus = Attribute-based Authorization service –Attributes = DN, CA, FQAN, …. –Internal engine that determines whether a request containing a set of attributes shall be authorized or not Decisions are taken for a given resource and a given action: –E.g. A WN has a resource id and the action may be “execute_pilot” –Policies are formulated for  Individual resource and action  Groups of resources and groups of action  All resources and all actions Default deployment: all components on a single host Note abbreviation: authZ = authorization

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Service Components Administration Point: Formulating the rules through command line interface and/or file-based input Decision Point: Evaluating a request from a client based on the rules Enforcement Point: Thin client part and server part: all complexity in server part Runtime Execution Environment: Under which env. must I run? (UID, GID) Initial rules: Banning unbanning Pilot job Initial default deployment: All components on one host

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, On the CE

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Proposed Deployment Plan Deployment during EGEE-III Adoption during EGEE-III

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Outline Introduction Command line interface Global Banning Summary

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Argus CLI Argus is operated from the command line Policies either –Added/removed from command line –Import/export of file in simplified policy language (optional!)  see A.Ceccanti’s talk in MWSG Banning and unbanning users Evaluating authZ decisions

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Banning Users To ban a user on the entire site: pap-admin ban subject pap-admin ban fqan To un-ban a user on the entire site: pap-admin un-ban subject pap-admin un-ban fqan To ban a user on a specific resource: pap-admin ban -r resource_id subject

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Evaluating authZ Decisions pepcli -p -c /tmp/x509up_u964 -r res_nok -a my_action Decision: Deny pepcli -p -c /tmp/x509up_u964 -r res_ok -a my_action Decision: Permit Username=testb001 UID=5100 GID=5100 pepcli -p -s -f /switch -f /switch/test -r test -a test Decision: Permit Username=testb002 UID=5101 GID=5100 Secondary GIDs=5300

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Outline Introduction Command line interface Global Banning Summary

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Grid-wide Banning by OSCT OSCT offers centralized banning list to the sites Allows banning for: DN (with or without SN) CA VO FQAN As well as regular expressions of the above Operated (same as for local Argus instance) From the CLI pap-admin ban-user pap-admin ban-fqan Import / export of files in a simplified notation

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Operational Policy Each site manages its own access policies Local site autonomy OSCT operates a central banning service (CBS) Sites SHOULD deploy CBS Sites SHOULD give CBS priority over local policies Sites SHOULD configure CBS so any ban/restore action is active in under 6 hours Time period still under discussion Grid Security Operations MUST inform VO manager whenever user/group access is changed (ban & restore) SHOULD= Obligation with escape clause Inform Grid Security Office. Currently proposed by JSPG Discussions continuing.

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Policy for Global Banning (Full text) Each site manages its own local access policies to its resources. In addition, Grid security operations SHOULD operate a central banning service. Whenever Grid security operations bans a user or group of users, or restores their access, they MUST inform the appropriate VO Manager. Sites SHOULD deploy this central banning service and give it priority over local policies. The site implementation of the central banning service SHOULD be configured such that any ban or restore action made by Grid security operations is active at the site without a delay of more than 6 hours

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Outline Introduction Short Description of the Service Deployment Proposal Global Banning Summary

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Summary Gradual deployment in six self-contained steps Simple CLI for –Banning/unbanning users –Adding/removing policies –Evaluating request for debugging OSCT global banning list Feedback and volunteer from sites / OSCT for trying service out is highly welcome

Enabling Grids for E-sciencE EGEE-II INFSO-RI OSCT/MWSG meeting, EGEE09, Sept 22, Further Information About the service: –authZ service design document: –Deployment plan: General EGEE grid security: –Authorization study: –gLite security: architecture: Other: –Wiki: (under development)