...

The following table describes the actions to be taken when an incident potentially affecting EGI users, data, services, infrastructure is suspected. Administrators are recommended to take note of every action (with timestamp) they take, for later analysis or legal cases.

Resource Centre Checklist

...

EGI-CSIRT Responsibilities

...

• Evaluate the initial incident report and determine whether it appears to be part of an incident covering multiple RCs, in particular, whether it is related to a previously known incident (e.g. do the same attacking IP addresses appear, are the attacker's tools and methodology strongly similar):
  • If this is a new, unrelated incident, assign an identifying tag (of the format [EGI-YYYYMMDD-NN]) to the incident and announce it to all RCs via site-security-contacts@mailman.egi.eu, all NGIs via ngi-security-contacts@mailman.egi.eu and the EGI CSIRT via csirt@egi.eu using the recommended templates.
  • If the incident is part of an incident covering multiple RCs, the incident coordinator MAY choose not to announce each incident separately, but instead issue regular updates on the overall incident.
• Take any appropriate actions in order to:
  • Contact affected parties to obtain accurate information at an appropriate level of detail and in a timely manner.
  • Investigate to determine the cause and extent of the incident, what assets have been compromised (credentials etc.), and how to resolve the incident.
  • Help involved RCs to resolve the incident by providing recommendations, promoting collaboration with other RCs and periodically checking their statuses.
  • Maintain communications with any other involved parties inside and outside EGI.
• When appropriate, send updated:
  • Summary reports to all RCs, NGIs and the EGI-CSIRT (site-security-contacts@mailman.egi.eu, ngi-security-contacts@mailman.egi.eu and csirt@egi.eu), containing the status of the incident and indicators of compromise that can be used by RCs to evaluate their implication
  • Detailed reports to the RCs directly involved and affected by the incident, containing interesting findings or possible leads that could be used to resolve the incident
• If malicious behaviour or a policy violation can be linked to a user account or identity:
  • Add the account or identity to the emergency suspension list following the appropriate procedure.
  • If applicable, report the incident to the VO providing access. Coordinate any user suspension and job termination with the VO.
  • Without hindering the investigation, verify the legitimacy or otherwise of the activity with the owner of the account or identity
• If user credentials have been exposed or compromised, report it to the relevant credential provider. In particular, CA contacts are available on https://www.eugridpma.org/showca.
• When suspended accounts or identities no longer represent a threat, typically when the incident is resolved and compromised credentials have been re-issued, remove them from the emergency suspension list
• When a virtual appliance is identified as being vulnerable or malicious, ensure that:
  • Its endorsement is revoked on APP-DB
  • All instantiated and running VMs using this virtual appliance are properly handled
• Based on the incident closure report received from the affected RC, send a closure report with the relevant information to all partners.

...