Difference between revisions of "SPG:Drafts:Security Policy"

From EGIWiki
Jump to: navigation, search
Line 21: Line 21:
 
*''<span style="color: windowtext;">Site management</span>''<span style="color: windowtext;"> is the collection of various individuals and groups mandated to oversee and control a ''site''.</span>  
 
*''<span style="color: windowtext;">Site management</span>''<span style="color: windowtext;"> is the collection of various individuals and groups mandated to oversee and control a ''site''.</span>  
 
*A ''resource administrator'' is the person responsible for installing, operating, maintaining and supporting one or more ''resource(s)'' at a ''site''.
 
*A ''resource administrator'' is the person responsible for installing, operating, maintaining and supporting one or more ''resource(s)'' at a ''site''.
<div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.2''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Objectives''</font>'''</div><div style="margin: 2pt 0cm;">This ''policy'' gives authority for actions which may be carried out by certain individuals and bodies and places responsibilities on all ''participants''.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.3''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Scope''</font>'''</div><div style="margin: 2pt 0cm;">This ''policy''applies to all ''participants''.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Every ''site'' participating in the ''Grid'' autonomously owns and follows their own local security policies with respect to the system administration and networking of all the ''resources'' they own, including ''resources'' which are part of the ''Grid''.&nbsp;This ''policy'' augments local policies by setting out additional ''Grid''-specific requirements.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.4''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Additional Policy Documents''</font>'''</div><div style="margin: 0cm 0cm 12pt;"><span style="font-size: 11pt;">Appendix 1 defines additional policy documents which must exist for a proper implementation of this ''policy''. These documents are referred to in section 2. </span></div><div style="margin: 0cm 0cm 12pt;"><span style="font-size: 11pt;">An accompanying document for each ''Grid'' adopting this ''policy'' must define the ''Grid-''specific locations and version numbers of their approved and adopted additional policy documents.</span></div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.5''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Ownership and Maintenance''</font>'''</div><div style="margin: 2pt 0cm;">This ''policy'' is prepared and maintained by the Security Policy Group, approved by ''management'' and thereby endorsed and adopted by the ''Grid'' as a whole.&nbsp;</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">This ''policy'' will be revised by the Security Policy Group as required and resubmitted for formal approval and adoption whenever significant changes are needed. </div><div style="margin: 2pt 0cm;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">The most recently approved version of this document is available at [https://documents.egi.eu/document/86 <font color="#0000ff">https://documents.egi.eu/document/86</font>]</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">2</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Roles and Responsibilities</font></font>'''</div><div style="margin: 2pt 0cm;">This section defines the roles and responsibilities of ''participants''.</div><div style="margin: 2pt 0cm;"></div><div style="margin: 2pt 0cm;">Participants must be uniquely identifiable and the&nbsp;binding of&nbsp;identifiers to participants&nbsp;must be persistent, i.e. no name recycling.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.1''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>''<span>The IT&nbsp;Organisation</span>''</span></font>'''</div><div style="margin: 2pt 0cm;">The''IT&nbsp;Organisation ''provides, through the adoption of this ''policy'' and through its representations on the various approving bodies of the ''IT&nbsp;Infrastructure'', the overall authority for the decisions and actions resulting from this ''policy ''including procedures for the resolution of disputes.</div>
+
<div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.2''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Objectives''</font>'''</div><div style="margin: 2pt 0cm;">This ''policy'' gives authority for actions which may be carried out by certain individuals and bodies and places responsibilities on all ''participants''.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.3''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Scope''</font>'''</div><div style="margin: 2pt 0cm;">This ''policy''applies to all ''participants''.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Every ''site'' participating in the ''Grid'' autonomously owns and follows their own local security policies with respect to the system administration and networking of all the ''resources'' they own, including ''resources'' which are part of the ''Grid''.&nbsp;This ''policy'' augments local policies by setting out additional ''Grid''-specific requirements.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.4''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Additional Policy Documents''</font>'''</div><div style="margin: 0cm 0cm 12pt;"><span style="font-size: 11pt;">Appendix 1 defines additional policy documents which must exist for a proper implementation of this ''policy''. These documents are referred to in section 2. </span></div><div style="margin: 0cm 0cm 12pt;"><span style="font-size: 11pt;">An accompanying document for each ''Grid'' adopting this ''policy'' must define the ''Grid-''specific locations and version numbers of their approved and adopted additional policy documents.</span></div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''1.5''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Ownership and Maintenance''</font>'''</div><div style="margin: 2pt 0cm;">This ''policy'' is prepared and maintained by the Security Policy Group, approved by ''management'' and thereby endorsed and adopted by the ''Grid'' as a whole.&nbsp;</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">This ''policy'' will be revised by the Security Policy Group as required and resubmitted for formal approval and adoption whenever significant changes are needed. </div><div style="margin: 2pt 0cm;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">The most recently approved version of this document is available at [https://documents.egi.eu/document/86 <font color="#0000ff">https://documents.egi.eu/document/86</font>]</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">2</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Roles and Responsibilities</font></font>'''</div><div style="margin: 2pt 0cm;">This section defines the roles and responsibilities of ''participants''.</div><div style="margin: 2pt 0cm;"></div><div style="margin: 2pt 0cm;">Participants must be uniquely identifiable and the&nbsp;binding of&nbsp;identifiers to participants&nbsp;must be persistent, i.e. no name recycling.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.1''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>''<span>The IT&nbsp;Organisation</span>''</span></font>'''</div><div style="margin: 2pt 0cm;">The''IT&nbsp;Organisation ''provides, through the adoption of this ''policy'' and through its representations on the various approving bodies of the ''IT&nbsp;Infrastructure'', the overall authority for the decisions and actions resulting from this ''policy ''including procedures for the resolution of disputes.</div>  
= '''<font size="5"><span>''2.1.1''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>''<span> The IT </span>''</span>''Security Officer and the CSIRT''</font>''' =
+
= '''<font size="5"><span>''2.1.1''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>''<span> The IT </span>''</span>''Security Officer and the CSIRT''</font>''' =
 
