Document control
Procedure reviews
The following table is updated after every review of this procedure.
Table of contents
Overview
The document describes the process for suspending a Resource Centre in the EGI infrastructure. The aim of this procedure is to ensure that the all parties are notified about suspension and that record history is kept.
Definitions
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Entities involved in the procedure
- Resource Centre Manager: person who is responsible for Resource Centre.
- NGI Representative (NGI): person who is responsible for NGI Operations.
Service Delivery and Information Security Lead: person who oversees the implementation of the procedure and coordinate communication with EGI governance bodies if necessary
Service Delivery and Information Security Team: team of the EGI Foundation responsible for performing suspension at EGI Federation Level, when required
- EGI Foundation Director: person responsible of keeping the Service Delivery and Information Security Lead and of defining the applicable suspension plan and communications plan
Triggers
Resource Centre can be suspended either by NGI operators or the Service Delivery and Information Security Team member in case of breaking Resource Centre Operational Level Agreement or whenever a risk is identified at national or EGI Federation level related to the participation of the Resource Centre in the EGI Infrastructure.
- PROC01: Resource Centre is failing EGI Infrastructure Oversight escalation procedure
- Level 3: NGI/ROC operations manager should make Resource Centre responsive or suspend it
- Level 4: If no action was taken by NGI/ROC operations manager for 5 working days Operations send an email to NGI/ROC operations manager with CC to site administrator, ROD and GGUS. If no response after 1 working day Operations performs Resource Centre suspension.
- PROC04: Resource Centre is underperforming (below the OLA target) for 3 consecutive months
- PROC16: Resource Centre is failing Decommissioning of unsupported software procedure
- Follow up the migration: Resource Centre which didn't provide information on migration plans can be suspended
- SEC01-05: Resource Centre is failing Security Incident or Critical Security procedure
Notes for suspended Resource Centres
- Suspended Resource Centres are not displayed in GGUS
- When a Resource Centre gets suspended in GOC DB the "Notified site" field is flushed automatically in the corresponding tickets, and NGIs start managing them (processing or closing is up to them).
Steps
In case of suspension decided by the NGI or the Service Delivery and Information Security Team of the EGI Foundation
| # | Responsible | Action | Notes |
|---|---|---|---|
| 1 | NGI/Service Delivery and Information Security Lead at the EGI Foundation | Decision about suspension | In case a risk is identified by the EGI Executive Board and/or the EGI Council that requires the suspension as mitigation action, the EGI Service Delivery and Information Security Lead is informed by the EGI Director. |
| 2 | NGI/EGI Foundation Service Delivery and Information Security Team | Notification is sent to Resource Centre Manager and to NGI Representative – a minimum of 3 working day on reaction | The NGI or the EGI Service Delivery and Information Security Lead are responsible for deciding the notification period applicable to the case. The notification period is decided in consultation with the affected VOs. The chosen notification period is communicated. |
| 3 | NGI/EGI Foundation Service Delivery and Information Security Team | If there is no reply from Resource Centre Manager
|
In case of suspension decided by the EGI Executive Board or the EGI Council.
| # | Responsible | Action | Notes |
|---|---|---|---|
| 1 | EGI Foundation Director | EGI Director informs Service Delivery and Information Security Lead at the EGI Foundation about the need to proceed with suspension to enforce a EB or Council decision. | |
| 2 | EGI Director and Service Delivery and Information Security Lead | DEFINITION OF SUSPENSION PLAN Define applicable suspension actions to be implemented depending on the motivation of suspension. See the following list of options. Change status of the Resource Centre to ‘SUSPENDED’(mandatory) Suspending a site in GOCDB effectively ‘removes’ the site from the production infrastructure. The site will then need to be recertified. Consequences of this are:
Revoking of roles of key personnel at a site (optional, depending on suspension case) Revoking of roles of individual persons in GOCDB. Consequences of this are: access to the Pakiki security monitoring system is no longer possible. Revoking X509 certificates of key personnel at a site (optional, depending on suspension case) This is possible by individual Certificate Authorities revoking certificates across the federation, or at the level of ARGUS which affects resources using this authorization service. Consequences of this would be to prevent people from making use of services using X509 certificate authentication Remove an Identity Provider (IdP) from Check-in (optional, depending on suspension case) Removal of an institute’s IdP from a site from Check-in would have the consequence of preventing anybody with a local institutional login at that site authenticating with another resource provider across the federation when making use of the Check-in service. | |
| 3 | EGI Director and Service Delivery and Information Security Lead | DEFINITION OF COMMUNICATION PLAN Define the list of entities to be informed about the suspension decision and the defined suspension plan.
| |
| 4 | Service Delivery and Information Security Lead | Oversee the execution of the suspension plan, in coordination with the Service Delivery and Information Security Team | |
| 5 | Service Delivery and Information Security Lead | Inform EGI Director about the completed execution of the suspension plan |