From EGIWiki
Revision as of 19:06, 3 February 2014 by Dkelsey (talk | contribs) (2. Main Achievements)
Jump to: navigation, 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
02/12/2013 EGI CSIRT team face to face meeting (2-3 Dec 2013) in Bergen Aan Zee, NL Review activities of the previous month and plan for the coming month
09/01/2014 EGI SVG monthly meeting Review activities of the previous quarter and plan for the coming quarter
30/01/2014 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

DRAFT at this point.

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 the November and December meetings were combined into one two-day face to face meeting at the start of December. This meeting also involved participation by security experts from PRACE and EUDAT, continuing our growing collaboration with these infrastructures.

For the Incident Response Task Force (IRTF) xx security incidents were handled during the quarter. This is more than in recent quarters and confirms the need to chase sites with the timely application of security patches. ?Provide breakdown of types of incident?. 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.

The CSIRT has been an accredited member of the TERENA Trusted Introducer scheme since October 2012. We are now carrying out the necessary steps to achieve full certification. An on-site visit happened in January 2014 with detailed investigation of our polices and procedures. We are awaiting the report from this vist to see what changes are required for full certification.

For the Security Drills team, we were still not able to run the planned NGI Security Service Challenges (SSC) in Germany and Italy. The final technical preparations required should now happen in February allowing the national SSC campaigns to happen soon after. A challenge of the NGI security communication infrastructure has been prepared and will take place during the next quarter.

For the monitoring team, further testing of site-wide monitoring took place at the pilot site (KIT, Germany). Work also continued on improving the combination of data from Pakiti and the Nagios probes to allow better viewing of security issues in a single place. A new security Nagios server was deployed with the latest release of SAM (update 22). New Nagios probes were developed and deployed as required to monitor new critical vulnerabilities from SVG.

The Software Vulnerability Group (SVG) continues to handle reported vulnerabilities. This quarter was somewhat quieter than recent times with 6 new vulnerabilities being addressed, including one high-risk issue. The other five issues were moderate risk or below. SVG issued two advisories that went to all EGI sites and one advisory to the EGI federated clouds team. To help deal with vulnerabilities still not patched in production code, the SVG produced an interim special version of Torque. All outstanding security assessments were completed and it has been decided that the next component to be assessed will be CVMFS if volunteer effort becomes available.

Work on the deployment of Emergency Suspension continues. About half of the NGIs have now deployed a national Argus server and testing of this infrastructure continues.

Plans have been made for a number of future training and dissemination events. Plans are well advanced for a one-day training event at the ISGC 2014 event in Taipei in March 2014. A similar event is also proposed for the EGI Community Forum in May (Helsinki).

Two members of the CSIRT attended a workshop of the EGI federated cloud team in Oxford in January. Presentations were given on the importance of operational security and a questionnaire for Cloud providers has been produced. It is clear that considerable work needs to be done on policies and procedures for the federated cloud service. New procedures for certification of cloud providers are required and we need to develop a new test suite to check basic traceability of actions and developments in security monitoring are likely to be required.

3. Issues and Mitigation

Issue Description Mitigation Description
Funding and effort for operational security in EGI Federated Clouds. Lots of work to do. We need more effort and funding. We will discuss with the management.

4. Plans for the next period

DRAFT at this point.

During the next quarter, the EGI CSIRT team will continue to work on all if its current activities in the same sub-groups. A face to face meeting of the whole team may be held in April if we can find a suitable date and location, if not it will have to happen after the end of EGI-InSPIRE. This meeting will review all our plans for security after EGI-InSPIRE, including the changes needed to cope with security in the EGI federated cloud service.

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. Joint discussions on this topic with PRACE and EUDAT will continue. The full certification of the CSIRT in TERENA Trusted Introducer will continue once the report of the site visit is available.

For the Security Drills team, the German and Italian NGI SSC will be performed. Plans will be made for the next set of NGI SSC's. The challenge of the NGI security communication infrastructure will take place.

A full-blown proposal for the deployment of the site-wide monitoring system in EGI will be provided. Monitoring and probes will be developed as required by security incident and vulnerability handling.

SVG will prepare a report on the vulnerability assessments that have happened, referring back to the original plans made in early 2011. It should be noted that all the software which was planned to be assessed in this original plan has had their assessments completed or they are currently in progress. Plans will be made for which pieces of software should have priority for the future, assuming this activity is able continue. This will probably include one or more of Data Management and software enabling cloud federation. Engagement with the EGI Federated cloud team is required, including invitations to join the RAT.

Work will continue on the deployment and testing of the Emergency Suspension mechanisms, using the deployed NGI Argus instances.

Various security training courses will be given. These will include ISGC 2014 in Taipei (March 2014) and the EGI Community Forum in May.

Work will continue on forming a better understanding of the requirements for security policy and procedures in federated clouds, if effort and funding for this activity can be found. A security threat risk assessment for federated clouds will happen as part of the general review of the EGI security risk assessment.