<div style="margin: 2pt 0cm;">The''IT&nbsp;Organisation ''must appoint a IT Security Officer who leads and/or coordinates the ''CSIRT'' providing the operational security capability.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The IT Security Officer may, in consultation with the CSIRT, IT&nbsp;Organisation and other appropriate persons, require actions by ''participants'' as are deemed necessary to protect ''resources'' from or contain the spread of IT security incidents. The IT Security Officer also handles requests for exceptions to this ''policy'' as described in section 5</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The responsibilities of Grid Security Operations include:</div>  
 
<div style="margin: 2pt 0cm;">The''IT&nbsp;Organisation ''must appoint a IT Security Officer who leads and/or coordinates the ''CSIRT'' providing the operational security capability.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The IT Security Officer may, in consultation with the CSIRT, IT&nbsp;Organisation and other appropriate persons, require actions by ''participants'' as are deemed necessary to protect ''resources'' from or contain the spread of IT security incidents. The IT Security Officer also handles requests for exceptions to this ''policy'' as described in section 5</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The responsibilities of Grid Security Operations include:</div>  
 
*The maintenance of contact details of security personnel at each participating ''site'' and the facilitation of ''Grid''-related communications between them.  
 
*The maintenance of contact details of security personnel at each participating ''site'' and the facilitation of ''Grid''-related communications between them.  
 
*Handling of operational security problems as they arise.  
 
*Handling of operational security problems as they arise.  
 
*Providing incident response teams who will act according to the Security Incident Response Policy [6].
 
