EGI Document 2734-v12

EGI Applications On Demand service - Security Policy (Infrastructure for the long tail of science)

Document #:
EGI-doc-2734-v12
Document type:
Policy
Submitted by:
David Kelsey
Updated by:
David Kelsey
Document Created:
11 Jan 2016, 18:43
Contents Revised:
05 May 2017, 08:29
Metadata Revised:
05 May 2017, 08:29
Viewable by:
  • Public document
Modifiable by:

Quick Links:
Latest Version

Other Versions:
EGI-doc-2734-v11
05 May 2017, 08:13
EGI-doc-2734-v10
03 Apr 2017, 18:28
EGI-doc-2734-v9
01 Feb 2017, 08:30
EGI-doc-2734-v8
01 Feb 2017, 08:30
EGI-doc-2734-v7
30 Jan 2017, 12:43
EGI-doc-2734-v6
30 Jan 2017, 12:40
EGI-doc-2734-v5
21 Oct 2016, 12:08
EGI-doc-2734-v4
07 Oct 2016, 10:09
EGI-doc-2734-v3
07 Oct 2016, 10:07
Abstract:
This document is applicable to all and only the Participants involved in the provisioning of the ‘EGI Applications On Demand service’, accessible at http://access.egi.eu. The goal of the service is to offer user-friendly access to e-infrastructure services for members of the long tail of science, i.e. for individual researchers and small research teams who do not belong to any of the established EGI Virtual Organisation communities.

This Policy and the Implementation Guidelines aim to enable a low-barrier Service to be offered to a wide range of research users in Europe and their collaborators world-wide, by any Resource Centre organisation that elects to do so. In offering such services, the Resource Centre shall not negatively affect the security or change the security risk of any other Resource Centre or any other part of the e-Infrastructure. In particular, security incidents originating in the LToS Service should not impact the IT Infrastructure in ways that are incompatible with the operational model of other, more tightly controlled, parts of the infrastructure. This document also provides guidelines on the implementation of security procedures and controls to facilitate offering of the Service by Resource Centres and Science Gateways. The Guidelines contain normative information on how to implement the Policy.

Files in Document:
Authors:

DocDB, Contact: Document Database Administrators