|Main||EGI.eu 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|
|22/08/2013||https://www.egi.eu/indico/conferenceDisplay.py?confId=1807||EGI CSIRT team Monthly meeting||Review activities of the previous month and plan for the coming month|
|12/09/2013||https://www.egi.eu/indico/conferenceDisplay.py?confId=1868||EGI SVG Monthly meeting||Review activities of the previous month and plan for the coming month|
|30/10/2013||https://www.egi.eu/indico/conferenceDisplay.py?confId=1927||EGI SVG monthly meeting||Review activities of the previous month and plan for the coming month|
|31/10/2013||https://www.egi.eu/indico/conferenceDisplay.py?confId=1923||EGI CSIRT team monthly meeting||Review activities of the previous month and plan for the coming month|
|Weekly Video conference meetings (every Monday)||Minutes recorded in EGI CSIRT private wiki (not publicly accessible)||IRTF weekly meeting||Operational security issues are reviewed weekly|
2. Main Achievements
The work of the EGI CSIRT (TSA1.2), as ever, is split into several sub-groups, each of which is reported on here. The whole team continues to meet monthly by video conference, except that we did not have a meeting in September as we had a security session that month at the EGI Technical Forum in Madrid.
For the Incident Response Task Force (IRTF) 4 security incidents were handled during the quarter. Three of these related to stolen ssh passwords while one was as the result of a brute-force ssh scanner. The IRTF continued to track new security vulnerabilities in operating systems and other non-Grid software, and chase sites who were vulnerable to previously announced problems. A joint security training event and security workshop between EGI and security staff from PRACE and EUDAT was held on 7-9 October 2013 in Linkoping, Sweden. This was a very useful and successful meeting and plans for future closer cooperation on security operations were discussed.
For the Security Drills team, it was not yet possible to run the NGI Security Service Challenge (SSC) in Germany. A successful training session at the EGI Technical Forum helped a number of other NGIs prepare for their own SSC. Plans are now well underway for the next NGI SSC in Italy.
For the monitoring team, further testing of site-wide monitoring took place at the pilot site (KIT, Germany). The next step will be to deploy more pilot sites allowing a move towards a full delpoyment across EGI. A new version of Pakiti was deployed with an implementation of better mechanisms for collecting data from the sites. Currently the probes report to both the old and the new servers. New NAGIOS probes were developed and deployed to monitor new critical vulnerabilities from SVG. A new mechanism for processing data for the dashboard was agreed during the EGI TF and when ready this will allow better viewing of security issues in a single place.
Experience of handling vulnerabilities after the end of EMI and IGE shows that the Software Vulnerabiliy Group (SVG) communication and handling procedures are still working well. No changes to the SVG procedures are needed. The SVG risk assessment team suffers from lack of effort available for performing the risk assessments. During the quarter, 11 new vulnerabilities were handled, including one critical and 6 high-risk issues. SVG issued 6 public advisories and one advisory that went to all EGI sites. The security assessment of CREAM-CE was completed and reported at the EGI TF. The vast majority of problems found have now been fixed. The assessment of WMS was peformed but the team doing this work were not happy with the results and wish to revisit this. In the mean time work has started on an assessment of middleware from UNICORE.
The Emergency Suspension procedures document was finalised and approved by OMB in its September 2013 meeting. The Italian NGI has successfully deployed an NGI Argus server which is correctly handling the suspended credentials out to Italian sites who also run Argus. The next step is to implement a mechanism for deployment at sites not running Argus.
Many members of the CSIRT team attended the EGI Technical Forum in Madrid in September. Three security training courses were successfully given and all security activities (operational and policy) were presented and discussed at an open session. Training was also give at the GridKa school in August. Plans have been made for a number of future training and dissemination events.
There was little time to make much progress on forming a better understanding of the requirements for security in federated clouds, particularly as we had no private face to face meeting during the quarter. This will be a topic for dicussion at the next face to face meeting in December 2013.
3. Issues and Mitigation
|Issue Description||Mitigation Description|
4. Plans for the next period
DRAFT - NOT COMPLETED
During the next quarter, the EGI CSIRT team will continue to work on all if its current activities in the same sub-groups. Apart from the usual ongoing regular operational duties, the following items are mentioned.
For IRTF, planning will continue for incident handling beyond the end of EGI-InSPIRE. A joint meeting between EGI CSIRT and security staff from PRACE and EUDAT is planned for October. Future cooperation on security operations will be one of the topics to be discussed there.
For the Security Drills team, the German NGI SSC will be performed. Training will be given at the EGI Technical Forum to help other NGIs prepare for and operate their own SSC.
For the monitoring team, further testing of site-wide monitoring will be performed, working towards a full-blown proposal to EGI for deployment. Work will continue on Pakiti to support this. Collaboration with the dashboard developers will work towards the provision of better reports on security issues to sites, operations and management.
The SVG will consider how to improve distribution/version handling and tracking. Revision of the vulnerability issue handling document will take place now that the post-EMI/IGE situation is clearer, and will take account of other changes that are happening. The SVG will act on the reports on the WMS and CREAM security assessments when these become available.
The Emergency Suspension document will be finalised and OMB approval will be sought. First implementation of the suspension ARGUS system will either be deployed and tested or planned for the following quarter.
Members of the team will attend the EGI Technical Forum in Madrid to give various security training courses and to present at and run the planned EGI security sessions. Plans will be made for future training and dissemination.
Work will continue on forming a better understanding of the requirements for security in federated clouds, taking forward a suitable use case and deployment of monitoring and logging in the virtualised environment.