*Providing incident response teams who will act according to the Security Incident Response Policy [6].
<div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.3''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Virtual Organisation Management''</font>'''</div><div style="margin: 2pt 0cm;">The responsibilities of the ''VO management'' include:</div><div style="margin: 2pt 0cm;">2.3.0&nbsp;&nbsp; Appoint a Security Officer or ensure that they have a security incident response capability</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>VO Security Policies</font>'''</div><div style="margin: 2pt 0cm;">''VOs'' are required to abide by the Virtual Organisation Operations Policy [9] and the Virtual Organisation Registration Security Policy [2]. They must have a VO Acceptable Use Policy (AUP) and ensure that only individuals who have agreed to abide by the Grid AUP [1] and the VO AUP are registered as members of the ''VO''.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.2<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>User Registration and VO Membership Service</font>'''</div><div style="margin: 2pt 0cm;">The ''user'' registration procedure of the ''VO'' is required to be consistent with the Virtual Organisation Membership Management Policy [8]. Approval to join the ''VO'' must be restricted to individuals who are recognised as having legitimate rights to membership and who agree to be bound by the AUPs.&nbsp;A VO membership service must be provided with appropriate interfaces to generate authentication, authorization and other identity mapping data for the services running on the ''sites''. ''VO''s are required to maintain the accuracy of the information held and published about their members, and to promptly remove individuals who lose their right to such membership.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.3<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>VO-specific Resources and Services</font>'''</div><div style="margin: 2pt 0cm;">''VO''s are responsible for ensuring that their ''software'' does not pose security threats, that access to their databases is secure and is sufficiently monitored, that their stored ''data ''are compliant with legal requirements, and that VO-specific ''services'' are properly monitored and do not compromise ''sites'' or ''resources''.&nbsp; Need to refer to Service Operations policy...&nbsp; ALso VO&nbsp;Portal policy ... Also their client actions towards other participants.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.4<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Applying Sanctions to Users</font>'''</div><div style="margin: 2pt 0cm;">''VOs'' are responsible for promptly investigating reports of ''users'' failing to comply with the AUPs and for taking appropriate action to ensure compliance in the future, as defined in section 6.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.4''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Users''</font>'''</div><div style="margin: 2pt 0cm;">All ''users'' must be members of one of the registered ''VOs'' or application communities.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The responsibilities of ''users'' include:</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.4.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Acceptable Use</font>'''</div><div style="margin: 2pt 0cm;">''Users'' must accept and agree to abide by the Grid Acceptable Use Policy [1] and the VO AUP when they register or renew their registration with a ''VO''. </div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' must be aware that their work may utilise shared resources and may therefore affect the work of others.&nbsp;They must show responsibility, consideration and respect towards other ''users'' in the demands they place on the ''Grid''.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' must have a suitable authentication credential issued as approved by the ''Grid''. They must ensure that others cannot use their credentials to masquerade as them or usurp their access rights.&nbsp;''Users'' may be held responsible for all actions taken using their credentials, whether carried out personally or not.&nbsp;No intentional sharing of credentials for ''Grid'' purposes is permitted.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' must be aware that their jobs will often use ''resources ''owned by others.&nbsp;They must observe any restrictions on access to ''resources'' that they encounter and must not attempt to circumvent such restrictions.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Application software written or selected by ''users'' for execution on ''resources'' must be directed exclusively to the legitimate purposes of their ''VO''.&nbsp;Such software must respect the autonomy and privacy of the host ''sites'' on whose ''resources'' it may run.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.5''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span>''<span><span>Resource Centre</span></span>&nbsp;''''Management''</font>'''</div><div style="margin: 2pt 0cm;">The responsibilities of the ''Site management'' include:</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.5.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Site Operations Policy</font>'''</div><div style="margin: 2pt 0cm;">''Sites'' hosting ''resources ''are required to provide reliable and well managed ''services'' and abide by the Grid Site Operations Policy [3]. ''Sites'' must abide by the Site Registration Security Policy [7] and the Grid Security Traceability and Logging Policy [5].</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.5.2<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Mitigating Risks</font>'''</div><div style="margin: 2pt 0cm;">''Sites'' acknowledge that participating in the ''Grid'' increases the risk from security incidents, to both</div><div style="margin: 2pt 0cm;">''Grid'' and non-''Grid'' hosts on each site.&nbsp;''Sites'' are responsible for mitigating this risk.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.5.3<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Incident Response</font>'''</div><div style="margin: 2pt 0cm;">''Sites ''accept the duty to cooperate with Grid Security Operations and others in investigating and resolving security incidents, and to take responsible action as necessary to safeguard ''resources'' during an incident in accordance with the Security Incident Response Policy [6]. </div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.5.4<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Access Control</font>'''</div><div style="margin: 2pt 0cm;">Access to all ''resources'' is controlled by a common grid security infrastructure which includes both authentication and authorization components. The global components of this infrastructure, e.g. as specified in the Approval of Certification Authorities [4], must be deployed by all ''sites'' and ''resources''. The deployment of additional local security measures is permitted should the local security policies of the site or resource administration require this.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.5.5<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Notification of Legal Compliance Issues</font>'''</div><div style="margin: 2pt 0cm;">If exceptions or extensions to this ''policy'' are required because of local legislation, the ''site'' must inform the Grid Security Officer(see section 5).</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.6''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Resource Centre Administrators''</font>'''</div><div style="margin: 2pt 0cm;">In addition to their local site policy ''resource centre administrators'' must ensure their implementations of ''services'' comply with this ''policy''. </div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The responsibilities of ''resource centre&nbsp;administrators'' include:</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.6.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Notifying Site Personnel</font>'''</div><div style="margin: 2pt 0cm;">''Resource administrators'' are responsible for ensuring that their ''site ''is registered with the ''Grid'' and that all appropriate personnel concerned with security or system management at their ''site'' are notified of and accept the requirements of this ''policy'' before offering any ''services''.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.6.2<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Resource Administration</font>'''</div><div style="margin: 2pt 0cm;">The ''resource administrators'' are responsible for the installation and maintenance of ''resources'' assigned to them, including the ongoing security and integrity.</div><div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">3</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Physical Security</font></font>'''</div><div style="margin: 2pt 0cm;">All the requirements for the physical security of ''resources'' are expected to be adequately covered by each ''site’s'' local security policies and practices.&nbsp;These should, as a minimum, reduce the risks from intruders, fire, flood, power failure, equipment failure and environmental hazards.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Stronger physical security may be required for equipment used to provide certain critical ''services'' such as VO membership services or credential repositories.&nbsp;The technical details of such additional requirements are contained in the procedures for operating and approving such ''services''.</div><div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">4</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Network Security</font></font>'''</div><div style="margin: 2pt 0cm;">All the requirements for the networking security of ''resources'' are expected to be adequately covered by each ''site’s'' local security policies and practices.&nbsp;These should, as a minimum, reduce the risks from intruders and failures of hardware or software by implementing appropriate firewall protection, by the timely application of all critical security-related software patches and updates, and by maintaining and observing clearly defined incident response procedures.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">It is ''Grid ''policy to minimise the security risk exposed by applications which need to communicate across the Internet; even so, the peripheral firewall on every participating ''site ''may be required to permit the transit of inbound and outbound packets to/from certain port numbers between a number of external and internal hosts in order to run or reach ''services''.</div><div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">5</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Limits to Compliance</font></font>'''</div><div style="margin: 2pt 0cm;">Exceptions to compliance with this ''policy'' include, but are not limited to, the following:</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Wherever possible, ''Grid'' policies and procedures are designed so that they may be applied uniformly across all ''sites ''and''VOs.'' If this is not possible, for example due to legal or contractual obligations, exceptions may be made.&nbsp;Such exceptions must be justified in a document submitted to the Grid Security Officer for authorisation and, if required, approval at the appropriate level of management.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">In exceptional circumstances it may be necessary for ''participants'' to take emergency action in response to some unforeseen situation which may violate some aspect of this ''policy'' for the greater good of pursuing or preserving legitimate ''Grid'' objectives.&nbsp;If such a ''policy'' violation is necessary, the exception should be minimised, documented, time-limited and authorised at the highest level of the ''management'' commensurate with taking the emergency action promptly, and the details notified to the Grid Security Officer at the earliest opportunity.</div><div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">6</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Sanctions</font></font>'''</div><div style="margin: 2pt 0cm;">''Resource Infrastructure Providers - need a para''</div>
+
<div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.2&nbsp;&nbsp;&nbsp; Resource Infrastructure Provider Management''</span></font>'''</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span</span></font>'''</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''i.e. a Resource Centre Federation''</span></font>'''</div><div style="margin: 12pt 0cm 3pt 28.8pt;"><font size="5"><span>A resource centre federation is resonspible for ensuring compliance of all its resource centre members and provides the capabilities for meeting the responsibilities for its members with respect to this policy and can represent its members towards the IT&nbsp;Organisation.</span></font></div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span</span></font>'''</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.3''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Virtual Organisation Management''</font>'''</div><div style="margin: 2pt 0cm;">The responsibilities of the ''VO management'' include:</div><div style="margin: 2pt 0cm;">2.3.0&nbsp;&nbsp; Appoint a Security Officer or ensure that they have a security incident response capability</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>VO Security Policies</font>'''</div><div style="margin: 2pt 0cm;">''VOs'' are required to abide by the Virtual Organisation Operations Policy [9] and the Virtual Organisation Registration Security Policy [2]. They must have a VO Acceptable Use Policy (AUP) and ensure that only individuals who have agreed to abide by the Grid AUP [1] and the VO AUP are registered as members of the ''VO''.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.2<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>User Registration and VO Membership Service</font>'''</div><div style="margin: 2pt 0cm;">The ''user'' registration procedure of the ''VO'' is required to be consistent with the Virtual Organisation Membership Management Policy [8]. Approval to join the ''VO'' must be restricted to individuals who are recognised as having legitimate rights to membership and who agree to be bound by the AUPs.&nbsp;A VO membership service must be provided with appropriate interfaces to generate authentication, authorization and other identity mapping data for the services running on the ''sites''. ''VO''s are required to maintain the accuracy of the information held and published about their members, and to promptly remove individuals who lose their right to such membership.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.3<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>VO-specific Resources and Services</font>'''</div><div style="margin: 2pt 0cm;">''VO''s are responsible for ensuring that their ''software'' does not pose security threats, that access to their databases is secure and is sufficiently monitored, that their stored ''data ''are compliant with legal requirements, and that VO-specific ''services'' are properly monitored and do not compromise ''sites'' or ''resources''.&nbsp; Need to refer to Service Operations policy...&nbsp; ALso VO&nbsp;Portal policy ... Also their client actions towards other participants.</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.3.4<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Applying Sanctions to Users</font>'''</div><div style="margin: 2pt 0cm;">''VOs'' are responsible for promptly investigating reports of ''users'' failing to comply with the AUPs and for taking appropriate action to ensure compliance in the future, as defined in section 6.</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.4''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Users''</font>'''</div><div style="margin: 2pt 0cm;">All ''users'' must be members of one of the registered ''VOs'' or application communities.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The responsibilities of ''users'' include:</div><div style="margin: 12pt 0cm 3pt 36pt;">'''<font size="4"><span>2.4.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Acceptable Use</font>'''</div><div style="margin: 2pt 0cm;">''Users'' must accept and agree to abide by the Grid Acceptable Use Policy [1] and the VO AUP when they register or renew their registration with a ''VO''. </div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' must be aware that their work may utilise shared resources and may therefore affect the work of others.&nbsp;They must show responsibility, consideration and respect towards other ''users'' in the demands they place on the ''Grid''.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' must have a suitable authentication credential issued as approved by the ''Grid''. They must ensure that others cannot use their credentials to masquerade as them or usurp their access rights.&nbsp;''Users'' may be held responsible for all actions taken using their credentials, whether carried out personally or not.&nbsp;No intentional sharing of credentials for ''Grid'' purposes is permitted.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' must be aware that their jobs will often use ''resources ''owned by others.&nbsp;They must observe any restrictions on access to ''resources'' that they encounter and must not attempt to circumvent such restrictions.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Application software written or selected by ''users'' for execution on ''resources'' must be directed exclusively to the legitimate purposes of their ''VO''.&nbsp;Such software must respect the autonomy and privacy of the host ''sites'' on whose ''resources'' it may run.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 12pt 0cm 3pt 28.8pt;">'''<font size="5"><span>''2.5''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span>''<span><span>Resource Centre</span></span>&nbsp;'''</font>'''<font size="5">''Management''</font</div>
 +
