View source for EGI-InSPIRE:Plan 2013 SA1.2

{{Template:Op menubar}} {{Template:Inspire_reports_menubar}} {{TOC_right}} 
[[Category:EGI-inSPIRE SA1]]
= Assessment of progress in 2012 =

==Completed Activities and Milestones==
<!-- please make sure that the text here is self explanatory and sufficiently detailed-->

Successful ongoing security operational activities, including SVG operations and close collaboration on the MW upgrade campaign.

Specific milestones achieved during 2012 include:
* extension of access Monitor Module of SSC5
* 1 NGI run of SSC5 
* further development of security dashboard
* EMI Vulnerability Assessment of VOMS Core
* Security Threat Risk Assessment (as described in D4.4)
* CSIRT face to face meeting
* extension of SSC5 framework (integration of more job-submission methods), improvement of reporting module
* optimization of alerts in security dashboard
* proposal for site-wide security monitoring
* Update of the EGI Software Vulnerability Group/EMI Vulnerability Assessment plan, including status report. (This is for pro-active examination of software to find vulnerabilities that may exist carried out by our collaborators.)
* Ran SSC6
* update of site certification procedure
* SVG face to face meeting
* security training at EGI technical forum
* EMI Vulnerability Assessment of WMS completion started (but delayed by illness)

==Milestones not accomplished==
<!-- list here milestones that were not completed according to the envisaged schedule, saying why they were not completed, and the new schedule is -->


* The security vulnerability assessment of WMS and CREAM (started but not completed)
* Improvements to the RTIR ticketing system are still awaited
* The evaluation of SSC6 still to be completed
* nagios: CRL checking on services that have gridftp (CEs/SEs) and checking for known vulnerable file permissions via gridftp
* The revision of the Vulnerability Issue handing procedure was postponed to handle post EMI/IGE handling at the same time
* EGI CSIRT operational procedure for compromised certificates still to be done
* Security monitoring
** New version of Pakiti -- largely maintenance performed; insufficient effort to finish current development version
** docs on site-wide monitoring

= Plans for 2013 =
<!-- add or remove entries below as needed -->

==Cross Security Team Activities==

* MS235 Security Activity within EGI Month 34 Report detailing the non-operational security activity within EGI including SCG, SVG, EUGridPMA and IGTF.
* EGI Security Threat risk assessment - Report on what is being done concerning threats of highest risk value and highest impact value.
* Re-assess security risk assessment - start at end of 2013, to be completed before end of EGI-InSPIRE
* Investigate Federated Cloud Services and the implications for the various security groups. Assist in defining new policies and procedures to implement these.

==EGI CSIRT Activities==

===Daily security operations===

A very important part of the CSIRT work
* Via the Security Officer on Duty rota, carry out all agreed tasks as specified at
https://wiki.egi.eu/csirt/index.php/Security_Officer_on_Duty_tasks


===CSIRT meetings===

* Regular monthly team meetings including 2 F2F meetings 

===RTIR ticketing system===

* Need improvements to RTIR for Security Service Challenges (Q2)
* EGI customisations need to be ported to new releases of RTIR (by EGI IT team) or move away from use of EGI SSO

===Incident Response===

* Regular weekly IRTF meetings
* handle security incidents as and when they occur
* Plan for and build a sustainable future beyond the end of EGI-InSPIRE

===Security drills===

* Complete the evaluation of SSC6
* Define, develop and run SSC7 in Q2-3, with subsequent evaluation/debriefing
* NGI runs to be carried out, say one or two in Q1, more in the following Q n

===Security monitoring tools===
<!-- add or remove entries below as needed -->
* Assist in SHA2 "campaign"
* if needed continue to support MW-Upgrade campaigns
* site-wide monitoring - a description of plans produced and delivered to OMB (Q1), technical pilot with a few NGIs implemented and evaluated (Q2-Q4)
* Pakiti release - alpha (Q2), final (Q4). If we don't have resources for more extensive development, the current development release will be frozen and stabilized. The EGI instance will be primarily supported focusing mainly on sufficient support for site-wide monitoring.
* probes - overview the SVG/CSIRT issues/alerts and make sure they're monitored, enable sending notifications (Q2).
* Collaboration with dashboard developers
** Involvement of RODs in handling non-criticial issues (our results start appearing in operational dashboard) (Q?)
** Start providing reports to mgmt/NGIs/sites - providing monthly (?) plots summarizing number of issues detected/handled (Q2)
* Monitoring of our tool with EGI-wide monitoring (Q3)
* nagios: CRL checking on services that have gridftp (CEs/SEs) and checking for known vulnerable file permissions via gridftp


====Security Training&Dissemination====

* Training in the TF-CSIRT / FIRST in January in Lisbon (Q1)
* Training at ISGC 2013
* Preparation of a poster for EGI CF
* Consider training at other Grid events such as GKS and TF (Q2/3)
* Updating and renovation of the CSIRT Wiki

====Security procedures====

* EGI CSIRT operational procedure for compromised certificates. (1st quarter)

==EGI SVG Activities==
<!-- Add or remove entries as needed -->
===Continue Vulnerability issue handling===
* The most important activity of the group is to perform its ongoing operational duties handling vulnerabilities according to the agreed procedures

===SVG meetings===

* Monthly SVG meetings
* SVG session at EGI Technical Forum

===Revise and improve Vulnerability Issue handing procedure ===

* Revise EGI Software Vulnerability Handling procedure for Post EMI/IGE. (Also submitted an abstract to present this at the CF.)
* Poster at CF on how to report a vulnerability or incident (and explain the difference) to be generally useful as well as for the CF. (CSIRT/SVG)
* Further revise Vulnerability issue handling - after a few months using it.
* Improve tracking of vulnerable and fixed RPM versions, platforms, and distributions. 

===Vulnerability Assessments===

* Completion of WMS vulnerability Assessment
* CREAM vulnerability Assessment
* Report on Status of Vulnerability assessment after the end of EMI - and whether anything further can be done.