Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @


From EGIWiki
Revision as of 19:46, 6 February 2013 by Dkelsey (talk | contribs)
Jump to navigation Jump to search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports

1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome
15/11/20112 EGI SVG Monthly meeting Review activities of the previous month and plan for the coming month
22/11/2012 EGI CSIRT team Monthly meeting Review activities of the previous month and plan for the coming month
13/12/2012 EGI CSIRT team monthly meeting Review activities of the previous month and plan for the coming month
20/12/2012 EGI SVG Monthly meeting Review activities of the previous month and plan for the coming month
17/01/2013 EGI SVG Monthly meeting Review activities of the previous month and plan for the coming month
18/01/2013 EGI CSIRT team monthly meeting Review activities of the previous month and plan for the coming month
Weekly EVO meetings (every Monday) Minutes recorded in EGI CSIRT private wiki (not publicly accessible) IRTF weekly meeting Operational security issues are reviewed weekly
Weekly EVO meetings (every Monday) "Monitoring & follow up of sites running unsupported software" - joint with EGI Operations Status of the Sites upgrading to supported software are reviewed weekly

2. Main Achievements

The incident response team handled one minor security incident involving a site in Estonia during the quarter and issued just one security advisory.

This relatively quiet period in terms of incidents was however used to make very good progress on the monitoring, persuading, and even forcing, all Resource Centres to upgrade or replace software that was no longer supported for security updates. A large number of components of gLite 3.2 were required to be removed by 1st November 2012. An intense upgrade campaign was necessary with many of the SA1.2 staff very actively involved both from the monitoring and the incident teams. This was very successful in that the vast majority of sites upgraded before the deadline and the remaining small number voluntarily removed the services from production. There was no requirement to suspend a site. The final components of gLite 3.2 had to be upgraded or removed before the end of January 2013. Again this campaign was very successful. We are now planning for the end of life of EMI 1 by the end of April 2013.

The upgrading of all EGI instances of WMS services which were still affected by the two vulnerabilities handled in the last quarter was also completed early in the quarter.

The security monitoring activity was very busy during the quarter, developing and deploying new custom security probes as required for monitoring for deployed software beyond end of support and also for the NGI SAM instances. A dedicated Nagios box was established to monitor middleware components.

After the successful run of security service challenge SSC6 last quarter, there has been little activity in this area during this quarter, partly because we still await upgrades and modifications to the special RTIR service used for monitoring progress in these service challenges and partly because of all the activity on middleware ugrade campaigns. Plans have been made for a number of NGI SSCs which will happen in 2013.

The Software Vulnerability Group handled more than ten new vulnerabilities during the quarter and issued or updated five advisories, one of which was High Risk. Work on the procedure for handling compromised certificates has started as has work to define the handling of software vulnerabilities in the period beyond the end of the EMI and IGE projects.

Preparations have been made for the next EGI-CSIRT security tutorial to happen at the ISGC2013 conference in Taipei in March 2013. An abstratc on EGI security operations was also submitted to the conference and accepted for oral presentation. A poster on Security Training and best practice from the point of view of end users is being prepared for the April 2013 EGI Community Forum meeting.

It has long been recognised that the deployment of a centrally run emergency user suspension service would be extremely useful for the CSIRT during the handling of an ongoing security incident. The suspension of a compromised user identity, from the authorisation point of view, defined in one place and then automatically rolled out to all sites and services in a short period of time is currently missing. Discussions were held during this quarter with Operations, SPG and the OMB and deployment mechanisms are being planned.

Members of TSA1.2 participated in a WLCG security meeting at FNAL in the USA on the 17-18 December. This brought together security staff from EGI, OSG and NDGF and included full discussion of many operational security and policy issues

Central user banning meeting (13 Dec) and present to OMB on 18 Dec Propose mini-projects

Planning for Global tasks evolution beyond EGI-InSPIRE

3. Issues and Mitigation

Issue Description Mitigation Description

4. Plans for the next period

Work will continue on the improvements of the RT/RTIR ticketing system, e.g. to facilitate better reporting.

The Site Certification Procedure will be revised to include the required security items and a procedure will be developed for the handling of compromised certificates.

Work will continue on requiring the timely migration from unsupported software.

Work will continue on Pakiti V3 and the move to site-wide security monitoring.

SSC6 will be performed at approximately 40 sites across EGI and more NGIs will perform the national variant of SSC5.

Security training will be given at the GridKa school and the Technical Forum. These will include hands-on training in forensics.

The annual review of the SVG issue handling procedure will be performed.