'''<div style="margin: 2pt 0cm;">The responsibilities of the ''Site management'' include:</div><div style="margin: 12pt 0cm 3pt 36pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 36pt;"><font size="4"><span>2.5.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Site Operations Policy</font</div>
 +
'''<div style="margin: 2pt 0cm;">''Sites'' hosting ''resources ''are required to provide reliable and well managed ''services'' and abide by the Grid Site Operations Policy [3]. ''Sites'' must abide by the Site Registration Security Policy [7] and the Grid Security Traceability and Logging Policy [5].</div><div style="margin: 12pt 0cm 3pt 36pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 36pt;"><font size="4"><span>2.5.2<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Mitigating Risks</font</div>
 +
'''<div style="margin: 2pt 0cm;">''Sites'' acknowledge that participating in the ''Grid'' increases the risk from security incidents, to both</div><div style="margin: 2pt 0cm;">''Grid'' and non-''Grid'' hosts on each site.&nbsp;''Sites'' are responsible for mitigating this risk.</div><div style="margin: 12pt 0cm 3pt 36pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 36pt;"><font size="4"><span>2.5.3<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Incident Response</font</div>
 +
'''<div style="margin: 2pt 0cm;">''Sites ''accept the duty to cooperate with Grid Security Operations and others in investigating and resolving security incidents, and to take responsible action as necessary to safeguard ''resources'' during an incident in accordance with the Security Incident Response Policy [6]. </div><div style="margin: 12pt 0cm 3pt 36pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 36pt;"><font size="4"><span>2.5.4<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Access Control</font</div>
 +
'''<div style="margin: 2pt 0cm;">Access to all ''resources'' is controlled by a common grid security infrastructure which includes both authentication and authorization components. The global components of this infrastructure, e.g. as specified in the Approval of Certification Authorities [4], must be deployed by all ''sites'' and ''resources''. The deployment of additional local security measures is permitted should the local security policies of the site or resource administration require this.</div><div style="margin: 12pt 0cm 3pt 36pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 36pt;"><font size="4"><span>2.5.5<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Notification of Legal Compliance Issues</font</div>
 +
'''<div style="margin: 2pt 0cm;">If exceptions or extensions to this ''policy'' are required because of local legislation, the ''site'' must inform the Grid Security Officer(see section 5).</div><div style="margin: 12pt 0cm 3pt 28.8pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 28.8pt;"><font size="5"><span>''2.6''<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>''Resource Centre Administrators''</font</div>
 +
'''<div style="margin: 2pt 0cm;">In addition to their local site policy ''resource centre administrators'' must ensure their implementations of ''services'' comply with this ''policy''. </div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">The responsibilities of ''resource centre&nbsp;administrators'' include:</div><div style="margin: 12pt 0cm 3pt 36pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 36pt;"><font size="4"><span>2.6.1<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Notifying Site Personnel</font</div>
 +
'''<div style="margin: 2pt 0cm;">''Resource administrators'' are responsible for ensuring that their ''site ''is registered with the ''Grid'' and that all appropriate personnel concerned with security or system management at their ''site'' are notified of and accept the requirements of this ''policy'' before offering any ''services''.</div><div style="margin: 12pt 0cm 3pt 36pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 36pt;"><font size="4"><span>2.6.2<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span>Resource Administration</font</div>
 +
'''<div style="margin: 2pt 0cm;">The ''resource administrators'' are responsible for the installation and maintenance of ''resources'' assigned to them, including the ongoing security and integrity.</div><div style="margin: 12pt 0cm 3pt 21.55pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 21.55pt;"><font size="6"><span><font size="5">3</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Physical Security</font></font</div>
 +
'''<div style="margin: 2pt 0cm;">All the requirements for the physical security of ''resources'' are expected to be adequately covered by each ''site’s'' local security policies and practices.&nbsp;These should, as a minimum, reduce the risks from intruders, fire, flood, power failure, equipment failure and environmental hazards.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Stronger physical security may be required for equipment used to provide certain critical ''services'' such as VO membership services or credential repositories.&nbsp;The technical details of such additional requirements are contained in the procedures for operating and approving such ''services''.</div><div style="margin: 12pt 0cm 3pt 21.55pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 21.55pt;"><font size="6"><span><font size="5">4</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Network Security</font></font</div>
 +
'''<div style="margin: 2pt 0cm;">All the requirements for the networking security of ''resources'' are expected to be adequately covered by each ''site’s'' local security policies and practices.&nbsp;These should, as a minimum, reduce the risks from intruders and failures of hardware or software by implementing appropriate firewall protection, by the timely application of all critical security-related software patches and updates, and by maintaining and observing clearly defined incident response procedures.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">It is ''Grid ''policy to minimise the security risk exposed by applications which need to communicate across the Internet; even so, the peripheral firewall on every participating ''site ''may be required to permit the transit of inbound and outbound packets to/from certain port numbers between a number of external and internal hosts in order to run or reach ''services''.</div><div style="margin: 12pt 0cm 3pt 21.55pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 21.55pt;"><font size="6"><span><font size="5">5</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Limits to Compliance</font></font</div>
 +
'''<div style="margin: 2pt 0cm;">Exceptions to compliance with this ''policy'' include, but are not limited to, the following:</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">Wherever possible,&nbsp;''IT&nbsp;Infrastructure'' policies and procedures are designed so that they may be applied uniformly across all&nbsp;resource centre federations, resource centres''&nbsp;''and''VOs.'' If this is not possible, for example due to legal or contractual obligations, exceptions may be made.&nbsp;Such exceptions must be justified in a document submitted to the IT Security Officer for authorisation and, if required, approval at the appropriate level of management.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">In exceptional circumstances it may be necessary for ''participants'' to take emergency action in response to some unforeseen situation which may violate some aspect of this ''policy'' for the greater good of pursuing or preserving legitimate&nbsp;''IT&nbsp;Infrastructure'' objectives.&nbsp;If such a ''policy'' violation is necessary, the exception should be minimised, documented, time-limited and authorised at the highest level of the ''management'' commensurate with taking the emergency action promptly, and the details notified to the&nbsp;IT Security Officer at the earliest opportunity.</div><div style="margin: 12pt 0cm 3pt 21.55pt;"></div>'''
 +
<div style="margin: 12pt 0cm 3pt 21.55pt;"><font size="6"><span><font size="5">6</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Sanctions</font></font</div>
 +
'''<div style="margin: 2pt 0cm;">''Resource Infrastructure Providers - need a para''</div>'''
 +
 
 
&lt;div style="margin: 2pt 0cm;"&lt;/div&gt;  
 
&lt;div style="margin: 2pt 0cm;"&lt;/div&gt;  
 
<div style="margin: 2pt 0cm;">''Sites'' or ''resource administrators'' who fail to comply with this ''policy'' in respect of a ''service'' they are operating may lose the right to have that service instance recognised by the ''Grid'' until compliance has been satisfactorily demonstrated again.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' who fail to comply with this ''policy'' may lose their right of access to and/or collaboration with the ''Grid'', and may have their activities reported to their home institute or, if those activities are thought to be illegal, to appropriate law enforcement agencies.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''VOs'' which fail to comply with this ''policy''','''''together with all the ''users'' whose rights with respect to the ''Grid'' derives from that ''VO'', may lose their right of access to and/or collaboration with the ''Grid''.&nbsp;</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;"><strike>The issues of liability, dispute resolution and intellectual property rights, all of which may be ''Grid''-specific, should be addressed in the additional policy documents. </strike>(We propose to delete this sentence)</div><div style="margin: 2pt 0cm;">&nbsp;</div>  
 
<div style="margin: 2pt 0cm;">''Sites'' or ''resource administrators'' who fail to comply with this ''policy'' in respect of a ''service'' they are operating may lose the right to have that service instance recognised by the ''Grid'' until compliance has been satisfactorily demonstrated again.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''Users'' who fail to comply with this ''policy'' may lose their right of access to and/or collaboration with the ''Grid'', and may have their activities reported to their home institute or, if those activities are thought to be illegal, to appropriate law enforcement agencies.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;">''VOs'' which fail to comply with this ''policy''','''''together with all the ''users'' whose rights with respect to the ''Grid'' derives from that ''VO'', may lose their right of access to and/or collaboration with the ''Grid''.&nbsp;</div><div style="margin: 2pt 0cm;">&nbsp;</div><div style="margin: 2pt 0cm;"><strike>The issues of liability, dispute resolution and intellectual property rights, all of which may be ''Grid''-specific, should be addressed in the additional policy documents. </strike>(We propose to delete this sentence)</div><div style="margin: 2pt 0cm;">&nbsp;</div>  
 
'''&lt;span style="text-transform: uppercase; font-size: 16pt;" /&gt;'''  
 
'''&lt;span style="text-transform: uppercase; font-size: 16pt;" /&gt;'''  
 
<div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">7</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Appendix 1: Additional Policy Documents</font></font>'''</div><div style="margin: 2pt 0cm;">The current list of additional policy documents describing procedures, rules and other technical details required to implement this ''policy'' are presented here.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">The current versions may always be found in the EGI document database at<br>[https://documents.egi.eu/public/DocumentDatabase <font color="#0000ff">EGI Document Database</font>]<br><br></div><div style="margin: 2pt 0cm;">An accompanying document for each ''Grid'' adopting this ''policy'' must define the ''Grid-''specific locations and version numbers of their approved and adopted additional policy documents</div><div style="margin: 2pt 0cm;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">The additional policy documents with their web links are as follows:<br><br></div><div align="left" style="margin: 2pt 0cm; text-align: left;">[1] Grid Acceptable Use Policy, [https://documents.egi.eu/document/74 <font color="#0000ff">https://documents.egi.eu/document/74</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[2] Virtual Organisation Registration Security Policy, [https://documents.egi.eu/document/78 <font color="#0000ff">https://documents.egi.eu/document/78</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;[3] Grid Site Operations Policy, [https://documents.egi.eu/document/75 <font color="#0000ff">https://documents.egi.eu/document/75</font>] </div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[4] Approval of Certification Authorities, [https://documents.egi.eu/document/83 <font color="#0000ff">https://documents.egi.eu/document/83</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[5] Grid Security Traceability and Logging Policy, [https://documents.egi.eu/document/81 <font color="#0000ff">https://documents.egi.eu/document/81</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[6] Security Incident Response Policy, [https://documents.egi.eu/document/82 <font color="#0000ff">https://documents.egi.eu/document/82</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[7] Site Registration Security Policy, [https://documents.egi.eu/document/76 <font color="#0000ff">https://documents.egi.eu/document/76</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[8] Virtual Organisation Membership Management Policy,<br>[https://documents.egi.eu/document/79 <font color="#0000ff">https://documents.egi.eu/document/79</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[9] Virtual Organisation Operations Policy, [https://documents.egi.eu/document/77 <font color="#0000ff">https://documents.egi.eu/document/77</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[10] VO Portal Policy, [https://documents.egi.eu/document/80 <font color="#0000ff">https://documents.egi.eu/document/80</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[11] Policy on Grid Multi User Pilot Jobs, [https://documents.egi.eu/document/84 <font color="#0000ff">https://documents.egi.eu/document/84</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[12] Grid Policy on the Handling of User-Level Job Accounting Data, [https://documents.egi.eu/document/85 <font color="#0000ff">https://documents.egi.eu/document/85</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[13] Security Policy Glossary of Terms, [https://documents.egi.eu/document/71 <font color="#0000ff">https://documents.egi.eu/document/71</font>]</div><div style="margin: 2pt 0cm;">&nbsp;</div>
 
<div style="margin: 12pt 0cm 3pt 21.55pt;">'''<font size="6"><span><font size="5">7</font><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><font size="5">Appendix 1: Additional Policy Documents</font></font>'''</div><div style="margin: 2pt 0cm;">The current list of additional policy documents describing procedures, rules and other technical details required to implement this ''policy'' are presented here.</div><div style="margin: 2pt 0cm;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">The current versions may always be found in the EGI document database at<br>[https://documents.egi.eu/public/DocumentDatabase <font color="#0000ff">EGI Document Database</font>]<br><br></div><div style="margin: 2pt 0cm;">An accompanying document for each ''Grid'' adopting this ''policy'' must define the ''Grid-''specific locations and version numbers of their approved and adopted additional policy documents</div><div style="margin: 2pt 0cm;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">The additional policy documents with their web links are as follows:<br><br></div><div align="left" style="margin: 2pt 0cm; text-align: left;">[1] Grid Acceptable Use Policy, [https://documents.egi.eu/document/74 <font color="#0000ff">https://documents.egi.eu/document/74</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[2] Virtual Organisation Registration Security Policy, [https://documents.egi.eu/document/78 <font color="#0000ff">https://documents.egi.eu/document/78</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;[3] Grid Site Operations Policy, [https://documents.egi.eu/document/75 <font color="#0000ff">https://documents.egi.eu/document/75</font>] </div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[4] Approval of Certification Authorities, [https://documents.egi.eu/document/83 <font color="#0000ff">https://documents.egi.eu/document/83</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[5] Grid Security Traceability and Logging Policy, [https://documents.egi.eu/document/81 <font color="#0000ff">https://documents.egi.eu/document/81</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[6] Security Incident Response Policy, [https://documents.egi.eu/document/82 <font color="#0000ff">https://documents.egi.eu/document/82</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[7] Site Registration Security Policy, [https://documents.egi.eu/document/76 <font color="#0000ff">https://documents.egi.eu/document/76</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[8] Virtual Organisation Membership Management Policy,<br>[https://documents.egi.eu/document/79 <font color="#0000ff">https://documents.egi.eu/document/79</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[9] Virtual Organisation Operations Policy, [https://documents.egi.eu/document/77 <font color="#0000ff">https://documents.egi.eu/document/77</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[10] VO Portal Policy, [https://documents.egi.eu/document/80 <font color="#0000ff">https://documents.egi.eu/document/80</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[11] Policy on Grid Multi User Pilot Jobs, [https://documents.egi.eu/document/84 <font color="#0000ff">https://documents.egi.eu/document/84</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[12] Grid Policy on the Handling of User-Level Job Accounting Data, [https://documents.egi.eu/document/85 <font color="#0000ff">https://documents.egi.eu/document/85</font>]</div><div align="left" style="margin: 2pt 0cm; text-align: left;">&nbsp;</div><div align="left" style="margin: 2pt 0cm; text-align: left;">[13] Security Policy Glossary of Terms, [https://documents.egi.eu/document/71 <font color="#0000ff">https://documents.egi.eu/document/71</font>]</div><div style="margin: 2pt 0cm;">&nbsp;</div>

Revision as of 16:19, 2 February 2012

TITLE: The IT Infrastructure Security Policy

1         Introduction and Definitions
To fulfil its mission, it is necessary for the IT Infrastructure to protect its assets. This document presents the policy regulating those activities of participants related to the security of the IT Infrastructure.
1.1       Definitions
The word Grid, when italicised in this document, means any project or operational infrastructure which uses grid technologies and decides to adopt this policy.
 
The other italicised words used in this document are defined as follows:
  • Policy is interpreted to include rules, responsibilities and procedures specified in this document together with all those in other documents which are required to exist by stipulations in this document.
  • A participant is any entity providing, using, managing, operating, supporting or coordinating one or more Grid service(s).
  • A service is any computing or software system, based on grid technologies, which provides access to, information about or controls resources.
  • A resource is the equipment and software required to run a service on theGrid, and any data
    held on the service.
  • Included in the definition of equipment are processors and associated disks, tapes and other peripherals, storage systems and storage media, networking components and interconnecting media.
  • Included in the definition ofsoftware are operating systems, utilities, compilers and other general purpose applications, any software required to operate any equipment, software and middleware released and/or distributed by the Grid and any software required to support any application associated with Virtual Organisations or other authorized users.
  • Included in the definition of data are data required to operate any equipment defined as a resource, data required to operate any service, data intended to be processed or produced by any software defined as a resource, and any application data.
  • The IT Organisation is the collection of the various boards, committees, groups and individuals mandated to oversee and control the IT Infrastructure.
  • A user is an individual who has been given authority to access and use Grid resources.
  • A Virtual Organisation (or VO) is a grouping of users and optionally resources, often not bound to a single institution, who, by reason of their common membership and in sharing a common goal, are given authority to use a set of resources.
  • Included in the definition of a VO are cases where Grid resources are offered to individual users who are not members of a formal VO. These users are, however, often associated with an applicationcommunity, and these communities, or even a single user, are treated in this document as though they are a VO.
  • VO management is the collection of various individuals and groups mandated to oversee and control a VO.
  • A site is an entity having administrative control of resources provided to the Grid. This may be at one physical location or spread across multiple physical locations.
  • Site management is the collection of various individuals and groups mandated to oversee and control a site.
  • A resource administrator is the person responsible for installing, operating, maintaining and supporting one or more resource(s) at a site.
1.2       Objectives
This policy gives authority for actions which may be carried out by certain individuals and bodies and places responsibilities on all participants.
1.3       Scope
This policyapplies to all participants.
 
Every site participating in the Grid autonomously owns and follows their own local security policies with respect to the system administration and networking of all the resources they own, including resources which are part of the Grid. This policy augments local policies by setting out additional Grid-specific requirements.
1.4       Additional Policy Documents
Appendix 1 defines additional policy documents which must exist for a proper implementation of this policy. These documents are referred to in section 2.
An accompanying document for each Grid adopting this policy must define the Grid-specific locations and version numbers of their approved and adopted additional policy documents.
1.5       Ownership and Maintenance
This policy is prepared and maintained by the Security Policy Group, approved by management and thereby endorsed and adopted by the Grid as a whole. 
 
This policy will be revised by the Security Policy Group as required and resubmitted for formal approval and adoption whenever significant changes are needed.
 
The most recently approved version of this document is available at https://documents.egi.eu/document/86
 
2         Roles and Responsibilities
This section defines the roles and responsibilities of participants.
Participants must be uniquely identifiable and the binding of identifiers to participants must be persistent, i.e. no name recycling.
2.1       The IT Organisation
TheIT Organisation provides, through the adoption of this policy and through its representations on the various approving bodies of the IT Infrastructure, the overall authority for the decisions and actions resulting from this policy including procedures for the resolution of disputes.

2.1.1       The IT Security Officer and the CSIRT

TheIT Organisation must appoint a IT Security Officer who leads and/or coordinates the CSIRT providing the operational security capability.
 
The IT Security Officer may, in consultation with the CSIRT, IT Organisation and other appropriate persons, require actions by participants as are deemed necessary to protect resources from or contain the spread of IT security incidents. The IT Security Officer also handles requests for exceptions to this policy as described in section 5
 
The responsibilities of Grid Security Operations include:
  • The maintenance of contact details of security personnel at each participating site and the facilitation of Grid-related communications between them.
  • Handling of operational security problems as they arise.
  • Providing incident response teams who will act according to the Security Incident Response Policy [6].
'2.2    Resource Infrastructure Provider Management
<span
i.e. a Resource Centre Federation
A resource centre federation is resonspible for ensuring compliance of all its resource centre members and provides the capabilities for meeting the responsibilities for its members with respect to this policy and can represent its members towards the IT Organisation.
<span
2.3       Virtual Organisation Management
The responsibilities of the VO management include:
2.3.0   Appoint a Security Officer or ensure that they have a security incident response capability
2.3.1      VO Security Policies
VOs are required to abide by the Virtual Organisation Operations Policy [9] and the Virtual Organisation Registration Security Policy [2]. They must have a VO Acceptable Use Policy (AUP) and ensure that only individuals who have agreed to abide by the Grid AUP [1] and the VO AUP are registered as members of the VO.
2.3.2      User Registration and VO Membership Service
The user registration procedure of the VO is required to be consistent with the Virtual Organisation Membership Management Policy [8]. Approval to join the VO must be restricted to individuals who are recognised as having legitimate rights to membership and who agree to be bound by the AUPs. A VO membership service must be provided with appropriate interfaces to generate authentication, authorization and other identity mapping data for the services running on the sites. VOs are required to maintain the accuracy of the information held and published about their members, and to promptly remove individuals who lose their right to such membership.
2.3.3      VO-specific Resources and Services
VOs are responsible for ensuring that their software does not pose security threats, that access to their databases is secure and is sufficiently monitored, that their stored data are compliant with legal requirements, and that VO-specific services are properly monitored and do not compromise sites or resources.  Need to refer to Service Operations policy...  ALso VO Portal policy ... Also their client actions towards other participants.
2.3.4      Applying Sanctions to Users
VOs are responsible for promptly investigating reports of users failing to comply with the AUPs and for taking appropriate action to ensure compliance in the future, as defined in section 6.
2.4       Users
All users must be members of one of the registered VOs or application communities.
 
The responsibilities of users include:
2.4.1      Acceptable Use
Users must accept and agree to abide by the Grid Acceptable Use Policy [1] and the VO AUP when they register or renew their registration with a VO.
 
Users must be aware that their work may utilise shared resources and may therefore affect the work of others. They must show responsibility, consideration and respect towards other users in the demands they place on the Grid.
 
Users must have a suitable authentication credential issued as approved by the Grid. They must ensure that others cannot use their credentials to masquerade as them or usurp their access rights. Users may be held responsible for all actions taken using their credentials, whether carried out personally or not. No intentional sharing of credentials for Grid purposes is permitted.
 
Users must be aware that their jobs will often use resources owned by others. They must observe any restrictions on access to resources that they encounter and must not attempt to circumvent such restrictions.
 
Application software written or selected by users for execution on resources must be directed exclusively to the legitimate purposes of their VO. Such software must respect the autonomy and privacy of the host sites on whose resources it may run.
 
2.5       Resource Centre Management</font
The responsibilities of the Site management include:
2.5.1      Site Operations Policy</font
Sites hosting resources are required to provide reliable and well managed services and abide by the Grid Site Operations Policy [3]. Sites must abide by the Site Registration Security Policy [7] and the Grid Security Traceability and Logging Policy [5].
2.5.2      Mitigating Risks</font
Sites acknowledge that participating in the Grid increases the risk from security incidents, to both
Grid and non-Grid hosts on each site. Sites are responsible for mitigating this risk.
2.5.3      Incident Response</font
Sites accept the duty to cooperate with Grid Security Operations and others in investigating and resolving security incidents, and to take responsible action as necessary to safeguard resources during an incident in accordance with the Security Incident Response Policy [6].
2.5.4      Access Control</font
Access to all resources is controlled by a common grid security infrastructure which includes both authentication and authorization components. The global components of this infrastructure, e.g. as specified in the Approval of Certification Authorities [4], must be deployed by all sites and resources. The deployment of additional local security measures is permitted should the local security policies of the site or resource administration require this.
2.5.5      Notification of Legal Compliance Issues</font
If exceptions or extensions to this policy are required because of local legislation, the site must inform the Grid Security Officer(see section 5).
2.6       Resource Centre Administrators</font
In addition to their local site policy resource centre administrators must ensure their implementations of services comply with this policy.
 
The responsibilities of resource centre administrators include:
2.6.1      Notifying Site Personnel</font
Resource administrators are responsible for ensuring that their site is registered with the Grid and that all appropriate personnel concerned with security or system management at their site are notified of and accept the requirements of this policy before offering any services.
2.6.2      Resource Administration</font
The resource administrators are responsible for the installation and maintenance of resources assigned to them, including the ongoing security and integrity.
3         Physical Security</font
All the requirements for the physical security of resources are expected to be adequately covered by each site’s local security policies and practices. These should, as a minimum, reduce the risks from intruders, fire, flood, power failure, equipment failure and environmental hazards.
 
Stronger physical security may be required for equipment used to provide certain critical services such as VO membership services or credential repositories. The technical details of such additional requirements are contained in the procedures for operating and approving such services.
4         Network Security</font
All the requirements for the networking security of resources are expected to be adequately covered by each site’s local security policies and practices. These should, as a minimum, reduce the risks from intruders and failures of hardware or software by implementing appropriate firewall protection, by the timely application of all critical security-related software patches and updates, and by maintaining and observing clearly defined incident response procedures.
 
It is Grid policy to minimise the security risk exposed by applications which need to communicate across the Internet; even so, the peripheral firewall on every participating site may be required to permit the transit of inbound and outbound packets to/from certain port numbers between a number of external and internal hosts in order to run or reach services.
5         Limits to Compliance</font
Exceptions to compliance with this policy include, but are not limited to, the following:
 
Wherever possible, IT Infrastructure policies and procedures are designed so that they may be applied uniformly across all resource centre federations, resource centres andVOs. If this is not possible, for example due to legal or contractual obligations, exceptions may be made. Such exceptions must be justified in a document submitted to the IT Security Officer for authorisation and, if required, approval at the appropriate level of management.
 
In exceptional circumstances it may be necessary for participants to take emergency action in response to some unforeseen situation which may violate some aspect of this policy for the greater good of pursuing or preserving legitimate IT Infrastructure objectives. If such a policy violation is necessary, the exception should be minimised, documented, time-limited and authorised at the highest level of the management commensurate with taking the emergency action promptly, and the details notified to the IT Security Officer at the earliest opportunity.
6         Sanctions</font
Resource Infrastructure Providers - need a para

<div style="margin: 2pt 0cm;"</div>

Sites or resource administrators who fail to comply with this policy in respect of a service they are operating may lose the right to have that service instance recognised by the Grid until compliance has been satisfactorily demonstrated again.
 
Users who fail to comply with this policy may lose their right of access to and/or collaboration with the Grid, and may have their activities reported to their home institute or, if those activities are thought to be illegal, to appropriate law enforcement agencies.
 
VOs which fail to comply with this policy,together with all the users whose rights with respect to the Grid derives from that VO, may lose their right of access to and/or collaboration with the Grid
 
The issues of liability, dispute resolution and intellectual property rights, all of which may be Grid-specific, should be addressed in the additional policy documents. (We propose to delete this sentence)
 

<span style="text-transform: uppercase; font-size: 16pt;" />

7         Appendix 1: Additional Policy Documents
The current list of additional policy documents describing procedures, rules and other technical details required to implement this policy are presented here.
 
The current versions may always be found in the EGI document database at
EGI Document Database

An accompanying document for each Grid adopting this policy must define the Grid-specific locations and version numbers of their approved and adopted additional policy documents
 
The additional policy documents with their web links are as follows:

[1] Grid Acceptable Use Policy, https://documents.egi.eu/document/74
 
[2] Virtual Organisation Registration Security Policy, https://documents.egi.eu/document/78
 
 [3] Grid Site Operations Policy, https://documents.egi.eu/document/75
 
[4] Approval of Certification Authorities, https://documents.egi.eu/document/83
 
[5] Grid Security Traceability and Logging Policy, https://documents.egi.eu/document/81
 
[6] Security Incident Response Policy, https://documents.egi.eu/document/82
 
[7] Site Registration Security Policy, https://documents.egi.eu/document/76
 
[8] Virtual Organisation Membership Management Policy,
https://documents.egi.eu/document/79
 
[9] Virtual Organisation Operations Policy, https://documents.egi.eu/document/77
 
 
[11] Policy on Grid Multi User Pilot Jobs, https://documents.egi.eu/document/84
 
[12] Grid Policy on the Handling of User-Level Job Accounting Data, https://documents.egi.eu/document/85
 
[13] Security Policy Glossary of Terms, https://documents.egi.eu/document/71